Could you do the customisation entirely in CSS? If necessary, you could have the HTML contain a superset of what's needed for individual versions of pages, then use CSS to show/hide things appropriately.
That would greatly simplify it. Cheers, Chris On Tue, Sep 6, 2011 at 1:14 PM, Dmytrii Nagirniak <dna...@gmail.com> wrote: > Hi, > I was wondering ones do customisations per client in a Rails app? > Clients (businesses) do not want to bother with it and usually send their > own "layout" and stuff. So we incorporate that into the app. > More information: > > every client obtains a subdomain; > subdomain might get some of the pages customised; > when a client is on the main (www) subdomain, no customisation applies, but > same functionality is available; > > I was thinking about overriding the lookup mechanism for the views to have > structure like: > views/dashboards > index.html.erb > views/subdomain1/index,html.erb > But don't like it much as it is not very flexible (especially for assets per > client) and will get harder and harder to maintain and test. > > Have you done it before? > Any recommendations? > Cheers, > Dmytrii Nagirniak > http://ApproachE.com > > -- > You received this message because you are subscribed to the Google Groups > "Ruby or Rails Oceania" group. > To post to this group, send email to rails-oceania@googlegroups.com. > To unsubscribe from this group, send email to > rails-oceania+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rails-oceania?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to rails-oceania@googlegroups.com. To unsubscribe from this group, send email to rails-oceania+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
