[drupal-docs] opml vs weboutliner?

[Vladimir Zlatanov]

> >> I save the file, navigate to an import function, and import the file, 
> >> specifying the root where the synchronization should happen. Yes, 
> >> still might need to include IDs or some textual markers at the top of 
> >> each page.
> >
> > This sounds like a maintenance nightmare. How are you gonna handle 
> > merging?
> 
> Revisions.
drupal has native revisions, ok, in need of improvement.
CVS merging is a nightmare.

> > How is more than 1 person gonna work on the docs? We'd always be 
> > overwriting our changes.
> 
> *sobs*

One at a time with some safeguards?

Drupal's editing philosophy is more like cvs, than a typical PDM
(product document management). The biggest difference is how and when,do
you lock a document (no locking at all at the moment). But generally in
most commercial systems I've used they assume one person works at a
document at any one time. Usually check-out means put it in my
workspace. Everyone else can read the current 'stable' revision.
I'm unsure if I like this method but I thought I'd mention it.

Another thought. We can't do db locking, it's a mysql thing, but
can't we use ajax (js notification) techniques, to check if somebody
is not already editing this page. This way we won't resolve the problem,
but at least we will help a bit.

wiki? as a staging area, when settled ctrl-v?

> I just want an easy way to re-organize large chunks of book hierarchy. 
> You can feel free to ignore any crazy ideas I have if they are not 
> implementable. Right now it takes 3 clicks *per page* to change the 
> outline positioning, and it can only be done one page at a time.
That hurts :(

The whole hierarchy business is not very good in drupal. And I agree
that some better method for changing/refactoring different hierarchies
en masse is needed.