solidusio
[Admin][Users] Introduce taxonomy creation and modification capability
Description
Note:
- Taxonomies will change name in Categories
- Each taxon will become a Category
We already have a taxonomies/categories index page:
We need to replace this part related to the taxon/category management:
Features
- Follow the storyboard to redesign the current UI/UIX
Figma Design
@kennyadsl @tvdeyen Some clarification needed please 😄
Taxonomies will change name in Categories Each taxon will become a Category Follow the storyboard to redesign the current UI/UIX
As I understand the above, we won't have a dedicated page for taxonomies anymore. So to compare:
| Current | New |
|---|---|
| "Taxonomies" menu shows existing taxonomies | Menu renamed to "Categories", shows all taxons tree; there is no interface to CRUD taxonomies |
| To create new root taxon you go to "Taxonomies" and need to create a taxonomy of the same name first and after save it will create the root taxon under that taxonomy | To create new root taxon you go to "Categories" and from there choose "Add Category", and then in the dialog leave Parent Category empty; under the hood we will need to follow the same logic to create taxonomy with the same name first so it creates the root taxon |
Do we maybe intend to get rid of taxonomies as mandatory objects to have taxons tree at all? Figma designs imply that taxonomies are nowhere to be seen, but we have logic (i.e model associations and validations) in place that won't allow a Taxon record to not have a taxonomy associated, so implementing this logic will require some potentially breaking changes to be introduced.
What would be the desired result - hiding taxonomies interface but keeping existing logic on backend, or wiping out taxonomies completely?
Taxonomies (multiple categorizations) is one of the powerful tools that distinguish Solidus from other platforms. We will not remove or hide that feature. The design is clearly a taxon tree interface for a single taxonomy (in the example the "Categories" taxonomy). We will still need to have a CRUD interface for managing taxonomies. I am open for renaming taxonomies, in lieu for a better name, though.
@tvdeyen Got it. One thing to mention and you can see it in the screenshot for current UI:
There's always only one root taxon allowed under one taxonomy, in the example above taxonomy is "Categories" and the root taxon inherits same name (you can update the root taxon name though).
So in this new UI it does not show root taxon. You reckon it's just an overlook in design and we keep the tree structure as it is, i.e showing the root taxon and all the children below?
Very good question. Maybe the idea was to hide the root taxon and we only show first level children. Or they actually mixed the taxonomies into this interface as well?
I have not been involved in the design of the new admin. Maybe @kennyadsl can enlighten us?