You missed showing the SUBSECTION_ARTICLE table. <grin/> But I think that's pretty well implied by everything else.
I don't think you changed my thinking much.
The truly important table here really is that SUBSECTION_ARTICLE table, no?
The other tables are just a way to navigate from SECTION down to an appropriate collection of SUBSECTIONs.
And that means that everything you have said and done indeed makes sense.
Sure, you *COULD* have done this without the DIMENSIONs. In essence, all you'd do would be to rename your subsections:
DIMENSION Featured Legal + SUBSECTION Tax Law
would convert to
DIMENSIONSUBSECTION Featured Legal Tax Law
Or you could have done it with a single table. The one you showed, just above, SECTION_DIMENSION_SUBSECTION_ARTICLE. If you wanted, you truly could implement it like that, perhaps using ENUM values for the Dimension and Sub-section fields.
So to me this isn't really a question about database organization, per se, as just a way for you to make it easier for you to VIEW the organization.
If I'm wrong, then your answer to the following question would have to be "yes":
Question: Would there ever be a case where there would be an ARTICLE in a given SUBSECTION that would need to be *excluded* because of the SECTION it is in?
It sure looks to me like the answer to that is "no." In which case I think you are 100% on the right track.
An optimist sees the glass as half full.
A pessimist sees the glass as half empty.
A realist drinks it no matter how much there is.