Netlify CMS vs. Optimizely One

Netlify CMS is well suited when you have very less frequent updates to your content, maybe once a day and very few people need to access your data. You can connect it to Netlify, GitHub, or any platform and have multiple people access it and do as many updates as you wish, but the process is not well-defined and you need to build your own system for that. It is well suited for projects you need to pull off with very low cost, it is essentially free as the software is open source and free to use, and all you need to do is set up your schema correctly and find a deployment pipeline where you can build your static site/API to redeploy whenever the content changes. I personally used a GitHub Login -> Netlify CMS -> next app consumer of content -> GitHub pipelines to run next SSG -> GitHub Pages to deploy the built static site. It might not be appropriate for large teams where users themselves need no-code tools to modify the schema of the content.

Incentivized

It is well suited for heavy-duty A/B testing where management would like to see and quantitatively determine the effect of a change. It is not so efficient to try for a single page simple form, except when the form is part of a larger workflow. The security model is not very well understood, including RBAC and protection against injection attacks.

Incentivized

• Storing content data in customized schema without a database
• Full control over your content and infrastructure where it is deployed and stored
• Very low-cost way for building your own CMS and CDN

Incentivized

• Provides quicker release cycle for the way the product cards should be displayed.
• Provides feedback for new product introduction and how it'll be perceived.
• Allows rapid blackout from user experience changes that alters traffic flow.

Incentivized

• Linking between different schema types, i.e. having some relations between content
• Better ways to define content schema, like how TinaCMS would handle using a JSON

Incentivized

• Can use better interface for managing test, including scheduling and notification.
• Feels too heavy for simple projects, though this isn't a factor once past the PoC stage.
• Notification on various aspects can be made more powerful and granular if such a need arise.

Incentivized

We really can't compare it to full-fledged CMS software, like WordPress, which has a lot of community and support with widgets, plugins, and whatnot. It's not built for that, but you can compare it to Contentful, Ghost, Strapi, etc., which provide similar functionality to a headless CMS with custom schema options, but even among them, it still lacks a lot of functionality, ease of use, and support. But Netlify CMS pros would be of the opinion that compared to other platforms where most schemas need to use their own tools and frameworks, it's very cost-effective. Something new called TinaCMS has come up to compete with Netlify CMS by covering most of its shortcomings, but it's something new being built by the same team that built Forestry CMS and comes with many modern features, yet currently only supports NextJS SSG.

Incentivized

There is a big difference between the two: Google Optimize uses Bayesian analysis while Optimizely uses Frequenting. There is a risk of counting multiple visits. Google Optimize data isn't available instantly (if I remember correctly). Optimizely's analyses dashboard is a lot richer and offers a better experience, though it may get intimidating.

Incentivized

• Helped us inject dynamic content into existing site very quickly
• Wasted a lot of time to implement when something complex, such as querying content, was needed

Incentivized

• Almost immediate payoff in terms of the benefit.
• Easy to justify the TTM benefits to upper management.
• Still somewhat hard to justify ROI, though this is not my expertise.

Incentivized