[drupal-docs] opml vs weboutliner?

[Vladimir Zlatanov]

> hm...
> 
> CivicSpace documentation...
> 
> Alright.  I can see this working if, let's say, we let CivicSpace doc
> people handle the CivicSpace *specific* information.  Wherever that
> differs from Drupal info, we have a link (civic space users, see
> this....).  Maybe there is a book, or a branch in a book that deals
> with CivicSpace specific details we can link to.
I guess what I'm trying to say is the handbook is an online
documentation. Many people and organisations are interested in making it
good. These people target different 'native' audiences - look at
CivicSpace, DrupalED, Bryght,... Their effort in adapting their 'native'
docs should be minimised, if we want them to have more resources
available for docs proper. This is an organisational issue first,
technical second.

There is a second tier -good to have - 'related links'. On and off site
pages, related to the current handbook one. I personally would consider
these as suggestions and ideas of how to improve the current page.

> > > Ok, wait, I see, because you have downloaded the book.
> > > Hm, well, I guess we control it on this site to prevent two people
> > > editing the same page at the same time.  
> > >     
> > The bigger question is what do we control? Content and its structure, I
> > suppose. But structure should reflect the particular audience.
> > CivicSpace or Drupal? How do you map between those - to save the effort
> > of the writers - they are better at creating rather than pasting. It can
> > become frustrating after some time.
> > 
> >   
> bah, anyone can hit ctrl+v.  
it's not only ctrl +v  and it depends how many times

> Drupal is the base, and the handbook is hosted on Drupal.  
Agreed. 

> Documentation cannot be merged.  
If license allows, and it is useful why not? Automatically, guess not.

> What do the CivicSpace people want to do?
CivicSpace is just one of the many service providers. Bryght are
another. There is useful information, may be candidate documentation
spread all around the web.

I think it would make sense, for the really useful bits to tricke down
to mama (Drupal handbook that is)

> > The skeleton is the handbook - tight, rarely changed content. Feathers -
> > everything else, i.e suggested improvements, external articles, etc...
> > Some of those considered useful, can enter the handbook after some time.
> >   
> Due to Drupal's no backwards compatibility policy, some things will
> change every reiteration.  
Yes. But the changes are details of the improvements in Drupal. The
overall concepts, generally how to use it, many others will not.