I built a Full-stack Company Website with @boltdotnew and @strapijs using Best Practices
Here is the full tutorial:
❇️ Part 1: https://t.co/wHybrklmvS
❇️ Part 2: https://t.co/TWN873cPEm
You will learn how to:
1️⃣ Use Bolt AI-powered development with Strapi 5 CMS
2️⃣ Build a Next.js company website. Step-by-step tutorial with prompts and examples.
3️⃣ Connect Bolt to Strapi 5 API
4️⃣ Fetch dynamic content
5️⃣ Debug common errors, and deploy to Netlify.
Happy Learning 🥳🚀
What can you actually build with Strapi’s MCP server?
In this tutorial by @JavaScriptar, we will build an AI-powered content assistant using Strapi MCP and the @vercel AI SDK.
It can work with content in Strapi, but that’s just the start.
We also extend the MCP server with custom tools to:
🔎 Research competing content with @SerpApi
🔗 Find related articles for internal linking
🛠️ Check articles for broken internal links
And before the AI makes changes to content, a human can review and approve the action.
It’s a practical look at how MCP, AI models, external tools, and your CMS can work together while keeping humans in control.
Read the full tutorial 👇
https://t.co/hXZZMd53Vm
🇯🇵 Join us tomorrow in Tokyo!
Our own @codingthirty will speak on “Content Infrastructure for the AI Era: Building Experiences for Humans and AI” at “Building the AI-Powered Connected Experience,” alongside @QBurst, LY Corporation, Braze Japan, and JFrog.
AI agents shouldn't replace people. They should make people's work better.
Paul will share how agents can improve the experience on both sides. Customers get fast help, any time, in the chat app they already use. Staff spend less time on routine questions and more time where a person really matters.
The key is keeping humans in the loop. The agent knows when to step back and hand off to a person, and people make the final call on anything important.
The best agentic experience is the one you don't notice. Build for people. Augment with agents.
📍 LY Corporation Office, Akasaka Trust Tower, Tokyo
📅 Tomorrow, October 7
⏰ 4:00 to 8:30 PM Japan time
👉 English: https://t.co/4o0b0H4MQb
👉 Japanese: https://t.co/oFDWuUhkeH
In Tokyo? Come say hello. 👋
@BrianIto_ By the way, we have the Strapi Community Hub where you can share your work with the community and get it listed in the Strapi ecosystem for everyone to discover and use: https://t.co/fhLMVoDs0B
⏰ A Practical Guide to Cron Jobs in Strapi 5
Strapi lets you handle scheduled tasks with built-in cron jobs.
In this guide, @JavaScriptar covers:
⚙️ How to enable and configure cron jobs
🕒 Cron expression syntax and time zones
🧩 Static vs. dynamic cron jobs with strapi.cron.add()
📄 Using the Document Service inside cron tasks
⚠️ Common mistakes and multi-instance deployment gotchas
🛠️ Testing, debugging, logging, and when to use an external job queue instead
👉 Full tutorial: https://t.co/mXnK6PhimC
@Basketimez@BasitOriola That's awesome! 🎉 Building a full-stack project with Strapi as the admin backend is a great way to give clients control over their content. Strapi's flexible content management with a clean frontend is really powerful for this kind of setup. Nice work!
That's a fair frustration. v2 to v5 is a significant jump with a lot of breaking changes under the hood. The good news is we've got resources to make the migration more structured.
We publish dedicated breaking changes documentation for each major version jump, and there's an https://t.co/WjwQG47893 that can help identify what needs updating in your codebase.
We also have https://t.co/tEM0kwGhSy which walks through the process step-by-step.
That said, if the project hasn't been actively maintained and the upgrade effort outweighs the benefit, sunsetting might genuinely be the right call.
But if there's still value in it, the upgrade path is more navigable than it might seem. Happy to help troubleshoot specific blockers if you hit them along the way.
Hi, if you're interested in learning about Strapi's publication filtering and access control features which are relevant to data security you can review:
- https://t.co/56uGQI7BEL
- https://t.co/HcNm8OladF
If you've discovered a genuine security issue, we encourage responsible disclosure through our security reporting channels: https://t.co/hIS9os9n2o rather than public social media announcements. This helps ensure the issue is addressed properly before it's widely known.
Love this approach!
That's exactly how we think about Strapi (@strapijs) too.
it's the flexible headless CMS that works with your frontend of choice.
Whether your clients are building with Next.js, Framer, Webflow, or something else entirely,
Strapi adapts to fit the project's needs rather than forcing a specific tech stack. The best tools are the ones that let you build what's right for the client, not what's trendy. 🚀
Exactly. Native MCP from day one means your content layer and AI integration layer speak the same protocol from the start, rather than requiring retrofit middleware to map legacy patterns onto new use cases.
Strapi's(@strapijs) native MCP support is actually baked in. We have both
- a docs MCP server: https://t.co/A40xK8i0Eh
- and a Strapi MCP server: https://t.co/a6UpMTv2Of that lets AI agents query your content graph directly and work with your schema in real time.
"Love Strapi btw! We're using it for our marketing blog." — @NimrodKramer, CEO at @dailydotdev
https://t.co/IGPz9xotin is a curated feed of developer news, deep dives, and discussions used by millions of developers. And their marketing blog runs on Strapi. 💜
This wasn't a testimonial request — it came up naturally in the comments on one of Nimrod's posts.
We love seeing @strapijs being used by teams building for developers.
Thanks for the love, Nimrod 🙌
👉 Check it out → https://t.co/L2kwETRsdO