Nicolas,
Thanks for getting back to me with some fantastic questions. I've pushed the conversation to the inkscape developer mailing list so others can stay up to date and offer their ideas.
...
On Fri, 2013-05-31 at 14:34 +0100, Nicolas Dufour wrote:
I've started to work on translating pages and parts of the UI. Django-CMS is a bit complex and its website documentation somewhat cryptic, but it looks very interesting, and quite convenient for a translator.
It can take one like that. The template formula for including blocks of CMSable widgets is something that may require refinement as we go forwards. Especially for the front page. For now, we're using the most basic formulations.
I've just added a bug report about translated menus that are split in two lines and cause some issues (https://bugs.launchpad.net/inkscape-web/+bug/1186235). It's a very annoying problem, but I'm sure it won't be too difficult to solve. I also have some questions:
I saw the problem with the french menu and have already contacted the designer and some other people to help solve the issue. There has been no response as of yet, partly because of classes/exams. If anyone else wishes to help solve the bug, please see the developers link below.
- Regarding static content, we currently have some pages (tutorials
and keys and mouse references) that are generated externally (see https://launchpad.net/inkscape-docs). How should we handle them? Note that the keys and mouse references are linked directly in the application and thus should be accessible from exactly the same localized URL (for French: http://inkscape.org/doc/keys048.fr.html).
I didn't know about the generative content, that's quite interesting. We could either insert the generated content into the right cms widget items, or do something else. It depends if we want the content committed to bzr or just in the database with other content.
- How will the news be managed? I see nothing about it on the website,
but I guess that's something that won't be abandoned.
The news module is operational, but it has two big caveats: 1. English only, 2. No on-site editing. Thus as the technical lead, I intend to replace the news module with a newly written one which has both multi-language and onsite editing.
- The French menu is exactly as defined in
http://staging.inkscape.org/fr/admin/cms/page/, but it's not the case with the other languages. Is the menu order language-dependent?
The CMS seems to order the menu according to how much has been translated and which menu was edited last. It is not idea, but a fix would require patching upstream.
- Apparently, the website is synchronized to the LP code manually
(I've ported images for the books page, but they are not on-line yet). Do you plan to give update access to someone else, or do you prefer that we ask you every time we something is committed.
The cron jobs are not complete, there is a bug report assigned to me. Images should actually be uploaded via the CMS unless they are non-content images for use in the style/theme of the website. I may have to reverse your commit for now. If you get stuck adding images, let me know and we'll figure it out together.
Apart from it, I'd like to run a local version of the website for testing purposes. SQLite, Django, Django CMS and the dependencies are installed on my computer, but I still have difficulties with the CMS modules (Error: No module named cmsplugin_news, or Error: No module named cms.plugins.twitter if I comment the cmsplugin_news line). Do you have some documentation on how to run it (the README file didn't help)? I'm new to Django CMS, and not very experienced with Django and I've probably missed something obvious... If not, I'll try to search the web, there should be some tips somewhere.
Absolutely, at the bottom of the website there's a link "Website development guide:" to this wiki page: http://wiki.inkscape.org/wiki/index.php/WebSite and by following this guide we hope, the website should work locally for development. This also includes bringing in the data from the staging website, since the cms would be empty otherwise.
Please continue to report bugs and press the website further :-)
Best Regards, Martin Owens