3 ms·
I've thought an idea like this could be used for more than just a blog (and maybe it is in certain cases). Rather than pulling up the pages every time, have a
by dabent 17y ago
I've thought an idea like this could be used for more than just a blog (and maybe it is in certain cases). Rather than pulling up the pages every time, have a build process merge content and a template to form HTML pages. It could be used on sites that are potentially huge, but render an ultra-fast site with thousands of pages.
The only trick is to integrate that with comment forms and the like. But even that isn't too hard to code around.
- andrewvc 17y agoI'm currently making a dynamic rewrite of a legacy CMS written to generate static files. The static CMS is a huge PITA. Yeah you can slip dynamic features in there 'just' where you need them. What you wind up with is a mess, and once your site gets a lot of content you start generating a LOT of files. Our rebuild process can take a couple hours, and while it does that it's pegging the disk. There's nothing wrong with static sites, for something like a blog it's OK. The feature set is fairly limited. But once you do want to add dynamic stuff, it can get tricky. I'd say for most projects starting with a static generator is a mistake because unless you know for sure the requirements won't change you can easily paint yourself into a corner.