A few weeks ago, I quietly launched Taxonomy 2.0. I’ve been meaning to write up a post about it but to be honest I’ve just been really busy working on some awesome projects.
Thankfully too busy to spam the
#eecms stream with a new
#taxonomy2rocksyourworld hash-tag, or announce LAUNCHING AN OFFICIAL LAUNCH on the forums, or blast some $1 sale via the marketing cannon - or produce any other kind of furore that we’re now accustomed to.
Anyway, a quick recap
Taxonomy began about 18 months ago as a self assigned project to learn CI/EE development. I wanted to overcome what I thought was one of ExpressionEngine’s main shortcomings - creating dynamic nested navigation and assigning hierarchy to entries.
Along the way, I lost count of the times I almost gave up building it because of frustration. I’m so glad I didn’t because Taxonomy has now opened up way more doors than I ever could have imagined. This 2.0 release is something I’m really happy with, and I’m really stoked to be sharing it with those that are purchasing it on Devot:ee.
So, what’s different in 2.0
- The main differences are under the bonnet. The Taxonomy codebase is now 30% of what it was in the 1.x version. Trees that are several levels deep can be rendered blisteringly fast with very few queries.
- The interface is polished, I’m really happy with it.
- You can now restrict which member group(s) have access to which tree.
- You can set the maximum depth for trees; the module won’t let you drag a field below your defined limit. The fieldtype & module’s “select parent” options respect your limit too - disabling options that would breach your limits.
- The fieldtype is set on a per channel basis, instead of a fieldgroup basis.
- I’m officially supporting it. Evidently when Taxonomy was free, it put a lot of people off using it. Now that folks are paying, rest assured I’m even more committed to helping out and responding to support tickets.
So, what’s coming next
Examples. I’ve had numerous requests for examples and this is something I’m working on now. Putting together some screencasts of the administrative functions/options, and building a bunch of examples showing the nav tag in action is next on the to-do list.
There are some tweaks to come to the ‘add a node’ workflow, possibly with more distinction between all the different types of nodes that can be added (eg add a page vs add a manual link vs add a template etc).
As far as features go, it’s pretty much where I want it to be - from here the focus is on refinement. I’m all ears though, if you think it’s missing something or if there’s a reason you prefer another solution over Taxonomy, let me know. I’ll admit I’ve been quite selfish in developing the feature set to fit within my workflow, I’m always keen to hear how others approach navigation problems/puzzles and there might be some simple changes to help you with what you need to do.