-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hierarchical Taxonomies #92
Comments
+1, definitely need this. |
I just ran into this problem. |
+1. Hope to to see this soon |
@stuartcusackie and @tobinski could you please click the 👍 icon above to vote for the feature. I'm not sure if they can count the +1 in texts automatically. |
done. |
Why ist this still not implemented? Definitely need this! |
Because of all the other things people also need that we have been implementing. We’ll get to it as soon as we can! |
@jackmcdade sorry if that sounded like that, but this wasn't supposed to sound like an attack to the statamic devs. Just wanted to push this issue, since it's already 3 years old 😅 |
It's a really really big feature... 😅 |
This feature is one of the deciding factors when we are starting new projects, when we ask ourselves which CMS will suit the job, anything that needs multiple layers of taxonomies for even moderately complex search/filtering, we need to look at other options. I'm looking forward to when taxonomies are overhauled a little bit so we can use Statamic for that niche of projects as well. :) |
Exactly this 😅 |
Would be a really nice feature to have! |
Just chiming in to say that this is something I, too, would like to see being prioritized. |
Right now we are having a discussion with a client that needs hierarchical taxonomies. |
Please add a 👍 reaction instead of adding comments - that way the Team can sort the feature requests by the 👍 reaction. |
What is the status on this? I understand it is a big job, but almost ANY site with a category use-case, will have a need for nested categories. |
I don't believe it's being worked on yet. Based on the number of 👍 I'm guessing it's somewhere high up on the Roadmap but unsure on the ETA. |
Am also among the hordes of people awaiting this feature, would be great to get some sort of ETA for those weighing up starting new projects if possible. thanks! https://github.com/statamic/cms/discussions?discussions_q=nested |
I'd love to see this happen! The sooner the better 🙏 |
+1, this is a must have! Hard to tell client to move from WP without this feature. |
Is there a sponsorship program to get features like this implemented? Im already a paying pro user, but i would definitely be interested in sponsoring crucial things like this to get worked on |
Now is the time to join the discussion here: #839 |
This was a blocking feature for me unfortunately. Hierarchical tags / more robust ontology is important for so many projects. https://www.npmjs.com/package/sanity-plugin-taxonomy-manager |
Statamic can't really move far beyond tiny simple small business websites without massive cludge work till this is a thing. We've built big sites on it, but it's a huge time-sinking headache and makes us think twice about using this CMS for anything serious, really. For simple small business websites, we'd probably stick with WordPress. This issue is holding Statamic back, big time. |
@hmw-anthonyc Thanks for the feedback. |
I've been watching the development of Statamic from the sidelines for a little while, thinking about how it might replace Drupal in my tech stack. In most ways, Statamic is far superior to Drupal (speed, content structure, restful interface, content authoring experience etc...) Hierarchal Taxonomies are really the only missing feature that's a road block. |
@quadradan you can use a structured collection and an entries field for this use case. You lose magic routing but its otherwise pretty much the same. |
I also need this hierarchal taxonomies for almost all projects. I really hope that this could be added to statamic anytime soon. |
As explained in statamic/cms#74
The text was updated successfully, but these errors were encountered: