Docbook Build Toolchain (was Re: Proposal: Create product for each derivative's documentation)

[Dougie Richardson]

That is quite cool, what I've been looking at is the feasibility of a
web based editing system.

When you consider it, the selection of tags required is generally
pretty low and there are plenty of good JavaScript WYSIWYG editors out
there. If we had a WYSIWYM editor.

For example:

1. Click New Article, a skeleton DocBook page is generated and the
display leaves markers for title and any other expected tags.
2. User writes their article and highlights text that should be a
title and gives it a depth. System generates the relevant DocBook from
the highlighted region.
3. User hits the validate button and gets a pass or a highlighted
error on screen.
4. User saves and submits.

Or:

1. User finds an error and goes to the web docs, finds the page and
clicks submit alteration.
2. Page opens the editor with the relevant XML file.
3. User edits it.
4. User validates it.
5. User hits submit, a patch is generated and sent to the mailing list.

I've been messing about with a few ways of doing this and think that
the liklihood of having a production system that can do everything
core members can do is way off. However for the two above scenarios,
given the limited number of tags required I think this is completely
feasible within this cycle.

Regards,

Dougie Richardson
http://www.lynxworks.eu/
dougierichardson at ubuntu.com