The instinct to keep the system "small in concept" is the right one, and it's harder to maintain than it sounds — most CMS projects start focused and then bloat themselves into irrelevance trying to be everything. The tell will be how you handle feature requests that are genuinely useful but push against that philosophy. What's already been the hardest "no" to say?
by jeremykalfus
1 subcomments
Interesting concept. You may run into legal trouble with Palantir over the name Foundry if you scale, lol. Otherwise it's cool--website looks way too AI generated IMO.
No hate tho, you got this.
by kimchelgi03
1 subcomments
Interesting approach. Keeping everything as local content without a database is a strong design choice - it makes version control with git trivial and deployment much simpler.