When comparing Yesod vs Strapi, the Slant community recommends Yesod for most people. In the question“What are the best backend web frameworks?” Yesod is ranked 12th while Strapi is ranked 32nd. The most important reason people chose Yesod is:
While not required, Yesod offers templating through a Shakespearean family of languages to produce page code.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Offers templating for type-safe, well-formed content
While not required, Yesod offers templating through a Shakespearean family of languages to produce page code.
Pro Uses type-safe URLs
Ensures that data provided by the URL is type-safe. This means that data in the URL has a definitive type.
Pro Can be used without knowing much Haskell
While Yesod is written in Haskell, developers can achieve basic functionality without much investment in the language.
Pro Auto-generate REST APIs
Strapi comes with blueprints that let you create, read, update and delete your data. You also can paginate, sort and filter your results in a matter of seconds with simple but yet specific parameters.
Pro Users, groups and permissions
Manage user settings, login, registration, groups and permissions on the fly. Strapi delivers all those essential features out-of-the-box.
Pro Out-of-the-box administration panel
Easy way to manage your application. This panel allows you to add/edit/delete entries for your APIs, manage your users, groups and permissions. In the future, it will be such as WordPress-like administration panel dedicated to your application.
Cons
Con Is hard to customize
Learning how Yesod works internally is hard. It is a large framework with complicated components. Finding the appropriate code and understanding how it contributes to the framework is difficult, meaning developers will struggle.
Con Too much template haskell
You actually want to code in haskell and not some DSL with "magic" hidden under the bonnet.