Hi,

Docs and devel are very excited these days and I’m a bit overwhelmed —
well, it’s good to see motivation out there —, but I also have something
to say just in accordance with the recent website release you might have
noticed.

The first point is that I tried to contact you, Hinerangi, as the
website designer, about the website responsive view for mobile
platforms. Now Inkscape.org will look nice on your cell!
See my initial bug report:
https://bugs.launchpad.net/inkscape-web/+bug/1614196
Martin and I wanted to know if you had an opinion regarding this design;
you might not have received my e-mail.
It’s now possible to view the design directly on Inkscape.org, either
with your phone browser or your desktop browser’s responsive view.
You could also have an opinion concerning the fairly new modal dialogs,
or any other good work from Martin & co.

The second point is for the website editors: as you may have seen, now
our parent menus do no longer link to a page when clicked, but instead
there’s a submenu item in bold font. Initially I set this for the
touch-screen devices: you should be able to open the menu, then select
the page. But Martin told me to apply this mechanism everywhere. He said
that some visitors complained about the parent items being
unclear/confusing. Well, you see, you have an ‘About’ page with
‘Inkscape Overview’ in it as a title, but also ‘Overview’ as a submenu.
Recognize it’s weird — :S.
The current solution is not ideal and we should actually aim to remove
the parent menu items; means putting the interesting content in the
subitems, possibly creating a new subpage.
* ‘About’ may disappear silently.
* ‘Download’ will be changed soon, for the new Releases management system.
* In ‘News’, we should have a ‘Latest News’ submenu (probably not for
editors…).
* ‘Learn’ may disappear silently.
* ‘Develop’ should have ‘Getting Started’ as first menu item.
* ‘Contribute’ should have a similar thing, such as ‘Let’s go’.
* ‘Support Us’ might have a synthetical submenu, or disappear.
* For ‘Community’ it looks a bit more complicated.
Maybe not for right now but at least you’re aware — ;).
For the parent URL (that would become inaccessible from the UI), we
would have a redirect to the first subitem as a fallback, I’d say.

Good night,