Ruby on Rails

Alpha Blue wrote in post #1019380:
> I would decide what customizations you are willing to support or not
> support.

Life would be lovely if that were up to me. But the person with the
checkbook gets to make that decision. (Of course, I can charge more for
some customizations...)

> For the ones that you want to support, create a separate git
> and provide your customization gem/plugin there. In terms of skinning,
> this will be fairly easy. You could supply options for using different
> layout files which could include how the page displays, the CSS used,
> etc.

That's what I had in mind: swapping in different CSS files under git
control is straightforward. Swapping in different views isn't much
harder. Mercifully, the customer has not requested any 'tweaks' that
would require changes to the models or schema -- that could quickly
become a real PITA.

@Curtis Schofield: The customer is asking for more than just changes to
the CSS -- he wants different content and some additional views. And I
agree that this could become a nightmare -- I plan to maintain a bill of
materials, SKUs and ECOs for each variant of the app. That should help
some.

--
Posted via http://www.ruby-forum.com/.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.