[development] Staging content to production

[Bèr Kessels]

More stuff to consider:
 " You are now reading the first example newsentry. Follow this link to edit 
or remove it" 
 " Welcome to your new site. This page is the first page in your "about us" 
hierarchy. Follow this link to write your personal about us page."

Those are nodes. Those are content. And they are configuration. They should 
ship with install profiles. Yet also import and export under certain 
conditions. 

Op zondag 18 juni 2006 04:21, schreef Adrian Rossouw:
> This could be a bad idea. but how about negative node id's?

I think the best design is to:
a) allow multiple node-types. IE $node->types = array ('book', 'blog') 
b) add a type 'special' (better names are welcome). Any node with that type is 
considered special and configuration.

c) re-use these nodes to store mission, footer, welcome etc (I developed 
microcontent.module for this cery case where I wanted those "variables" as 
well as blocks to be import-exportable)