A big tech dev experience for an open source CMS
Hey HN! We're building an open-source CMS designed to help creators with every part of the content production pipeline. We're showing our tiny first step: A tool designed to take in a Twitter username and produce an "identity card" based on it. We expect to use an approach similar to [Constitutional AI] with an explicit focus on repeatability, testability, and verification of an "identity card." We think this approach could be used to create finetuning examples for training changes, or serve as inference time insight for LLMs, or most likely a combination of the two. The tooling we're…
In plain words
Content Foundry is an open-source CMS platform designed to help creators manage the full content production pipeline. The team has released an initial tool that generates identity cards from Twitter usernames using a Constitutional AI approach, emphasizing repeatability and testability. The system is intended to support both model finetuning and inference-time insights for language models. The project prioritizes developer experience and community contribution, aiming to provide a more accessible alternative to existing content management systems.
written from the facts on this page · September 2026
From the sources
In the maker’s words, at launch
Hey HN! We're building an open-source CMS designed to help creators with every part of the content production pipeline. We're showing our tiny first step: A tool designed to take in a Twitter username and produce an "identity card" based on it. We expect to use an approach similar to [Constitutional AI] with an explicit focus on repeatability, testability, and verification of an "identity card." We think this approach could be used to create finetuning examples for training changes, or serve as inference time insight for LLMs, or most likely a combination of the two. The tooling we're showing today is extremely simplistic (and the AI is frankly bad) but this is intentional. We're more focused on showing the dev experience and community aspects. We'd like to make it easier to contribute to this project than edit Wikipedia. Communities are frustrated with things like Wordpress, Apache, and other open source foundations focusing on things other than software. We have a lot of community ideas (governance via vote by jury is perhaps the most interesting). We're a team of 5, and we've bounced around a few companies with each other. We're all professional creators (video + music) and we're creating tooling for ourselves first. Previously, we did a startup called Vidpresso (YC W14) that was acquired by Facebook in 2018. We all worked at Facebook for 5 years on creator tooling, and have since left to start this thing. After leaving FB, it was painful for us to leave the warm embrace of the Facebook infra team where we had amazing tooling. Since then, we've pivoted a bunch of times trying to figure out our "real" product. While we think we've finally nailed it, the developer experience we built is one we think others could benefit from. Our tooling is designed so any developer can easily jump in and start contributing. It's an AI-first dev environment designed with a few key principles in mind: 1. You should be able to discover any command you need to run without looking at docs. 2. To make a change, as much context as possible should be provided as close to the code as possible. 3. AIs are "people too", in the sense that they benefit from focused context, and not being distracted by having to search deeply through multiple files or documentation to make changes. We have a few non-traditional elements to our stack which we think are worth exploring. [Isograph] helps us simplify our component usage with GraphQL. [Replit] lets people use AI coding without needing to set up any additional tooling. We've learned how to treat it like a junior developer, and think it will be the best platform for AI-first open source projects going forward. [Sapling] (and Git together) for version control. It might sound counter intuitive, but we use Git to manage agent interactionsand we use Sapling to manage "purposeful" commits. My last [Show HN post in 2013] ended up helping me find my Vidpresso cofounder so I have high hopes for this one. I'm excited to meet anyone, developers, creators, or nice people in general, and start to work with them to make this project work. I have good references of being a nice guy, and aim to keep that going with this project. The best way to work with us is [remix our Replit app] and [join our Discord]. Thanks for reading and checking us out! It's super early, but we're excited to work with you! [Constitutional AI]: https://www.anthropic.com/research/constitutional-ai-harmles... [Isograph]: https://isograph.dev [Replit]: https://replit.com [Sapling]: https://sapling-scm.com [Show HN post in 2013]: https://news.ycombinator.com/item?id=6993981 [remix our Replit app]: https://replit.com/t/bolt-foundry/repls/Content-Foundry/view... [join our Discord]: https://discord.gg/TjQZfWjSQ7
More ai this month
the category →
I trained a 125M-parameter transformer to autocomplete piano performances in real time (~108 notes/sec on an iPhone 15). The idea is basically GitHub Copilot or Tabnine, except instead of prompting it with code, you prompt it by playing a few notes on a MIDI piano. The model then continues what you played, entirely on-device. The app is free if anyone wants to try it. Happy to answer questions about the model, training, Core ML, or the many things that didn't work.
AI · 17d ago · simedw.com
Astute▲585Automate your B2B brand going viral, with new media creators
AI · 18d ago · company-app.joinastute.com
Hey HN, Henry from Cactus here! We previously released Cactus Needle, a 14MB agentic LLM for tool call, device use, and structured extraction for phones, wearables, smart homes, small robots and microcontrollers. We got really great feedback here, and have now incorporated the suggestions to release Needle 2. The whole model is a single 14MB binary that runs a full session in 28MB of RAM; 45m parameters at 2bit compression. Needle hits 500 tokens/sec decode speed on a Raspberry Pi 5, sits between 400-1,500 tokens/sec on VR devices like Meta Quest 3S and Apple Vision Pro, and ranges…
AI · 26d ago · cactuscompute.com
Launched alongside, March 2025
the whole month →
Mimic Human Research & Save Findings in AI Knowledge Base
AI · 2025 · sider.ai
