Am 13.10.2011 16:07, schrieb Cédric Krier:
Sphinx can do more than just documentation. We already analyzed and it
matches all our requirements (see previous emails).
We don't want a CMS.
Implementing a lot of extensions will convert sphinx to a CMS - so this
is not the point. Better to say: sphinx is in focus, because the
documentation is the heart of the website and the easiest way to
maintain it is sphinx, am I right?
In a formerly post you wrote, that you want edit the page with vim,
everything in flat files etc. But this will build a barrier for the
future: You wanna write a lot of modules, documented with rst and
exportable as documention to the website. But there could be a less
technical group involved in the tryton community: the project managers
of implementations. They should have also the possibility to contribute
here knowledges to the website - without opening a comandline and
learning markup languages. And finally you don't want to be annoyed with
a lot of questions about how to contribute content to the website.
I have not see any good translation tools in Drupla nor any CMS. We
want po files to translate.
This looks strange for me. Changing a single word in the english version
will result in the need to change other languages as well. And for non
technical user is a hassle to translate things like
msgstr ""
" {{li}}{{a class=\"documentation\" "
"href=\"/de/documentation.html\"}}Dokumentation{{/a}}{{/li}}".
So it's hard to acquirer volunteers who translate content on the
website. This should be more simple - without knowing how to implement
an other solution. In our CMS we have choosen this way: a text without a
marker is general (or untranslated), if there is a translation fitting
the browser language the system choose this (like content negotiation).
But this ist technical stuff again ;)
The conclusion of what I wanna say:
The discussion about the content and the target of the website is
fruitful, because we get a more general picture of the expectations of
all the community. The discussion about the technical implementation
should start later. So Anthony's approach to write a document together
is a good step and each other input should be welcome as well.
--
[email protected] mailing list
