Saturday, February 02, 2002

Well, the big difference between Radio and BigFrog is that Radio is first a blog, and BigFrog is first a CMS.  Stories rather than weblogs.  At least initially.  After a long cold spell, Los Angeles has warmed up.  Spent a hour clipping away some old bushes and plants.  Decided to make it easy to edit in BigFrog.  Speed (caching) is easy to add on with my design... premature optimization is the root of all evil. 11:38:14 AM

What's more important, natural editing or speed?  The less PHP is involved, the better.  Fastest implementation is to only render PHP on cache miss -- on cache hit, PHP will put page together and save it to disk.  Question is, should page be servered by apache directly meaning there's a seperate editing interface, or should PHP just include the cache page and add a little editing bar for those with the correct cookie?? 9:37:05 AM

I've been meaning for the last two years to write my own CMS, but I get easily sidetracked.  Having a two year child doesn't help matters, and #2 is on the way... I've written 2 CMSes at work, too.  They're lots out there, and I've tried a few including CityDesk, CuteSiteBuilder (aka Trellix) and Radio.  I like Radio best so far, but the problem is I don't have enough to write about.  Plus, I need to find my blog voice.  So what better way than to document my very own CMS.  How is it going to be different -- it's not going to be a desktop app.  It's going to be written in the holy trio, apache/php/mysql, and will live on the server.  Might need a little java later on to have some sort of drag&drop ftp for easily posting images...   12:18:14 AM