Content and editing
Categories and taxonomies
Understand the current single-category article model and category-based layouts.
On this page
What is implemented
Care CMS currently has configured article category slugs and labels, with a default category for new articles. It does not provide arbitrary taxonomy registration, nested terms, multi-category assignment or a general tag-management system. Categories are managed under Settings → Writing. A slug is a stable machine identifier; the label is the readable editorial name. Keep slugs lowercase, using letters, numbers and hyphens.
Use a category
- Configure the allowed category and its label.
- Set the default for new articles when appropriate.
- Choose a category while editing an article.
- Apply a category-specific shared layout if articles need a distinct presentation.
- Review the published archive and its category filtering.
Deletion and translation
Categories still used by articles cannot be removed. Rules used by shared layouts must also remain consistent. Reassign content and review layout rules before removing a category. English article duplication preserves the category while resetting language-specific layout overrides. A category is not an automatic translation engine.
API boundary
The current public page serializer returns content type and language, but does not expose category as a field or provide a dedicated taxonomy endpoint. Do not build a frontend around an invented /api/v1/taxonomies route. Additional taxonomy models require a data migration, validation, permission checks, editorial UI and explicit API design; they are separate development work.
Something unclear? Contact me about this guide.