Thanks, HAOYU! I appreciate the support. If you get a chance, feel free to check out the live demo and let me know your thoughts. Always happy to hear feedback from fellow developers. 🚀

Great questions, Priya — thanks for the thoughtful feedback! Regarding headless usage, SHONiR CMS is currently designed as a traditional CMS, but its architecture (built on CodeIgniter 4) makes it quite flexible. It’s definitely possible to expose content through APIs and use it with a React or other frontend frameworks, and a more formal headless-style integration is something we’re considering as the project evolves. You’re right about the GitHub repository — the full source will be published on March 17, 2026, but in the meantime you can explore the live admin panel demo here: Admin Panel: https://8.shonir.com/shonir-cms/Users Login Credentials Access Key: shonir Username: demo@example.com Password: 923333336426 That should give you a feel for the content editing workflow and day-to-day admin experience. And yes — CodeIgniter definitely has a nostalgic reputation, but CodeIgniter 4 is a very different beast compared to the older versions many of us used years ago. It’s modern, lightweight, and surprisingly powerful for building scalable systems. If you get a chance to try the demo, I’d love to hear your thoughts or suggestions! 🚀

Thank you! I’m glad the guide helped make the initial setup clearer. The .env configuration is definitely one of the most important steps when running SHONiR CMS locally, so I tried to make that part as straightforward as possible. SHONiR CMS is designed to stay simple for small projects while still being flexible enough to handle more complex content structures. The admin dashboard demo should give you a good idea of how it manages pages, categories, and dynamic content. If you test it on your project and have any feedback or suggestions, I’d really love to hear your experience. Contributions and ideas from developers help improve the project a lot. Thanks again for checking out the repository and tutorials! 🚀

Thanks, Nube Colectiva! 🙌 Absolutely—PHP 8 has made a noticeable difference, especially with the JIT improvements and better type handling. Pairing it with MariaDB really helps keep things lightweight and fast. Glad to hear you’ve had positive experiences with this stack too!

Thanks a lot for the kind words! 🚀 That’s exactly what we’re aiming for with SHONiR CMS — making open-source tools approachable and practical so developers can adopt them quickly. Clear guides and real-world examples are the bridge between curiosity and actual implementation. We’d love to see more AI/ML and frontend experts like your team explore SHONiR CMS and even contribute — open-source thrives on collaboration.

SHONiR CMS isn’t trying to be another WordPress clone, nor a Strapi/Directus replacement. Its differentiator is performance‑first architecture in PHP: multi‑CDN integration, environment‑driven caching, and enterprise‑grade helpers baked into the core. Ecosystem: Instead of a plugin bazaar, it ships with curated utilities (SEO, caching, formatting, navigation) so agencies don’t rebuild basics every project. Content modeling: Code‑first with database schema, but exposed in the admin panel for editors—lighter than Strapi’s UI, faster to deploy. Headless/API: Hybrid mode. You can serve JSON endpoints for React/Vue frontends, or use the built‑in theme system. Open source: Repo goes live March 17, so evaluation beyond the demo is limited until then. In short: Strapi/Directus = UI‑heavy, API‑first ecosystems. SHONiR CMS = PHP‑based, hybrid, speed‑optimized, with built‑in helpers. It’s aimed at agencies that want fast, scalable sites without adopting a Node.js stack