Greetings all! 2012/3/31 Bogdan Marinov <daggers...@gmail.com>: >> 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.
I updated translations and changed index.php and .htaccess for use /$LANG_CODE/ pattern for translations and backward compatible. On some languages phrase "User Guide" too long and we have troubles with show this links. I think we can drop one "User Guide" link from header box and maybe apply some patches for i18n support. Also we have a big problem with RTL languages like Arabic - we don't support correctly those languages. I can write some patches for support this feature but not very fast. You can look at our new design for test here - http://pollux.47tuc.ru > 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.) > I think the separation of the right column to the blocks for users and developers a good idea. > 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 made it. -- With best regards, Alexander ------------------------------------------------------------------------------ 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
