Le 03/06/2016 à 05:45, Brynn a écrit : 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… 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. 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. I think we can just do it because I'm very focused on the typography/semantics of the website and this is quite annoying… About the commits, the wiki has some info: http://wiki.inkscape.org/wiki/index.php/WebSite#Website_Development Then I joined the project and submitted two things: a fix for the ‘TOC nesting bug’ I detailed previously, and a fix in style to avoid overflow of preformatted blocks, using a scrollbar — see e.g.: https://inkscape.org/en/develop/debugging/ Therefore I had such an introduction… However I don't have a local installation of the website as the Python scripts don't work with me (I didn't emailed Martin about it yet, I'll do it), and I avoid using it as it is very hard to use with my ten-year slow computer. Fortunately I can often look carefully at what I wrote with autistic abilities, and prove its exactness. About caching, well, if you know the English word (I've only known the use in computing for a long time), this is it: the website server must compute many things to have the document it finally deliver to the visitor. To avoid redoing those same computations for each visitor who looks at the very same page, it caches some results to deliver them automatically, until the variables are effectively changed (in a perfect world). I don't have many details about what is cached for the Inkscape website but this principle is usually sufficient to understand everything. The ‘trunk’ is usually unique — it is the main development branch for a project. What is a branch? When we want to develop a feature, we might break the project. The next person who want to develop can't wait for our feature to be ready to start to develop their own one. So both developments are started from a state of the project that is known to work. Then we divide the development progress in two ‘branches’ and we will ‘merge’ them when both will be ready, to get a project with two new cool working features. Well, life with branches is much more rich and complex, but this is the basic idea. A ‘commit’ is the process of submitting a change to a branch. Am I clear? I should have enough… Thanks for your investment in the FAQs. I followed the story of the apparition of the TOC, don't you remember? About that TOC plugin, it seems you really didn't get it… even if we tried to explain. This plugin is a wonderful thing: it generates the anchors itself from the page contents. Then the writers don't have to mind the TOC when adding sections. You can totally add new questions to the FAQ without any problem. The anchor will appear in the TOC. You don't even have to set an ID to the heading (unless your heading has exactly the same title as another one). Just look at this script which is delivered with the website's pages: http://bazaar.launchpad.net/~inkscape-webadmin/inkscape-web/inkscape-web/... Lines 22–26 say: when the document is ready, if there is a (single) #toc, then initialise anchors. The description of the way to do it is from line 35 to 83. Line 39 says: iterate over every heading in .wrapper. Lines 44–54 say: pick an id for the current heading. Line 69: add an anchor in the TOC as a list item leading to the heading. Okay, but then, how can you edit the plugins? This is the main problem. Another thing that bothers me is the forced use of HTML entities by the CMS in the source code. In English you mostly have simple letters so that's not a problem, but e.g. in French you have many accented letters, and the very frequent ‘é’ becomes é and the source code becomes really difficult to read. There are also many apostrophs which become '. And many different accented letters: à è ê ô î â û ë ï and capital variants. https://inkscape.org/en/download/?edit Do you see any gap? -- Sylvain