On 13/10/11 17:02 +0200, Jan Grasnick | grasbauer ug wrote: > 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?
Absolutly not.
Sphinx will build a static website and it is a very important feature for us.
A CMS is a bullshit to maintain.
We did not choose sphinx because of the documentation but because it is the
best tool we find that match our requirements.
> 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.
Yes rst is a great format because *anybody* can use it.
> 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.
If someone want to write a document for the website and he can not do it in
RST, I prefer that he doesn't do it because he will lose the time of
everybody.
> And finally you don't want
> to be annoyed with a lot of questions about how to contribute
> content to the website.
Don't care. It will be pretty simple to explain:
- fetch the source here
- submit a patch like explain in HowtoContribute.
> >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}}".
That's why we want to switch from rst2tag to Sphinx.
Sphinx is in rst and it will give such po file:
http://hg.tryton.org/tryton/file/tip/doc/usage.pot
> 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 po way is pretty comment and it works.
I don't understand your explaination.
--
Cédric Krier
B2CK SPRL
Rue de Rotterdam, 4
4000 Liège
Belgium
Tel: +32 472 54 46 59
Email/Jabber: [email protected]
Website: http://www.b2ck.com/
pgpchxSwnjuDK.pgp
Description: PGP signature
