Open ghost opened 14 years ago
Here's the domain language: a "category" is a subject-based label for an article, roughly corresponding to a newspaper section but with one difference: one article can belong to many categories.
In print editions, it's quite rare to have an article published in more than one section. In order to properly capture the organization of the print edition (and usually, the newspaper's internal structure), each article can also belong to one primary category, referred to as its "section".
We can change the terms, but we'll need to distinguish between the two relationships somehow.
One thing to note: there was once a separate class for this (called Section) until it became clear that they were really just the same as categories. That class is entirely unnecessary. At some point, we'll have to run a migration to get rid of it.
Right, that makes sense. Maybe it would be better to use "primary category" or something similar instead of "section." That way it would be clear that a section isn't really any different than a category, just that there can only be one.
In the article edit screen and articles list screen, we use the word "section", but he rest of the interface and routes use "category". Is there any reason for this discrepancy, and if not, should we standardise on "category" across the interface?