On Fri, Mar 23, 2012 at 10:14 PM, Matthew Gates <matthew...@gmail.com> wrote:
> Hullo Guys n Gals,
>
> Alex and I (OK, mainly Alex) have been working to refine the new main
> website design. It uses gettext to lookup transaction strings from
> launchpad translated files in the hope that this is much easier to
> maintain than the separate pages we currently have... this should make
> it possible to avoid the problem where we have a page for some
> language which is showing old information.
>
> I want some feedback on it. There is a test version of the site here:
>
> http://porpoisehead.net/stelalex/
>
> What's missing or needs improving?
The link to the "current" manual should make it more clear that it's
on the Wiki. It can be either a change to the text, or a change to the
icon, or both.
For example, the icon can be completely replaced with something else
or a label like the "PDF" for the old user guide can be added to the
current, bland one. A standard wiki symbol is the double-bracket
syntax for links, so I think that a "[[wiki]]" label can do. For a bit
of colour/contrast, the text "wiki" can be in blue like the default
link colour.
Also, the wiki version link/icon should be to the left of ("before")
the PDF one, because it's the recommended option (isn't it?).
I don't like the aggregation of the links in the right column for
several reasons:
- the title "Collaborate" doesn't match the contents
- I think that the list is too long to be readable with the current formatting
- it also aggregates too many too similar-looking links that link to
too different places/tasks - there is a forum link, various downloads
(extras like landscapes), a duplicate link to the user guide, multiple
links to the wiki, etc.
- the scripting documentation link: it's is either unnecessary (there
is already a link to the scripting page on the wiki that should
include this link)
I do like it for one reason, though: it puts all of these links in the
"top screen". Before, they were spread all over the page. I think that
this was one of the reasons that the wiki was (and still is) neglected
by a lot of people. More prominent link to its main page somewhere?
How would it look if all the "contact" links are aggregated in the
same section? The forum and the IRC channel, perhaps also the bug and
support trackers, with some accompanying text instead of the bare
links.
The plugin/script/landscape library links can be inlined in the
feature list, though I don't know how this will affect their
discoverability.
The "bzr" section is bad and should be re-written. (The badness is
actually inherited from the current design. :) At the very least, a
more suitable section name would be something like "source code".
Another option is to move the link to the developers documentation
there. (Which gives me another idea - that section becomes "for
developers", and "collaborate" becomes "for users". Just an idea,
though.)
The site also needs HTTP redirects from the old language sub-sites
(/de, /jp, etc.) to the new dynamic translation URLs. Apologies if
they already exist.
I think that's it. For now. :)
Regards,
Bogdan Marinov
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Stellarium-pubdevel mailing list
Stellarium-pubdevel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel
