Aurélien | Strapi.io

What an exciting day! We just announced 👇 ➡️ v4.1.5 with in-app marketplace ➡️ v4.2 (beta) with dark mode & @typescript support ➡️ Custom fields RFC ➡️ Strapi Cloud (strapi.io/cloud) #strapiconf

This guy made 40 Facebook ads, 100 landing pages, booked himself on 4 podcasts, and wrote 3 guest blog posts. In a single day. People called him a fraud. There was literally a Polymarket bet on whether he's a con artist. So i asked him to prove it live. And he did. Here's @codyschneiderxx's actual system for AI-enabled paid marketing: 1) He uses Perplexity to search Reddit for his ICP's actual pain points in their own words. Not what he thinks they care about, what they've literally said online. 2) He feeds those pain points into Claude, which generates 40 ad variations, titles, supporting copy, and the actual creative using React components exported as PNGs via a library called HTML-to-canvas. 3) He tests all 40 variations in a CPC campaign on Meta. $100 over 3 days. Cheapest cost-per-click wins. 4) Winners get matched landing pages. He uses an open-source CMS called Strapi connected to Claude Code via API, so he bulk-generates a landing page for every winning ad angle. Same headline on the ad and the page = higher conversion. 5) Once he finds a winning concept, he scales it — AI avatar UGC via HeyGen, upgraded with V3, and only brings in a human creator if the AI version plateaus. The whole thing runs on Claude Code + APIs + a .env file with all his keys. No engineering team. Just him on multiple desktops with multiple Claude agents running simultaneously. His best line: "you're not just hiring me anymore. you're hiring me and the 30 agents behind me and all the personal software i've built."

Since the early days of @liveblocks, we've wanted to open source our server stack. Today we're doing it. We're releasing @​liveblocks/server, the core technology behind our WebSocket infrastructure. It's a realtime data storage and presence server compatible with two sync engines: Liveblocks Storage and Yjs. Built on the foundation @guillaume_slls started 5 years ago. One command to run it locally: $ npx liveblocks dev

🚀 Strapi v5.36.0 is out, and it's all about Quality and Community This release improves daily workflows in the admin and adds a few meaningful DX upgrades. What’s new: ✨ Persistent list view settings in the Content Manager: filters, sorting, and display preferences now persist, so you don’t have to reset your view when navigating away 📱 Mobile improvements in edit views for a smoother experience on smaller screens 🧰 Better TypeScript support for project configuration ☁️ Upgraded S3 upload provider: improved compatibility with S3-compatible services (MinIO, DigitalOcean Spaces, Backblaze, IONOS, etc.) plus security enhancements 🔄 --non-interactive mode for improved CI/CD and scripted project creation 🔒 Security update: Apollo upgraded to 4.13.0 ⚙️ Bug fixes & polish: improvements to content history drawers, sidenav scrolling, relation cloning, and async preview handling About 50% of the work in this release comes from community contributions. Thank you to everyone who reported issues and submitted PRs 🫶🏻

@daytonaio @FirstMarkCap HUGE!!

Today, Daytona is announcing a $24M Series A, led by @FirstMarkCap, to give every agent a computer. This round reflects what the market is increasingly concluding: the cloud was not built for agents. Full announcement 👇

Today, Fimo.ai is officially live 🚀 The sleek new #websitebuilder – powered by an #AI-native CMS – is brought to you by the minds behind @strapijs, the world's leading open source #headlesscms Read our review👉tinyurl.com/mtdwnpz4

Fimo.ai is live on ProductHunt. Upvotes appreciated 😊 producthunt.com/products/fimo-…

@pierre_burgy @jasonlk @HarryStebbings Our only goal is to have @jasonlk mention other vibe-coding tools than Replit on 20VC ahah

@jasonlk @HarryStebbings Here we are @jasonlk: x.com/pierre_burgy/s… Creating and managing websites will never be the same. Can't wait to hear your feedback (and give a talk about it at SaaStr)!

Wordpress powers 40%+ of the web Loveable and Replit are targeting that market and more. But they get to charge you $25/month and for every token you use. Wordpress in its most basic form is free outside of hosting, etc. That is a large market. Much as ChatGPT gets to charge for what Google provides for “free” … Loveable + Replit get to charge for what Wordpress provides in many cases for free or very cheap. That adds up to a lot of money, very quickly AI is getting us to pay a lot for what we used to get … for free. For more value, no doubt. But a lot more than we used to.

A successful Series B stage company launching a new AI product. Yep, this is exactly what we are doing 🤯 Meet Fimo.ai An AI-native CMS to build websites in minutes. Existing vibe coding tools are great for building apps, but websites have specific requirements.

Building a website used to take months. I created 5 in 10 seconds. Meet Fimo.ai, an AI-native CMS where your website lives, collaborates, and evolves with AI. Existing vibe coding tools are great for building apps, but websites have specific requirements. We’ve spent the last 10 years building Strapi, the most popular open-source Headless CMS. We know what is important for users: translate content, reuse assets, optimize SEO/GEO, update content, A/B test, personalize pages, schedule releases, review workflows, etc.

Bye 2025, Hello 2026. I have something to tell you. @Atinux @tannerlinsley @kentcdodds @wesbos @stolinski

This is the best article I’ve read in months. Highly recommend this 5 minute read.

It’s time to revisit what a CMS can do and what the experience should feel like. Our vision is bold. Our mission stays the same: Empower millions of people to create and share content

Using a CMS should feel like hiring a team of growth engineers working 24/7 on your website. No ego. No noise. Just impact. And still: full autonomy, full control over what you build. 3/4

CMSs aren't dead. They're evolving. AI is everywhere. And a new application layer is emerging. A modern CMS shouldn’t just manage content. It should actively empower you. Comment FOMO for early access! 1/4

The CMS is dead. Long live the CMS! AI is changing the rules in every industry. The CMS is no exception, especially as it is at the intersection between developers and marketers, which are two of the most disrupted roles (code generation and content generation). @leerob (VP of DevRel at @cursor_ai, ex-@vercel) published a great piece of content about their migration from a proprietary, restricted, Headless CMS to a fully Markdown file-based workflow. And he is right (on some aspects): agents are excellent at editing both code and (content) files at the same time, as they can easily get both in context, especially in a great AI code editor like Cursor. Markdown files are great for small projects. We’ve seen a lot of “git-based” CMS emerging over the past years. However, none of them has been successful for large-scale projects: Requires a deployment every time there is an update Data inconsistency Unable to have relations between content types Too technical for non-devs But what we are talking about is worse than that. It is a no-CMS approach. We’ve been there, done that: The first version of our own website was all about hard-coded content in a good old EJS template (yes, that was before React!) and a big JSON file containing all of the (5 or so) blog posts. We were 3 developers, editing files was easier and faster than setting up a CMS. The Cursor team is very specific, as they are a team of engineers (which makes total sense for a code editor company). It is great, until it is not. CMSs have been invented because non-technical people need to edit their websites without needing to reach developers. CMSs bring the structure and features any serious project needs: - Relations management - Content internationalization - Content scheduling (aka releases) - Content history - API tokens - Webhooks - Integrations - Authentication - Custom fields - Media library - Role management - Review workflows - Security (Single Sign-On, Audit Logs, etc.) With all of this being said, I think the most important insight Lee shared in this post is the agentic approach to building content: everybody deserves to ask for website updates in plain English, and agents must be able to do this autonomously. That means: - CMSs must be agentic - Agents must easily communicate with each other, or everything must sit under one single tool: frontend code, CMS, hosting, and more This is exactly why: - We launched Strapi AI - We are about to release Strapi MCP - TEAAAASING: Over the last eight months, we have developed a brand-new product that addresses all the issues mentioned above. Comment “FOMO” to get early access, and I will send you the link Stay tuned!

Delighted to meet one of our favorite Strapi Cloud customers: coderabbit.ai! 🐇 @coderabbitai decided to use @strapijs for its main website because it is open-source and highly flexible. We look forward to using CodeRabbit on the Strapi open-source @github repository to merge even more pull requests from the community! @aravindputrevu @reidRMC @aureliengeorget

Meetup alert! Based in SF or attending Next.js Conf? Join us on October 21: - Using the @MuxHQ MCP to dynamically analyze video content for AI-driven tagging and content moderation by @joshalphonse - Build your own CodeGen platform by @andrelandgraf, Member of Technical Staff, @neondatabase @databricks - Docs are product: how we write (and use) docs at Replit by @mattyp, @Replit - Context Engineering: How We Ground Seer in Reality by Ram Senthamarai, Senior Machine Learning Engineer, @getsentry - What We Learned from Building a Vibe Coding Tool, by myself @vcoisne @aureliengeorget @strapijs

Strapi’s October Platform Update is LIVE🚀 Our biggest drop yet — built to boost developer speed and free up content teams. ✨ Here’s what’s new: 🔹 AI content type builder (just type your schema) 🔹 Auto alt-text & image captions 🔹 OpenAPI spec generation 🔹 Real-time live preview 🔹 Cloud upgrades: project transfers, backups, env sync & more 🔗 Full update: strapi.link/4q1DZB8