I'm working on a rails application, and so far I've focused on the api and the functionality. But now I'm more and more reaching a point where I will want to add static content, descriptions of the software and help information. Information that is generally in a CMS system.How do I in the best way structure this so I can still work with the application. Yet maintaining the look and feel of the rails application? Do write a CMS in my app? That seems a bit far fetched. Are there any Gems that do this? What is the de facto standard for architecting this scenario?
Structuring a rails application with static data
architecture;ruby on rails
It depends on the scenario. So far we needed a few 3-4 pages of static pages. so we made a separate controller for such static pages. as they are not needed to be handled by rails each time, we enabled page caching for them. However, these are implemented when we need to match the layout. When we don't need to use the layout, we better put them in /public directory. now i've seen several similar questions recommended to use high volatage. i guess you can give it a try. you can also check this discussion. a cms may be appropriate when the static pages will be created dynamically, i mean it will be created after the application is deployed by user without the help of developers. if you already know that you have a few static pages, i guess it is better you create them during development. but when you foresee that in future they may grow, it's surely good idea to implement a basic, at least, cms.  