Show HN: QuickBEAM – run JavaScript as supervised Erlang/OTP processes (github.com)
28 points by dannote a day ago | 3 comments
30 points by nsayoda 2 days ago
Hi HN! I've been building a CMS called Foundry, brought together from multiple smaller private projects as well as greenfield code.
The short version is: it's a CMS written in Go with a focus on markdown content, a simple hook-based plugin model, themes, archetypes, preview flows, and a clean authoring/developer experience.
I started working on it because I wanted something that was more powerful than Hugo for a few of my websites, without having to resort to dangling onto a database.
What seems different about it, at least to me, is that I'm trying to keep the system small in concept: local content, explicit behavior, compile-time plugin registration, and an admin/editor layer that is meant to stay close to how the content actually lives on disk. The goal is not to make "yet another website builder", but to make a CMS that is easy to use and quick to onramp onto, but has powerful advanced features and extensibility.
Still early, but usable enough that I wanted to put it in front of people here and get feedback. Please don't castigate me on the UI look - I'm not a designer, and the themes are basically clones of each other.
Happy to answer technical questions, architecture questions, or hear where this seems useful versus where it does not.