The release state should be documented for non-developers.
Most importantly a sequenced introductional howto should be written as readme.
Additionally the concepts, architecture and processes should be documented for advanced users and possibly future developers to get into the module idea.
Comments
Comment #1
miro_dietikerFound a nice introduction tutorial that was created by icanlicalize guys for their previous translation management module.
http://drupal-translation.com/content/drupal-translation-management
Something like this would be great.
Comment #2
schnitzel commentedcgalli was working here: http://drupal.org/node/1445790
I'm not sure if we need a dedicated page.
Comment #3
schnitzel commented2 days
Comment #4
cgalli commentedThe 'user' documentation is progressed quite far. Please have alook at it so we can take the incomplete' tag out.
Architectural documentation will follow.
Comment #5
berdirI think this is good enough for the moment, it will need to be continuously updates as the project progresses, as discussed.
As discussed, architecture/technical documentation is (for the moment) the API documentation, improvements should be made there.