# 10 Points How Cells Improves your Rails Architecture

**URL:** <https://www.ruby-forum.com/t/10-points-how-cells-improves-your-rails-architecture/196007>\
**Category:** Rails\
**Created:** [October 5, 2010, 11:57am UTC](https://www.ruby-forum.com/t/10-points-how-cells-improves-your-rails-architecture/196007 "2010-10-05T11:57:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nicksnels](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/n/aca169/32.png) [@nicksnels](https://www.ruby-forum.com/u/nicksnels)\
**Post date:** [October 5, 2010, 11:57am UTC](https://www.ruby-forum.com/t/10-points-how-cells-improves-your-rails-architecture/196007/1 "2010-10-05T11:57:12Z")

</div>

What steps does it take to improve your architecture with Cells? This  
article [1] discusses the best practices from keeping views dumb, via  
slim controllers, how to avoid messy helpers, through to hiding your  
caching strategy and component-oriented teams.

[1]  
[http://nicksda.apotomo.de/2010/10/10-points-how-cells-improves-your-rails-architecture/](http://nicksda.apotomo.de/2010/10/10-points-how-cells-improves-your-rails-architecture/)