[ANN] Instiki 0.8.5: Content Mangement Wiki

ruby-talk
1

You can now use Instiki as a CMS with a password-protected back end
that allows for edits and a read-only, published front end with no
controls. Read all about how to set that up in HowToUseInstikiAsCMS[1].
I’m powering the Next Angle[2] site with this version.

Look forward to version 0.9: Bill Atkins is implementing color diffs[3].

More information and download links on www.instiki.org.

[1] http://www.instiki.org/show/HowToUseInstikiAsCMS
[2] http://www.nextangle.com/
[3] http://www.instiki.org/show/ColorDiffs

···

–
David Heinemeier Hansson

2

Look forward to version 0.9: Bill Atkins is implementing color diffs[3].

Not sure if this was discussed before; I thought I had asked I could not
find it.

Is there any plan to have a internal representation of a page independent of
input (Textile, RDOC, …) or output (HTML) markup e.g. XML(ish) ?
Conversion loss can be handled by the usual XML approach: “don’t mess with
what you can’t understand, but make sure you pass it on through.” So in
whatever markup I choose to edit a page, I might see some parts as raw
XML(ish).

Pros:

  • RDOC input markup can be subsequently edited with Textile markup
  • Semantic markup can be minimally entered as XML(ish)
  • Editing can be done at level of semantic units smaller than entire page:
    needs a small amount of cross-platform JScript to open edit boxes on units
    smaller than entire wiki page
  • CSS easier exploited for such semantic markup

Cons?

  • Counter to the philosophy of Instiki?
  • Spoils the simplicity of Instiki?
  • Other cons?

Or have I missed something that is already there? e.g. is there already the
ability to easily create something functionally akin to
…
or even

…
markup ?

Thanks!