Hello

I've been thinking lately about how we can make it easier for people
to contribute to the project..

The OE was a great improvement and made it whole lot simpler to get
going for users and did its job pretty well.

Editing xml however isn't something the general public seems to be
willing to do, not to mention they have no idea what docbook is at
all.
Other pain points are how long it takes to validate and build the
documentation - and the cheesy tricks we've had to deploy to squeeze
every performance drop out of both PHP and XML.


If you guys remember our story..
DSSSL rendering took _days_ to build.
XSLT took _hours_.
PhD takes _minutes_.
I think we can do better.
I want it down to _seconds_.

I've been toying with the idea of retiring my baby on its 6year old
birthday early October.. And replace it with something new. Faster.
Easier. Better.


I however don't think we can do that with XML.
And I want to make it even easier to contribute - with essentially no
learning curve.


Looking around the web.. People seem pretty happy with Markdown...
Now, markdown has its obvious crazy huge drawbacks when it comes to
writing documentations.. but I think it can be done. Well.. Sortof.

We would need to create our own Markdown flavour, only adding a tick
here and there, should give us very readable format where people focus
on content rather then struggling with picking xml elements or fitting
things into correct containers or limited semantics.

Rendering our new format into our currently supported formats
shouldn't be a problem, and will more or less be exact same visual
rendering - just massively simplified html output due to the reduction
of the extreme semantics docbook uses.
The important semantics will however still be kept ofcourse.


I've already started working on a PhD output format to help with the transition.
The current format I am targetting looks something like the document attached.



What do you guys think? :)



-Hannes

Reply via email to