[NeXus-definitions-tickets] [NeXusDefinitions] #146: reactivate key wiki pages that document NeXus

[NeXus Base Classes and Instrument Definitions]

#146: reactivate key wiki pages that document NeXus
-------------------------+--------------------------
 Reporter:  Pete Jemian  |       Owner:  Pete Jemian
     Type:  defect       |      Status:  assigned
 Priority:  major        |   Milestone:  later
Component:  general      |  Resolution:
 Keywords:               |
-------------------------+--------------------------

Comment (by Pete Jemian):

 Suggested actions for the NeXus WWW site first page:
 * follow Ray Osborn's guidelines
 * provide links back to wiki content
 * How to generate the page
   * wiki (preferred method for now)
     * already using
     * requires no additional learning, tooling, or maintenance
   * sphinx to generate the page
     * can be prettier
     * another tool to learn, use, and maintain
       * requires Python
       * sphinx and dependencies are installed by Python's
 {{{easy_install}}} tool
 * Pete will develop a prototype within the wiki and show to the tech
 committee

 Some examples of good home pages (for similar tools) are:
 * sphinx.pocoo.org
 * numpy.org
 * python.org
 * others ... ?

 ''Note'': This is related TRAC ticket
 http://trac.nexusformat.org/definitions/ticket/121 (wontfix)

-- 
Ticket URL: <http://trac.nexusformat.org/definitions/ticket/146#comment:3>
NeXus Base Classes and Instrument Definitions <http://www.nexusformat.org/>
NeXus Base Classes and Instrument Definitions