Show HN: A big tech dev experience for an open source CMS

58 点作者 randall2 个月前

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]: <a href="https://www.anthropic.com/research/constitutional-ai-harmlessness-from-ai-feedback" rel="nofollow">https://www.anthropic.com/research/constitutional-ai-harmles...</a>[Isograph]: <a href="https://isograph.dev" rel="nofollow">https://isograph.dev</a>[Replit]: <a href="https://replit.com" rel="nofollow">https://replit.com</a>[Sapling]: <a href="https://sapling-scm.com" rel="nofollow">https://sapling-scm.com</a>[Show HN post in 2013]: <a href="https://news.ycombinator.com/item?id=6993981">https://news.ycombinator.com/item?id=6993981</a>[remix our Replit app]: <a href="https://replit.com/t/bolt-foundry/repls/Content-Foundry/view#README.md" rel="nofollow">https://replit.com/t/bolt-foundry/repls/Content-Foundry/view...</a>[join our Discord]: <a href="https://discord.gg/TjQZfWjSQ7" rel="nofollow">https://discord.gg/TjQZfWjSQ7</a>

10 条评论

jmuguy2 个月前

Maybe its just me but I can't figure out what exactly this is. I tried your demo, gave it a Twitter user. And its now generating blog posts in the "voice" of that Twitter user? And this is a tiny first step to... what? I know this sounds antagonistic but I'm just genuinely confused.

评论 #43292683 未加载

rbalicki2 个月前

I'm incredibly excited for this launch! Bolt Foundry is the first company to use [Isograph], which is a framework for building data-driven apps that are performant and stable out of the box. It does so by making heavy use of a compiler and of generated files, and essentially being an incremental computation engine for your UI. Your UI becomes performant by doing the least amount of unnecessary work.And Bolt Foundry is truly the perfect first adopter! As "A big tech dev experience" implies, they're very focused on providing great DevEx. And a bunch of them previously worked at Meta, where they used Relay, and understood the powers that it provides.Isograph aims to provide an even better developer experience (see the YouTube link), and give you the things that previously were only feasible at FAANG-co scale: e.g. even in a very dynamic app, fetching just the JavaScript and data you end up using.So far, they've had a great experience using Isograph!! You should also [give it a try] or [contribute].[Isograph]: <a href="https://www.youtube.com/watch?v=sf8ac2NtwPY" rel="nofollow">https://www.youtube.com/watch?v=sf8ac2NtwPY</a>[give it a try]: <a href="https://isograph.dev/docs/quickstart" rel="nofollow">https://isograph.dev/docs/quickstart</a>[contribute]: <a href="https://github.com/isographlabs/isograph">https://github.com/isographlabs/isograph</a>

graypegg2 个月前

Interesting! I think the idea of a "tone" in your content being enforced by a sort of... prose linter makes a lot of sense.You can assume 1 person with at least some practice in writing will have a clear tone and presence in the things they write, but this would be rather useful for corporate communications, especially when simpleton engineers (such as myself) try to write blog posts for a company engineering blog. If there was something nudging me towards the style of the blog, without steam rolling me constantly by rewriting everything, I would like that.For the CMS, (I think you're building a CMS?) I think building around THAT use case would be an awesome selling point. Let content folk spawn special ephemeral links that let someone write up a draft without having to set up an account. Have some sort of approval process in there too, that could be configured on that "magic link", so I don't impulsively publish to everyone.Make it super easy to just stumble into writing something the company can actually communicate with, right away. There's a lot of passionate people at companies, with 0 writing experience that would lend a lot of authenticity to blogs/engineering comms/recruiting ads, if they they had the bumpers in their bowling lane.

评论 #43292971 未加载

652 个月前

What's so difficult about just writing a blog post yourself, in your own writing style? What's so wrong about pure human expression?

评论 #43293263 未加载

Etheryte2 个月前

For your consideration, the main page you've linked to is nearly unusable on mobile, might want to look into that.

评论 #43292531 未加载

评论 #43292535 未加载

__MatrixMan__2 个月前

I think this is interesting in sort of a scifi way because if you can establish a reliable enough characterization of "tone" then maybe you can then create a steganographic side channel out of deviations from that tone: so your adversaries see inane blather about something unimportant, but your comrades can decode the blather into more meaningful messages. Meanwhile, others are hosting your communications for free because what is actually cyphertext appears to them as engagement.

评论 #43294917 未加载

MSFT_Edging2 个月前

With the constant deluge of AI slop everywhere, your voice is basically all you have.This is basically a tool to train a computer to "steal" your voice. I find that sad.Why can't we figure out how to use this technology in something other than creative tasks? I don't care what anyone says, a blog post showing off some technology or accomplishment should be a creative task, otherwise what's the point?

评论 #43293234 未加载

jpc02 个月前

I'm not sure how, but the text is miniscule on Safari on iOS and causes reader mode to need to scroll horizontally by nearly double the page width.I am going to slog through it but I would recommend checking on mobile Safari in the future.

评论 #43292706 未加载

评论 #43292710 未加载

评论 #43292689 未加载

mediumsmart2 个月前

This is great! Assuming the LLM versions of me will build their fake consumer clones believably. Once this goes FAANG-co scale it will only be a couple of months until we can all go public and Advertisers will stop buying ads putting an end to the enshittification of the interwebs. Genius. Who came up with this? ... and is Apple likely to sue considering their patent from 2012?

ThinkBeat2 个月前

um what?That did not seem cohesive.I am all for new and better content management systems, and like all geeks written at least two of them, but what is our plan for the CMS?Making a Twitter card does not seem that relevant?Am I stuck on the wrong CMS interetation?Why/How will this be different than WordPress? (or any ohter)

评论 #43296398 未加载