Guri Website
De Wiki - Unasur
Contenido |
Introduction
This page is about the organisation of the Guri website. It's a discussion page in which everyone can post his or her opinions about the site administration. Now I put my own ideas about the management of the site, but anyone can edit/add points.
Structure
This section is meant to discuss about the structure of the site such as menus, blocks, user management...
- Menus: how do we organise the menus?
- what menus?
- Navigation menus
- Projects menus
- Links
- Partners
- Other
- disposition
=> Lio: I think it´s better to organise the site in three blocks: left main menu - main - right menu (like the older site). On the left we should put the navigation links and the connections to the main projects we are following. On the right I think it´s better to put secondary links, less important than the first ones, and logos like partners and stuff like that.
- Blocks: what about them?
- what blocks?
- disposition
- User management
- Utilities:
- what functions we have to add to the site?
- Wiki ? ***
- what functions we have to add to the site?
Really useful but it is necessary to organise it well if we want docs to be used from everyone. So I´m pro-wiki only if it´s well done.
- Forum ? ***
I actually dunno if it´s necessary to have a forum. I can follow it - no prob - but if it ends like the first one we did it´s better to focus on other things... The forum can be seen as a “Help plaza” where everyone can get solutions to various problems.
- Banners & logos
what kind of banner would you like to put on? We will put on small banners for "Partners" I think
- Banner list:
- hipatia
- unasur
- fsf.org
- ututo
- drupal
- apache & other software which the site is based on
- debian
- itis
- Banner list:
Modules
This is a list of drupal modules which should be installed on the site. They can be found here.
- Module List
Theme
What theme should we use? How we configure it?
On the drupal website i found Zen, a theme which is highly configurable and easy to use, with much documentation. It is possible to easly make subthemes with CSS if we want.
It´s interesting... could you ssh it and load it? So that I can study better how it works. Theme is very important!
Localization
Now we are working with people internationally, and we know that English is not enough. 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 we are using). I found also some modules which are very useful to solve the localization problem.
i18n which is the current Drupal approach on this issue 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.
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.
Excellent!
Design
How we design the site? Logos? Pictures?
- NK ?
Nice logo done. What other things are necessary?
Improvements (for a more user friendly site)
Features to add to make the website easier to use and understand.
Rss Feeds ? Newsletter?
Contents
- Article we have to write.
- External articles and sources we have to link.
Education material
The main thing we have to produce at the moment is content. We have a lot of things to write about our past projects inside the ITIS.
In my opinion we can split the articles in many parts and think about these topics (of course you can add what you want):
- how we were welcomed by people in the school (by the headmaster, the teachers and the classes)
- do you remember that they didn't want us to teach to informatics classes?
- we can write about Rigola (he wanted to support us economically)
- do you remember Ferraris :D ?
- how we introduced the project to people
- how people knew about us
- what kind of people attended our lessons
- what kind of people continued attending our lessons through the year
- what people expected from our lessons and what they got in the end
- how the lessons developed
- themes
- people reactions to the topics (e.g. when we dealt with p2p they all were interested and active, when we talked about apt they were surfing the net..)
- the internal network problem in the school
- stallman conference in the school
- the most important thing: our conclusion
- our thoughts in relation with free software and free knowledge
- how we decided to organise future lessons
- topics
- the lessons structure (how to experiment a new way of spreading the message)
If we develop this content i think we will have a very interesting material about education to free knowledge
What do you think? - Argon
Material
- Photos, videos and all the things and documents we can share.
- Jucar can get from India books about Gnu/Linux. There is a lot of material inside them on we can base our future lesson and learn too.
Wonderful
To Do
Introduction
- We have to decide who can work for this site and what everyone of us can do.
- After any 'to do' item in the list anyone who starts working at the item must write his or her name in order to distribute the amount of work.
- We have to decide deadlines in order not to waste time.
List:
- Jucar: contact India for the books
Let's split our works ok?
- Lio: work on the website ==> I´ll try to see what is better for us ;)
- Sbals: work on the website
- Argon, Palby & Co: make documents?
