Looking to migrate from #Forestry because of being stuck on a discontinued CMS that’s no longer maintained?
Here’s tldr where BCMS is better:
- Visual modeling without YAML config files
- Native REST & GraphQL APIs
- Native MCP support & open BCMS agent skills
Full comparison here: thebcms.com/compare/forestry…
Introducing Eventually.
There are more useful threads, ideas, tools, and references on X than we could keep up with daily. I wanted a way to save the good stuff without letting it disappear into a pile of bookmarks I never open.
Eventually is exactly that: it backs up your X bookmarks and emails them back to you like a personal newsletter, on whatever schedule fits you. Mine is every day at 9am.
BCMS retweeted
Top headless CMS
Happy to show you the new BCMS website! Rebuilt with Next.js from the ground up.
Hardly any visual on this site is a static image... everything is an interactive part of the real BCMS interface! Hope you enjoy finding all the Easter eggs!
thebcms.com
I just had an idea: what if I move the entire Tailwind config into @thebcms?
Every single thing: colors, fonts, spacing, shadows, border radius... all of it... and then just consume those values on the site.
Why??? ----------> why not???
It's possible, and apparently even a less powerful model can do it in ~2 minutes
youtube.com/watch?v=NhvZ-qTC…
I just had an idea: what if I move the entire Tailwind configuration into @thebcms? Every single property: colors, fonts, spacing, shadows, rounded corners... everything... and then consume those values on the site.
Why??? ----------> why not???
It's possible, and apparently even a less powerful AI model can do it in ~2 minutes
BCMS retweeted
I've started a Tools section on HTMLrev. It's dedicated to high quality premium web design and development tools. No free resources. Premium books and courses are welcomed too. Want something listed? DM me
I tested a workflow where @cursor_ai reads selected @figma pages through the Figma MCP, figures out the content structure, then uses the @thebcms MCP to create templates, groups, entries, and media inside BCMS...
The result is (still) not perfect, but it gets weirdly close. It can turn a real website design into a working CMS structure, with reusable content, property fields, sample entries, and uploaded images - before writing the actual frontend
This is especially useful in the early phase of building a website, when you need to decide what should be editable, reusable, structured, and client-friendly
BCMS retweeted
UI/UX Designers, you can now access 263+ animated icons that actually move with intent.
I just found this amazing tool called Itshover, a growing collection of beautifully crafted open-source animated icons designed to make interfaces feel more alive and engaging.
Can’t believe it’s free; bookmark it for later. 💜
"List all draft blog entries and summarize them"
typed that into our CMS this morning. had the full picture in under a minute.
A year ago this was a spreadsheet everybody should updated + a monday status meeting for years.
AI writing blog posts is fine I guess. but AI that lets you actually see your whole content pipeline, what's stalled, where the gaps are? that's the part I am excited about.
one of the most powerful parts of @thebcms
Replying to @thebcms
@thebcms is now live on ClawdHub too clawhub.ai/user/bcms
I've been shipping BCMS + AI features for months. And only today I realized I had never once tried plugging BCMS MCP into ChatGPT itself.
Turns out: paste a URL, done.
Three combos I tested in the last 2 hours that I loved:
1. Ahrefs MCP + BCMS MCP - find new keyword opportunities for our existing articles in BCMS in the "travel" category
2. Linear MCP + BCMS MCP - plan an article, scaffold internal links, and file the asset tasks in one pass.
3. BCMS MCP alone - "find every blog post where we could naturally mention [new feature]" → actual usable list & placements.
Full walkthrough + more ideas:
thebcms.com/blog/bcms-mcp-an…
been using @thebcms MCP internally for about a month now: creating entries, updating content, all through prompts in cursor. Kind of obsessed!
looking for 10 testers before we go public. supports cursor, claude code, vs code, windsurf + more.
drop a 🙋 if you want early access
Justo estaba analizando cómo encarar el tema en @mostradorcito así que aprovecho para responder:
Opensource y completo, podés usar @payloadcms, @vercel tiene buena integración.
Si querés algo más simple, rápido de implementar, markdown y accesible en precio: @collected_notes de @gptcrosa, me gusta especialmente la posibilidad de crear notas (post) a través de su cli, por lo que podrías armar un flujo de trabajo con tu IDE o terminal para crear contenido desde ahí.
Si buscas un headless CMS con más funcionalidades: @thebcms es relativamente nuevo y tiene un modelo de precios muy bueno (si creás tu cuenta antes del 17 de febrero te queda gratis).
Después los clásicos de siempre como @strapijs, @sanity_io, entre otros.
BCMS retweeted
Ayer consulté por acá qué Headless CMS recomendaban... y aunque @payloadcms ganó casi todos los votos, me decidí por @thebcms.
¿Por qué? Porque no quería lidiar con mantenimiento de backend e infraestructura.
Buscaba algo 100% cloud, económico y funcional para pocas cosas:
👉 Crear contenido en un blog en español e inglés.
👉 Crear eventos con propiedades de contenido específicas.
Con Payload pueden hacer mucho más y con más flexibilidad... pero a veces hay que saber decir que no cuando premia la simpleza.
Les cuento la experiencia (me llevó medio día hacer todo):
1) El proyecto ya estaba en @astrodotbuild, así que abrí Cursor y arranqué desde ahí.
2) Sin conocer TheBCMS, leí la documentación. Como ya había usado Headless CMS, me familiaricé rápido con el funcionamiento general.
3) Armamos un plan para añadir Eventos: creamos el template en BCMS y configuramos la API para consumir las entradas.
4) Integré @thebcms con @astrodotbuild usando los tipos TypeScript que genera automáticamente. Todo funcionó bastante bien desde el inicio.
5) Configuré un webhook en @vercel que recibe updates cuando hay nuevo contenido y ejecuta el build/deploy automáticamente.
Lo que más me gustó:
✅ Setup en minutos (no necesitas servidor)
✅ Tipos TypeScript generados automáticamente
✅ Multiidioma nativo sin configuración extra
✅ API simple y clara
✅ Precio accesible para cualquier proyecto
Resultado:
El cliente puede gestionar blog y eventos desde una interfaz amigable, y cada cambio se deploya automáticamente. Sin preocuparme por servidores, bases de datos o mantenimiento.
A veces la mejor herramienta no es la más poderosa, sino la que resuelve tu problema sin complicaciones.
¿Alguien más con ganas de mejorar x100 sus sitios web con este tipo de tecnologías?
En la screenshot pueden ver cómo se ven los eventos publicados 🍻
BCMS retweeted
Meu irmão precisa de um blog, to testando @astrodotbuild com @thebcms pra ver se é bom e serve










