Although the progenitor of my having a website, this blog went on hiatus in January 2009, and only returned in April of 2012. That’s a good long break.
In the meantime, I was spending far less time on HTML and more time on dumping links onto pages, writing small amounts of text, and doing only small amounts (by comparison with re-installing WordPress and working on the poorly-designed-website) of bit-twiddling with PmWiki.
I much prefer the PmWiki markup to WordPress’ markup — especially since WordPress has a pseudo-HTML markup (that looks like HTML, but is re-processed invisibly on the backend and transformed in ways you’d least expect.
blah blah visual editor blah blah crap blah blah I miss WordPerfect 5.1 for DOS’s reveal codes blah blah blah
What I’d like is some way to tie the two together better.
One rendering engine for both, media-images use the same warehouse, etc.
The WP FreeStyle wiki plugin adds FreeStyle-wiki markup to WordPress. Nice!
It installs an entire working instance of FreeStyle Wiki inside of WordPress.
That’s a bit of overkill just for rendering posts.
Plus, I already have a working install of PmWiki — just not inside of WordPress.
So, I have to find some way to get allow WordPress to pass arbitrary text — hopefully with wiki-markup — to PmWiki and retrieve the HTML-ified text in return (and hope that WordPress doesn’t f**k it up).
The FsWiki plugin gives me a quick idea of how to pass off the text to a renderer — it’s getting it to and from PmWiki that concerns me.
Quite possibly not difficult — I just haven’t tried it yet.
Converts the string $str with PmWiki markup into the corresponding HTML code, assuming the current page is $pagename.
Other avenues of research include the TextControl plugin.