There are always some static pages such as About(about.html), Contacts(contacts.html) and other. In some tutorials authors create a special controller named “site” and define actions ‘about’, ‘contacts’ which just render static pages and allow using link_to in other erb pages. Other authors just create static html pages and use old-good About or something like that. Which method is better(if any is) and why choosing one over another?
There are always some static pages such as About(about.html), Contacts(contacts.html) and other. In some
Share
I don’t like accessing static resources directly from the URL bar–too often they end up becoming not static at some point, breaking links, and causing app-wide linking updates. Not always a big deal, since things like that are usually isolated, but… not always, and finding them when they’re not can be a pain.
I just don’t see a good reason for isolating them as static resources, they usually use the same layout as the rest of the site, you may want to add behavior later, etc.