Drupal Ideas, Development Opportunity, Co-operation
Intro…Product Community Content System
I’m going to be involved in a project, where we think that Drupal would be very useful.
It’s all about helping customers and dealers understand, use, and discuss our products. We would like to use web pages of content, comments, forums and tagging (n level). I’ve put together some requirements/ideas. Some of the pre-release stuff will have restricted acccess.
We will probably get some outside developer help on this, but before we appoint someone to do the work, we’d like to kick the ideas around with some friendly people.
Also if other people would find this useful, maybe we could release any code, guidelines etc etc into the open community.
Please get in touch with a comment or on Linked in(Drupal).
1.1 Requirements for Drupal for this purpose
In general Drupal seems to be a pretty good start point.
1.1.1 Automatic registration of users
We have a central system which has a user registration list that will be able to create selected user registrations in the Drupal system.
1.1.2 Inter application session continuation
One web app (e.g. our shopping system, or customer portal), can refer the customer web session to another web app (e.g. Drupal), with a session key. If the user is known to the target app, they will be logged in, otherwise they will be redirected to a registration page on a 3rd site.
1.1.3 Areas of content with their own access
There will be permission roles which are the same across the entire system. The roles will have a simple ascending set of rights.
We should like to split the system into areas (maybe like the Drupal “Books”) , including page, comment and forum content.
Another system will then allocate which users are entitled to access which areas with which roles.
1.1.4 Development between systems
We use several systems to develop software on using Sprint Methodology.
When we start a sprint, we will take a copy of the main Drupal system, and insert it into our development system.
In the meanwhile there will be changes on the main drupal system (comments, forum posts, small edits on the documents).
During the Sprint we will change the “pages” of the development Drupal system.
When we release the work from the sprint, we would like to merge the “pages” from development and the main system into the main system.
We would like to use a system like subversion for managing these changes.
We would like to separate the page content from the rest of the system, and be able to manage it in flat HTML files, probably with some extra tags.
Then we could book the sets of content into the subversion system and merge them.
Finally the merged pages would be upload into Drupal.