Hi All,
The LanguageTool website (and wiki) has many audiences. Possibly, a person
has more than one role.
Probably, the primary audiences are these:
People who want to use LT
People who want to write XML rules
Java developers who want to enhance LT
Website developers who want to integrate LT with their websites
(http://languagetool.org/website-integration/)
Secondary audiences not listed above
(http://wiki.languagetool.org/make-languagetool-better):
Language maintainers
Java Swing developers
Grails developers
Translators
Linguistics students
To make the new website as clear as possible, I suggest that the content is
organized according to the primary audiences. As an alternative to the
heading 'Development', have separate headings, for example:
Rule Development
Java Development
The Development page (http://languagetool.org/development/) has the text,
"This page has everything you need to know to teach LanguageTool new error
detection rules, plus more." That is not true, because we have the wiki.
But, why is some information on http://languagetool.org/ and some
information on http://wiki.languagetool.org? Unless you have a good reason
not to, I suggest that the information that is on the wiki is merged with
the primary website.
If you keep the wiki, change the name in the site navigation to something
more meaningful (its purpose or its content). The wiki is a medium of
delivery. If all the information were in a PDF file, the navigation title
would not be 'PDF'.
Regards,
Mike Unwalla
Contact: www.techscribe.co.uk/techw/contact.htm
-----Original Message-----
From: Daniel Naber [mailto:list2...@danielnaber.de]
Sent: 28 October 2013 15:58
To: development discussion for LanguageTool
Subject: Re: planning LT homepage relaunch
<snip>
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.
<snip>
------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
Languagetool-devel mailing list
Languagetool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/languagetool-devel
