new website organization

[ct]

New Website

this is a tracking ticket -- individual tasks depending.

the asciidoced content now needs to be brought into proper shape this means:

1. things will be merged into the 'website-staging' repository and refined there.
2. define a new directory structure (much of the old structure can be kept), needs discussion on how to do it.
3. integrate tiddlywiki (which are migrated to asciidoc) too
4. fix all links

after this the website should be generateable but still use the old asciidoc theme. meanwhile uwiki might be ready...

Later our web designers and css artists may give it a new look

[ct]

The asciidoc-day content is now merged, see:

http://lumiera.org/Lumiera/

Links and CSS are still broken and its not navigateable from the frontpage, further work is needed to be done by someone[tm]. I'd suggest to factor out as much as possible small tickets then this can be done in small incremental steps.

someone still has to asciidoc the tiddlywikis. Do we have a ticket for it?

[pseudoruprecht]

Replying to ct:

someone still has to asciidoc the tiddlywikis. Do we have a ticket for it?

Just created one, it's at #223 and not very detailed yet.

[pseudoruprecht]

I looked into the CSS issue. In the XHTML that is generated from the asciidoc sources, the standard asciidoc stylesheets are included in the header. But they don't exist on the server, so the browser displays the page with the defaults (which isn't very pretty).
The original plan was to go with the asciidoc style settings for now. Seeing to it that the .css are there would fix this issue right now. We can still adjust the styles later on.

[ichthyo]

we can use this ticket also to track individual sub-tasks (use the fields "blocking" and "blocked by")

[ichthyo]

(In #223) We discussed this topic already a bit during the preparation of the Asciidoc Day. The conclusion was that we probably should treat the small tiddlywikis and the Proc-Layer wiki (renderengine.html) separately.

• the small tiddlywikis could be converted into a single asciidoc page each, and then seamlessly integrated into the other asciidoced developer documentation. They mostly contain some design informations from the early stages of the project, and weren't much augmented (but kept up-to-date though)
• contrary to this, the Proc-Layer Tiddlywiki contains a huge amount of detailed technical documentation (probably the same amount then all the other, already asciidoced documentation together). It is crucial for the development of the Proc-Layer, closes the gap between the design documents and the sourcecode documentation and maybe could be the foundation of a technical detail documentation tree.

[bjmr]

I'm trying to get things started up on the site agian so for the time being I'll take this ticket_,