Hi Sylvain,
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 overhaul....or 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.
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
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.
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".
((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 hardly
have any understanding of the programming side, with the trunks and commits
and all.))
Maybe Martin and/or Maren can give updated and/or more technical
answer for that?
For #2, I created the vast majority of what we have on the FAQ page
today. (Well, the text anyway. It used to be straight html with anchors,
but Martin installed a TOC plugin a few months ago. Now we can only edit
the answers. If we need to add a new question, we have to ask Martin to do
it.) I updated it from the old version, which I think is still existing in
the wiki. (I made an updated version for the developers on the wiki too,
but they apparently weren't interested in updating it. So it stays out of
date.) Anyway, at that time, I had the option to have it all on one text
block, or divided over 2 or more.
For myself, it was better to have it all in one block. Most of the
time, I worked on it locally in a text editor, and then pasted back in to
save/publish. The text editor makes it so much easier, because it has the
formatting, numbered lines, find/replace, etc. Ssooo much easier!!
And so for myself, it's still better to have it in one block. And I
would be happy to take on the responsibility to edit that page, if folks
send me the info. However, on the other hand, I do understand that might
not be the best scenario, logistically, for the project as a whole. So if
everyone wants to break it up, I certainly would not object. I wonder if
that can be done in a seamless way? Wouldn't there be a gap between blocks?
I can't answer #3.
All best,
brynn
--------------------------------------------------
From: "Sylvain Chiron" <chironsylv...@orange.fr>
Sent: Thursday, June 02, 2016 5:07 PM
To: "Inkscape translators" <inkscape-transla...@lists.sourceforge.net>;
"Inkscape Docs" <inkscape-docs@lists.sourceforge.net>
Subject: [Inkscape-docs] Questions concerning the website's content
> Hi all,
>
> I have three questions concerning the website's content.
>
> 1. For more space and better reading, headings (h2) are often preceded
> by an empty paragraph, e.g. in:
> * https://inkscape.org/en/learn/animation/
> * https://inkscape.org/en/learn/faq/
> This is true that pages are harder to read without that space; see:
> * https://inkscape.org/en/develop/getting-started/
> * https://inkscape.org/en/contribute/testing/
> However I have something against that practice of the empty paragraph; I
> feel it as wrong semantic. Couldn't we simply add more margin at the top
> of these headings? I suggest 4ex (it's currently 1.5ex).
> We could also increase the margin-top of 3rd-level headings (from 1.5ex
> to 2.5ex).
> Then we should remove those empty paragraphs (in the source form of
> <p> </p>).
>
> 2. It is quite hard to find the part we want when editing the FAQ; could
> we subdivide the only text plugin in several text plugins, one for each
> section?
>
> 3. Is it possible to translate the two following pages, or will it be
> made possible?
> * https://inkscape.org/fr/apropos/captures/
> * https://inkscape.org/fr/teams/ (and why not teams themselves)
>
> Everyone may give their opinion about the first two questions; the last
> one is for those who know…
>
> Thank you,
> --
> Sylvain
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
> _______________________________________________
> Inkscape-docs mailing list
> Inkscape-docs@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-docs
>
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Inkscape-docs mailing list
Inkscape-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-docs
