Vysnu, evolution, etc.

I am undecided at present about what the future holds for Vysnu. Here are three divergent forks I’ll present to you.

  1. Vysnu will stay with the WordPress CMS codebase, and as it matures, WordPress will provide a flexible enough scheme for content generation and management. The latest alphas incorporate basic dynamic page generation, better cruft-free urls, and a leaner (presumably faster) codebase. One of the best things about WordPress is that it is geniunely easy to use, and matched only by e107 in its friendly interface.

  2. Vysnu can move to the drupal platform. Drupal offers flexibility unmatched by other popular CMSs. I can explore newer ways of blogging, newer ways of expressing myself. Drupal’s codebase is also very enticing, and over the last few weeks, I’ve become very familiar with it. One of the things that I like about Drupal is that the possibilities offered by it doesn’t seem to end. Why should I be limited to one linear blog? Why not two or three distinct, yet cohesive blogs on one page? Why can’t I find newer ways to extend the blogging sphere, why should I stick to the same rote that WordPress enforces? To break away, I must embrace Drupal, or…

  3. …I should develop my own CMS. What about one written ground up in PHP 5, building on OOP? In fact, the backend to Koal is a very primitive implementation of my perfect CMS, one without constraints 😉