Cms
De Wiki - Unasur
Contenido |
Introduction
This is the discussion page about the cms for dakshinsur.org Now a Drupal is installed, so the discussion in some parts will refer to the latest version of it. If another cms will be installed we have to add technical discussion on that too.
Drupal is a cms released under GPL. If you don't know anything about it, you can read this short intro
Structure
How do we design the website? This section is about the structure of the site so, how we use blocks and menus.
Localization
How do we organise the localization? We have to make a multi language Drupal, with interface and content translation. This features are already implemented on the Drupal 6 core version (the one installed now). I found also some modules which are very useful to solve the localization problem.
i18n is the current Drupal approach on this issue and provides a function which can get the locale from the visitors' browser and translate interface and contents into the proper language (if translated content is available). We can solve the interface translation problem with this module.
The other problem is to translate content. I was suggested to use these software in combination: Virtaal and Apertium. we can give this a try. It works well with spanish / portuguese languages and it is released under GPL.
Then there are two other useful modules:
- Translation 404: this module provides a 404 page for content which hasn't been translated yet.
- Translation Overview: this module gives a list of all content in which is possible to see in what language an article is available. (It is very useful to see if is there anything which has not been translated yet, just for content management)
It is also possible to make virtual domains in order to have different url based with language prefixes (e.g. es.unasur.info , en.unasur.info and so on)
Features
What features do we have to include in our installation to make it more safe and user friendly?
Content
This is the main point. The website we are building has to be clear (and possibly tidy), for us (in order not to have misunderstandings) and for the future visitors.
I think the main thing now is to write down a manifesto, in which we explain our purposes and the way in which we act. We have to expand the themes of Consegi and also Sasi's draft
Then:
- what are the actual contents in which we are working on? we should write them in the site so we can find new people to help us.
- should the mailing list be public? We can publish the mailing list forum like. We can make that integracion messages are automatically published in a forum on the website as messages.
Site administrarion
Client side: everyone of use will be a drupal administrator, so everyone will have the power to edit and configure anything. In the mailing list we decided that everyone (if it is possible) should publish new content and update existing one about every two weeks (this is another issue to discuss).
I (argon) can dedicate much time to administer the modules / content.
Server side: In the future we will all be able to administer the sever hosting drupal. For the moment who are the administrators?
