On 07/02/2011 15:09, Simon Laws wrote:
An idle question somewhat motivated by recently touching on the sample
docs in another ML thread.
Are we going to convert from Confluence to CMS [1]?
If we are eventually going to have to do this (when the autoexport
stops working?) we should probably plan for it rather than do it in a
rush when we are forced to. I haven't looked very closely at the
details. Anybody given it any thought yet? I note there are notes on
migration [2]
[1] http://www.staging.apache.org/dev/cms.html
[2]
https://svn.apache.org/repos/infra/websites/cms/conversion-utilities/cwiki/README.txt
Simon
Simon,
Good to bring this up.
However, looking at the material, my heart sinks :-(
For me, the key thing has to be the ease of creating and maintaining the material. Using some markup
language is ok, but what tools are us poor content creators supposed to use? In see this in the
Apache material at [1]:
"Editing the source in the CMS's webgui relies on the wmd-editor to provide a WYSIWYM look and feel
to the CMS."
...only to find that the link they provide to wmd-editor is broken. A very
poor start.
I checked out some alternative editors and I'm not impressed so far.
Things I would like to see are:
a) How hyperlinks are created and how they are maintained
b) How images/diagrams can be embedded in pages
c) How basic page layout is managed - in particular the handling of Menus,
banners and so on
It is notable how little graphics is contained in the Apache pages for [1] and [2] - are we
returning to the stone age here?
I get the feeling that this system has been produced for the ease of the publishing process, rather
than the creation and maintenance of attractive material.
Please someone prove me wrong.
Yours, Mike.