> About that TOC plugin, it seems you really didn't get it… even if we
> tried to explain.
Yes, I understand it now. Apparently you and Maren and Martin can add new
questions, as well as answers. But I can't add new questions - only
answers, because I can't edit the code.
The TOC is frustrating for me, because I originally typed/edited everything
on the page (by writing the html directly, which I find enjoyable). But
like so many other parts of the website cms/django, it very much limits what
I am able to do. Now, except for minor edits, here and there, all I can
contribute is comments about the website content. By now, most of the
website is controlled from a level that I don't have access to, and couldn't
use it, even if I did.
> Okay, but then, how can you edit the plugins? This is the main problem.
When I first created that page, the only plugin available (to me) was Links.
At first, I didn't use it at all, because it didn't work. But later, we
found the problem was one of my Firefox plugins that blocks the referrer
header. So then, I was able to fix all the links.
All best,
brynn
--
From: "Sylvain Chiron"
Sent: Friday, June 03, 2016 12:27 AM
To: "Brynn"
Cc: "Inkscape translators" ;
"Inkscape Docs"
Subject: Re: [Inkscape-docs] Questions concerning the website's content
> Le 03/06/2016 à 05:45, Brynn a écrit :
>>For #1, I brought this up a long time ago. Well, something very
>> similar (I think it was the h3 style I wanted to tweak, or maybe
>> h4.). I think the text styling needs an overhaulor at least a
>> tweak. Styles, and maybe even some classes or IDs, etc. too. The reply
>> at that time was that we were considering a new website design in the
>> foreseeable future. Although it seems like it stays in the distant
>> future, and doesn't get closer. But the response was let's talk about
>> it when we are getting a new design.
>
> Sure, we could have a better design… Currently pages' content is a bit
> blunt. I don't think it's the right moment as the focus is on the 0.92
> release. We could work on it in a few months if you want.
> I also have other work, such as translating that FLOSS manual…
>
>>There's a good chance that I put most of those empty paragraphs
>> in there. The pages, and especially the pages with a lot of text, come
>> across as imposing -- the wall of text, as they say. So I think they
>> are the best we can do currently. I would not want to remove them until
>> we have a good replacement. Do you think visitors to the site recognize
>> that it's an empty paragraph? I don't see how they could know the
>> difference, unless maybe if they are website designers
>
> If they are a bit interested in style, typography or semantics like I
> am, they will notice that some headings have more space above them than
> others, and they will now that use of an empty paragraph to add more
> space in computer writing (most probably think it's a good use).
> They can also inspect the DOM (the document tree), of course.
>
>>Are the changes you suggest something that could be made easily?
>> I'll have to refresh my html, and dig in a little bit, to understand
>> specifically what you mention. In general, I understand what you're
>> saying. But as far as the code itself, that's not in the front of my
>> memory.
>
> Yes, this is a very simple change, I can commit it within one minute.
> To understand what I meant, just right-click on a heading, and click the
> last menu item ‘Inspect element’. The inspector should appear, showing
> the document tree, and the tag/node for the heading you right-clicked
> will be selected. The styles that apply to the selected node are shown
> on the right.
> The style property I refer to is ‘margin’.
> In Firefox at least, you should see ‘main.css:line number’, indicating
> the place where the rule is defined. If you click on it, you'll go to
> the file.
>
>>If the changes can be easily inserted into the css, I'd say let's
>> do it. But in this case, one change may lead to another and another.
>> So maybe better to wait until everyone is focused on the new design? At
>> least that's what I like to call "my simple-minded thoughts".
>
> I think we can just do it because I'm very focused on the
> typography/semantics of the website and this is quite annoying…
>
>>((We (Sylvain and I) might not have had a formal introduction.
>> So just for general info I do not have a local installation of the
>> website. The only code I know is simple html, and my understanding of
>> how websites work is fairly general and non-technical. (For example,
>> this caching that's been mentioned so much lately -- I only understand
>> the definition of "caching" and not what happens technically with the
>> server.) I can add and edit the site content, using the django wysiwyg
>> and/or the source/html. And I can join discussions about the content.
>> But I
