Comfortable Mexican Sofa VS Cells

You could try a CMS engine, ala comfortable-mexican-sofa - though I don't think it's been updated for a couple of years.

You're going to be disappointed. https://www.locomotivecms.com/ might get you kind of close. https://github.com/comfy/comfortable-mexican-sofa is good, too, but not modern-looking.

I did my research, and I really liked comfortable mexican sofa or Comfy. It even had ActiveStorage integration for file uploads! Nothing against other CMS engines, be it RefineryCMS or AlchemyCMS - but I felt that Comfy had the right combination of being extremely simple, yet having enough hidden powers to not become a blocker in the future.

It can be used with Ruby on Rails or other frameworks because I implemented with trailblazer/cells.

I agree, though cells does still have a larger following.

Better official documentation for cells: https://trailblazer.to/2.1/docs/cells.html

So what about the world outside Rails defaults? There are quite a few independent projects trying to help build components in the Rails view layer, among the more famous being Draper (utilizing the decorators pattern) or Cells (full-featured components in views). In the end, we decided to take a deeper look into a relatively new one – the ViewComponent framework.

GitHub has recently posted an article about view_component: https://github.blog/2020-12-15-encapsulating-ruby-on-rails-views/ Before it gets too popular I think I should share my experience with cells So that developers can have another chance to re-think and pick what to use for "encapsulated view components".

This, combined with the fact that we are using cells gem for some view components, resulted in another couple of hours of hunting for the problem (it takes some time to debug what exactly and how exactly changed in Rails internals) and then fixing this problem. At this moment, I already spent over 8 hours debugging Rails internals, different gem internals, fixing application, fixing tests, screaming internally.