Topic: Scoping Sections
Okay, so I am setting up a site that has articles and profiles, each with its own set of sections. For example:
My first instinct is to create a simple, one-column table for sections, yet I am not sure how to scope them out so that article sections get called from articles and same with profiles. It seems like bad design to have two different tables that do the exact same thing and only have a column called "name"
For sections, STI seems like the cleanest approach db-wise, but the models are not really different (except for the has_many declaration), so this can't be the answer.
All of this I am trying to accomplish RESTfully... I am close but not quite there yet.