The Setup
As many of you know, I’m a major adherent to wikification of a variety of unstructured content. This has historically been in the context of corporate data availability and development optimization. However, for the general public, I haven’t gone through the massive transformation to present to you all a new wikification model.
Well, what you don’t know (yet) is: I actually have been researching and designing a wiki delivery for Javamancy! However, in addition to the wiki software to use, per se, there are also the considerations of:
- Data persistence
- Data backup/recovery/archival
- Content workflow
- Import/export of content
The Premise
Why wikify?
There are a lot of topics that, in blog-speak, may be more “page” oriented, rather than “post” oriented (in WordPress parlance). By itself, not a dramatic culture shock… however, if you anticipate have several hundred WP pages wandering about the system, it makes you wonder if it’s the correct way to manage this parallel ever-growing collection of content. And add in the requirement to provide URL/URN directory services (a link repository of useful destinations!), and clearly a blog is not the most appropriate platform.
This scenario is extremely common in corporate settings, so if you consider that much of the content I’m providing herein can be aligned in the same way, then it’s not difficult to understand and appreciate why a wiki platform is necessary to accommodate this new line of intended content.
The Action
So, hang in there, Adventurous Readers!
I’m still designing quite a bit of the upcoming platform. And, of course, we’ll announce its availability here once it’s publicly accessible.
N.B.
Yes, I’m targeting PHP and Python, not Java, for the wiki platform. This diverges from my predominant deployments of enterprise Java-based wiki-blog-CMS platforms. This isn’t due to preference; unfortunately, it’s currently due to the limitations of the hosting provider.
