* Avoid technical documentation being an afterthought, integrate from
the beginning
* Set space for technical documentation in the website
* What framework and tools to use:
- Python + Jinja, markdown based content
- automated documentation is currently being generated with Doxygen.
Some previous experience, challenge may be to make it look good and
integrate with the rest of the site
- important to automate the documentation of wrappers/filters,
choosing a number of standardized headers, that can then be automated
into a section of the site that list all the features supported
- fields to be brainstormed over at the mailing list. Some fields may
be more useful for end users or developers. Screenshots?
* we need to decide on the name and logo/visual metaphors for the
project, whether we build on the existing work from JSR or we start a
new thing. Ruben will put the campaigns team in touch to work on this as
well.
* The graphical aspects of the design (illustration style, fonts, color
palette) can be worked on as it is.
* Automated deployment will be set up by Manufactura on their server,
and later we'll figure out how to integrate with FSF build servers
* How will translation work with auto-generated pages? Maybe separate
site docs and code docs? Problem for later.
Next meeting for the design team would be Jan 29, at 4pm CET.