In the past I have created articles inside folders for organizing Articles into categories. The hierarchy would look something like this for example.
- Article Library
– General Interest
An article could belong to multiple categories so I would give it multiple locations. There’s nothing wrong with doing it this way but I’m curious if there is a better way to do this.
In my article contentType I could add a metadata field called ‘Category’ which would be a multiselect fieldtype. That solves having to use folders to organize my content and all articles would live in just one folder. However, I would need to come up with an admin UI extension so I can filter articles in the back end by category for Editorial purposes. I would also need to figure out how to inject the multiselect fieldtype into the url name alias pattern so the url would reflect all category selections. I’m not even sure if the content creation process could even do that by generating a dynamic url based on the multiselect fieldtype. On the front end I would have to create a custom controller and query type for filtering results from the article library based on url routing paths.
This all seems like a lot of work to avoid having to use multiple folders for category organization. The articles could be stored in multiple locations which solves the url generation issue. Maybe I just talked myself out of doing this but would be curious for any feedback. I also considered using tags however tags would span content types and I would not want anything to bleed over by mistake.