Story engine

I’ve always loved the simplicity and pleasantness of whatever must be under the hood of Elf’s stories — he seems to have easy management of story arcs, multiple sortings of stories, multiples sets of stories, next and previous buttons within stories, etc.

I’m debating how I want to build my own little story engine. Right now, my stories are in WordPress, published as page. One avenue I could take would be to write a WordPress plugin to allow me to manage stories the way I want — keep them as pages, but add the fluff I want.

Another avenue would be to roll my own — make a separate little system in Python or Ruby, whatever. Not a web-based system, but a system that just parses the stories into HTML files based on when I want them published, and lets me do all the features above. Have it run daily as a cron job.

I don’t know how much I want to tie myself to the WordPress monolith — for instance, it’d be nice to have the pages be static HTML without explicit caching. But a WordPress plugin would be something others might be interested in.

Then again, mucking around in other people’s code is likely to be messy. And less fun. And still in PHP.

Sounds like I may do the standalone system.

2 thoughts on “Story engine”

    1. It’s… normal. I sling PHP to some extend almost every day, and it’s humdrum to me, although perfectly appropriate for something like this. It’d be nice polish up my Ruby skills a bit with this — something not in Rails.

Comments are closed.