By saltcod on

Hi,

I want to develop a Drupalized intranet for creating policy documents. I want these documents to be 'pushed' out to a public Drupal site.

I want the intranet (eventually Open Atrium, or custom drupalization), to avail of case tracking, diff, calendar, etc....but I want the public site to be just like a regular website with lots of content organized in books.

So, a typical workflow:

Intranet
1. Create working drafts of policies
2. Edit drafts
3. create a 'final version'

Public site
4. "push" the final version of a document to the public site - this version is only readable at the public site. All edits will need to occur in the intranet.

This possible? It sounds like multisite + shared content to me......

THanks!

Terry

Comments

kvantomme’s picture

kvantomme commented

You should have a look at the demo movie we have up about Spezzle, a specification tool we are building.

When you say policy documents I'm thinking that there will be quite a few repetitive bits in there, in that demo you'll see a way to create those bits and reuse them. We also use RDFa to add a metadata layer that can be used for tickets that can be tracked or for adding comments, that then can be filtered out. All that through a WYSIWYG editor. So you could have a develop view of a policy paper and then filter out all the comments when you publish it for the public.

Right now we don't have concurrent multiuser editing, but that's in the pipeline...

If you have a specific project that you need help with, get in touch ;)

-----------------
Check out our blog on http://www.pronovix.com/blog