You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 10, 2021. It is now read-only.
Currently the news component auto-generates a news category for every category added by the content team and puts the category into the drop down filter:
The categories currently are used a bit like tags so that the 'related news' is relevant to the article - for example 'Women and Girls' is a grants initiative we support and we would want those articles to link to each other. We do not want the 'Women and Girls' category to be displayed as a front end filter to the end user.
The category should still exist in the background to link relevant articles to each other - the content team just need to be able to choose if they are displayed as final front end filters to the end users.
The text was updated successfully, but these errors were encountered:
@adamclark-dev I believe during planning we discussed an alternative way of doing this, i.e. by having a taxonomy tree, and only use the first level of the tree for display in the filter. 2nd levels wouldn't appear but can be used for linking up articles. Not sure if we delved further into this, but might be worth rechecking with @CarolineRennie@Heleen-cr and @LivMoss ?
Currently the news component auto-generates a news category for every category added by the content team and puts the category into the drop down filter:
The categories currently are used a bit like tags so that the 'related news' is relevant to the article - for example 'Women and Girls' is a grants initiative we support and we would want those articles to link to each other. We do not want the 'Women and Girls' category to be displayed as a front end filter to the end user.
The category should still exist in the background to link relevant articles to each other - the content team just need to be able to choose if they are displayed as final front end filters to the end users.
The text was updated successfully, but these errors were encountered: