Rails: How to use ActionMailer by itself?

Pinging the Ruby on Rails community to see the current adoption of Cells and component-oriented programming. Do you use Cells or a component-oriented architecture? Why or why not? Do you agree or disagree that helpers / partials are limited and / or require supplemental architecture(s)?

• It also seems that Aptomo might be the successor. (http://apotomo.de/). Looking to refactor to a include a component-oriented view structure in the next few weeks, and was hoping to get an idea of which (if any) tools should be used to extend the Rails framework (specifically, partials and helpers).

• Answer:

  Your question contains about 4-5 other questions. I will start with the topic on using Cells. The concept of using Cells architecture in a web application was adopted by Ruby On Rails from other frameworks (at least that I know of), because at the time there were no other complimentary ways Rails apps could become more modular. Cells were nice and cool, until: It became more like a liability rather than a beneficial feature. Created a confusing app directory tree, if there were no specific patterns to follow: The community's support slowed down, thus it has lots of tickets / issues to be resolved. Change in patterns: After the rise of Javascript / NodeJs and it's modular libraries, Cells architecture patten was quickly replaced by other things.  Some developers try to make the data / models accessible through a JSON api to give them the freedom to do whatever they want with the raw data, mostly to connect it to a frontend framework. JS enforcement: came along very early to be adopted instead of making Cells work and following that path. Nowadays, I can say that pretty much anything Cells was serving with can replace do in a  better shape. To briefly answer the rest of your questions: Do  you use Cells or a component-oriented architecture? Yes, component-oriented architecture can help in cases of a front-end heavy web applications. Why or why not? It's what it is, there are needs for these sorts of approaches and the industry is coming up with better approaches every minute. Having to deal with huge amount of data inside your browser looks like something everyone is being haunted by. Well Facebook is solving with , Google is trying with 2.0. was approaching this issue in their own way until recently using Rendrjs. Do  you agree or disagree that helpers / partials are limited and / or  require supplemental architecture(s)? This is not a question to agree or disagree on. Partials are made to deal with Partial interactions of data on the page and inside the Rails App. Perhaps check out this book to avoid anti-patterns: There is no correlation in between adopting tools, new approaches VS it's coolness, because once a company hits it's limitations, there has to be change to resolve it. source: https://xkcd.com/552/