Enabling easier translation - changing the structure of GGL
It's time we really change the way the content of GetGNULinux.org is managed.
We have discussed this in the past but in the end I have taken no action. I am now determined to improve this significantly.
I was unsure as to what we needed/wanted, but today I have a much clearer vision. I am simply looking at the case of the Galician translation. The whole GGL content has been translated into Galician on the translation wiki, and has been ready for several weeks now. However, the text has to be laboriously transferred to the XHTML code, while also using our SVN repository. The translator does not have the knowledge to do this, I do not have the time to do it (several days of full-time work, lots of site-specific things to know). This frustrates me a lot, because so much of the useful work has been completed and is just in standstill.
So I think the requirements for a new system are:
- Easy editing of the content of the pages.
A user should be able to edit the text of a page (content, not header/menus etc.) with a clear interface without code. The interface must respect any existing tags (XHTML classes, ids...) while allowing editing of the text just like a blog interface.
- Immediate preview of result.
There should be no two-step editing (currently wiki then html), one should view what he/she translates in the final form immediately.
- Headers, footers, CSS, can all be edited manually with code / SVN as they are today. These are rarely changed anyway.
- Current website appearance and urls entirely unchanged
- Vadid XHTML code
While working on the planet site I noticed that Wordpress is highly flexible (with the use of php for headers/footers) so I wondered if it could be a solution. I am not really sure about the other possibilities we discussed - the key here is that editing the site should be *easy*. I cannot conceive that one should know and work so much (build code, work with SVN...) just to change a page on our website, while blogs are so easy to build these days.
I look forward to your ideas once again, and this time with a more precise requirements list we should find a solution.
thanks a lot