First, the problem with a traditional CMS, like my Siikir CMS that powers Kirsle.net, is this: for every single request to a page managed by the CMS, the web server has to do work to get the page for you. The main
index.cgi needs to be executed every time (I know, I could use mod_perl, but I haven't gotten around to investigating that option yet).
And really, a lot of pages don't need to be dynamically generated for every single request. A lot of my pages don't change very often. Example: my 3D Renderings page. That page only changes when I change it.
Ideally, then, "static" pages that don't change often should be stored on the web server as a regular old flat HTML page. The server can send these to the browser much more efficiently than having to get Perl involved. But for pages that actually need to be dynamic (e.g. a guestbook page), the server should get Perl involved for that. So with my hybrid-dynamic CMS, I get the best of both worlds. Static pages are compiled once and saved as regular HTML, and dynamic pages (thanks to mod_rewrite) invoke the Perl code and the transition is seamless for the end user's experience.
I won't run Kirsle.net on Kirsle::Nano, though. But I do run my portfolio site on it, and, I figure, next time I build a website for somebody else, I'll use Kirsle::Nano for it as well.
In addition to being a server-side content management system, Kirsle::Nano also allows you to use it as a simple static webpage generator. You can compile all your HTML pages on your own computer, ready for upload to a web host that doesn't support Perl.
I'm releasing this CMS under the Apache 2 license, which means you can use it however you want, just don't delete the notices from the code where it says I was the original author.
There are 0 comments on this page. Add yours.