Migrating BeWelcome to Drupal: Difference between revisions
No edit summary |
No edit summary |
||
Line 45: | Line 45: | ||
* lemonhead | * lemonhead | ||
Come work together on the [http://www.bewelcome.org/forums/s1162?sidTB=Q-S6wMP,B48vAgYjaMIpkRVl6o7 4th and 5th of December in Antwerpen]. | |||
== Code driven development == | == Code driven development == |
Revision as of 00:53, 20 November 2010
This is an overview of the project to migrate BeWelcome to Drupal.
Migration
Main things to migrate:
- users
- page-like content:
- FAQ => faq content type (multicrud?)
- tour =>
User fields
- user/register should show more than username/password
Translation
Drupal is based on "everything is English". We would prefer keyword-based translations. A solution would be creating another language: "real English" or something and rename "English" to "coder English" or "Drupal English".
Drupal can't show translation links, but it might be possible to create a module for that.
Privacy
Waiting for D7 modules:
Roles
- developer
- support
- editor
- translator
..
Deployment
- Deployment strategies. We want to have as much as possible to be code-based, but some modules really love the database and auto-increment.
Performance
- Page load speed
- Scalability
People
- guaka
- lemonhead
Come work together on the 4th and 5th of December in Antwerpen.
Code driven development
- Features module for exporting stuff that lives in db into code
- Context module: works with features
- custom modules
- sites/all/modules/custom
- but we want to stick with mainstream modules as much as possible
Drupal 7
We have chosen to start right away with Drupal 7.
Con
- Many modules aren't ready yet.
- There are still some bugs.
Pro
- No need to upgrade to D7 ;)
- D7 has many good things in core that we want (such as user fields)