On 2013-10-23 20:08, Daniel Naber wrote: > I've planned for long to relaunch the LT homepage with a better design. > Now is the chance to finally do that. These are my *personal* ideas > about the future of the LanguageTool homepage. I'm looking for > feedback.
So here's a more detailed concept. This can be used for further discussion and once we think that nothing important is missing, this is also what I will send to the designer. I'll leave out the idea of using a CMS for now because of two reasons: I don't know Joomla or another CMS, so it would be another thing to care about, additionally to the design and structure, and it's not trivial to use it technically: we cannot just switch the DNS for languagetool.org to point to some external CMS host because languagetool.org also runs our API. Elements we need on every page: -Logo and page title or a claim (on the homepage) -link to twitter, facebook, and imprint -field for subscription to announcement mailing list -site navigation For site navigation, I suggest these items with sub items: -Languages * Overview (what is today http://languagetool.org/languages/) * All 29 or so languages. This is a lot... some structure would be nice. -Download * LO/OO * LanguageToolFx * Plugins - just links to external pages (now on http://languagetool.org/links/) -Support * FAQ - what's now the list of common problems, http://languagetool.org/issues/ * Forum - external, not sure if it can be integrated nicely * Contact -Development * several links to the Wiki * Mailing List * Bug Reports * WikiCheck What's not covered is the 'screen shots' page and the 'usage' page. I think screen shots can be put on the download pages, and usage information is already mostly covered by the popup that opens on download. Homepage: The homepage contains an intro sentence and a text form for trying LT. It is pre-filled with an example text in the user's native language (assuming his browser language is just that). If we don't support that, we fall back to English. The text form doesn't have a drop-down anymore as today for selecting the language, as the language can be switched in the navigation. If the language currently selected has a detail page (like http://languagetool.org/fr/), there's a big link below the text box "Learn more about LanguageTool's support for <language>" that leads to that page (any better idea to integrate those language pages?). Visual Design: Modern, but not too stylish. I think http://git-scm.com is a nice example of a modern design. What do you think? Anything that is missing? Regards Daniel -- http://www.danielnaber.de ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk _______________________________________________ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel
