Grav VS october

There are flat-file CMSes (content management systems) like Grav: https://getgrav.org/

I guess, in some vague/broad sense, config-as-code systems also implement something similar? Maybe even OpenAPI schemas could count to some degree...?

In the old days, the "semantic web" movement was an attempt to make more webpages both human- and machine-readable indefinitely by tagging them with proper schema: https://en.wikipedia.org/wiki/Resource_Description_Framework. Even Google was on board for a while, but I guess it never saw much uptake. As far as I can tell it's basically dead now, both because of non-semantic HTML (everything as a React div), general laziness, and LLMs being able to parse things loosely.

-------------

Side thoughts...

Philosophically, I don't know that capturing raw data alone as files is really sufficient to capture the nuances of any particular experience, or the overall zeitgeist of an era. You can archive Geocities pages, but that doesn't really capture the novelty and indie-ness of that era. Similarly, you can save TikTok videos, but absent the cultural environment that created them (and a faithful recreation of the recommendation algorithm), they wouldn't really show future archaeologists how teenagers today lived.

I worked for a natural history museum for a while, and while we were there, one of the interesting questions (well, to me anyway) was whether our web content was in and of itself worth preserving as a cultural artifact -- both so that future generations can see what exhibits were interesting/apropos for the cultures of our times, but also so they could see how our generation found out about those exhibitions to begin with (who knows what the Web will morph into 50 years later). It wasn't enough to simply save the HTML of our web pages, both because they tie into various other APIs and databases (like zoological collections) and because some were interactive experiences, like games designed to be played with a mouse (before phones were popular), or phone chatbots with some of our specimens. To really capture the experience authentically would've required emulating not just our tech stacks and devices, among other things.

Like for the earlier Geocities example, sure you could just save the old HTML and render it with a modern browser, but that's not the same as something like https://oldweb.today/?browser=ns3-mac#http://geocities.com/ , which emulates the whole OS and browser too. And that still isn't the same as having to sit in front of a tiny CRT and wait minutes for everything to download over a 14.4k modem, only to be interrupted when mom had to make a call.

I guess that's a longwinded of critiquing "file over app": It only makes sense for things that are originally files/documents to begin with. Much of our lives now are not flat docs but "experiences" that take much more thought and effort to archive. If the goal is truly to preserve that posterity, it's not enough to just archive their raw data, but to develop ways to record and later emulate entire experiences, both technological and cultural. It ain't easy!

I took a more traditional approach, focusing on something that's "good enough", which in my case was a cheap VPS and an install of Grav: https://getgrav.org/

Some optional customization for page templates/fonts/CSS, some CI so I can build and deploy it inside of a Docker container, Matomo for analytics that respect privacy (which I already use elsewhere) and some additional web server configuration to hide anything interesting behind an additional login and I'm good. Maybe backups and uptime monitoring if I'm feeling brave, which is what most sites should also have (so copy + paste there).

All of that for under 100 euros per year (could also pay half of that if I didn't host anything else on the server), the blog has actually survived getting on the front page of HN once or twice and requires relatively little maintenance, at least a bit less than a proper install of WordPress, due to its larger surface area.

The best thing is that it's simple enough for me to understand how it works, to be able to move it anywhere as needed and use more or less plain Markdown for writing the blog posts. Here's a quick example of a recent post: https://blog.kronis.dev/articles/ever-wanted-to-read-thousan...

Now all that's left is to find motivation to write more, but at least 90% of my time doesn't go into tinkering with custom fancy solutions, no matter how much I'd love that. Then again, nothing wrong with the alternatives either: 400 euros might be perfectly worth it for some, whereas working with static site generators or even custom CMSes would be a fun experience for others!

I'd check out Grav. https://getgrav.org/

Also, there is a CMS called Grav. Both Gravity and Grav use a very similar (but not identical) font for their logo.

I would use a flat file cms like https://getgrav.org

git clone https://github.com/octobercms/october.git your-website

It's not a WordPress clone but I've been wanting to check out October CMS for a while and just noticed this Twill project that looks like it would be along the same lines.

If I was to go for a blog platform, I'd opt for https://octobercms.com

Beside Symfony there is Laravel Framework , I will not go into deep difference between this frameworks as it really is just taste of what your team likes more (active record vs datamapper, facade/helpers vs dependency injection, blade vs twig, ...), as already mention above this kind of CMS make sense if Website is just one part of your application and you have to build more then just a simple digital business card / website. In Laravel world there are CMS like October CMS / Winter CMS, which target the same providing a CMS based on the Full Stack Larave framework and give you all features of that framework. Another already mention CMS in Laravel world is Statmatic.

October CMS

How comfortable are you with learning PHP? WordPress is the obvious choice due to it's popularity (but with it moving towards a full-site editing experience it isn't as fun to work with anymore IMO but that's just me). You could also look into things like Statamic or October CMS which are supposed to be very nice to work with as i believe they're both Laravel based.

As u/frontendben said, you can use Statamic CMS, it is a decent solution, and there are a number of others like October CMS, Asgard CMS (a bit old, but quite solid), LavaLite, Pyro etc. Craft CMS (based on Yii) could also be a possibility. Here is a list of someone's opinions on 5 popular Laravel-based CMSs.

I've used OctoberCMS[1] for a smaller project, and this looks similar on first glance. (Might just be the Lavarel underpinnings.)

What I really like about October is the ability to quickly spin up small CRUD database functionality (index + detail pages and simple backend updates for "custom" objects like staff members, white papers, etc.) using their Builder plugin. Any idea if Statamic offers something similar without diving into custom code?

However, October seems to be a little stagnant: you search, and most of the forum discussions are from 2016, and many plugins are no longer maintained well.

[1] https://octobercms.com/