Hey everyone! I'm gearing up to present a tech stack for a company that operates in multiple countries, and I'm stuck on picking the right CMS. Here are my must-haves:
1. Fast performance is crucial; I need a blazing fast user experience.
2. Full SEO compatibility is essential since the product will serve as a multilingual landing application. I want to avoid things like country-specific directories (/fr, /ru) and go for ccTLD level domain splitting instead.
3. It should allow easy implementation of new custom features, like tracking Analytics from each landing page using the same CMS API Endpoint, and creating workflows for pushing new content.
4. Scalability is key in case we want to add e-commerce features or anything else later on.
5. It needs to be open-source.
6. Ideally, I want a long-term solution that will last.
I've mainly been looking at Strapi, which seems to check all my boxes, but I've heard Payload and Directus might be better options. There's a lot of info out there comparing these CMSs, and it's overwhelming. I'm also familiar with Next.js but am leaning towards SvelteKit for the frontend. What do you all think would be the best choice for my situation? Some AI tools suggested sticking with Strapi, but I'm looking for more opinions!
5 Answers
All headless CMS options like Strapi, Directus, and Payload are pretty similar in concept; they let you create content structures that you fill in. The focus should be on how you handle the SEO aspects in your SvelteKit app. I personally use Kirby CMS, which is lightweight and meets similar needs.
I've been juggling between Strapi, Directus, and Payload too. Right now, Payload feels like the best option – it's lightweight, flexible, and powerful. Strapi has had some performance issues and clutter since its latest update, which turned me off.
Remember, no CMS will handle SEO for you; that's all about how you set it up. Payload does have an SEO plugin that might help, but it's ultimately up to your implementation.
Honestly, building your own CMS framework using lightweight Symfony bundles might give you exactly what you need. Alternatively, you can try a custom WordPress setup with caching for speed.
Any framework can work well. It really boils down to your team's productivity and preferences. Is this for a big application or integrating an existing product? Just keep in mind that maintaining multiple databases can increase your development costs in the long run.
True, but using a CMS with built-in SEO tools can help save time on those optimizations!