All the latest news and announcements, straight from the WooThemes HQ!
Update: Custom Navigation in WP 3.0
23. Feb, 2010 by Adii Rockstar in Development
We just wanted to give you a quick update on the integration of the WooNav into the core of WordPress 3.0 (final version to be available mid-April).
Jeff has been working really hard to get everything ready and the basic functionality for the Custom Navigation (as it is now being called) has already been included in the WP 3.0 nightly builds (after last week’s WP dev chat). The most significant amount of work centered around moving away from Woo-specific branding, uses of prefixes and coding preferences, which means Jeff had to create a patch using all of the WP core standards & defaults. It is now that patch which is available in the nightly builds.
This is what the Custom Navigation is looking like at the moment:
The New Custom Navigation in WP 3.0
Jeff & a few other leading WP contributors will now spend some time with the community in getting their feedback before further tweaks are made (you can get involved on the Trac ticket here). There are still a few obvious UI and then a few more technical things that needs attention, but overall the project is bang-on track and we’re super excited about seeing it rolled out in WP 3.0! 
23 February 2010 at 7:38 am #
Nice work Jeff
23 February 2010 at 7:38 am #
Sweet, WP needs something like this. I’ll keep following you guys on Twitter for developments.
23 February 2010 at 7:42 am #
Awesome stuff – looking forward to WordPress 3.0’s release!
Is there any guidance / instructions on how to use this menu within a WP theme? I tried using `wp_custom_navigation_output` without success…
23 February 2010 at 8:00 am #
Not at the moment no and since we’re making a bunch of changes to this now, we probably won’t have a proper “codex” ready until WP 3.0 is released.
23 February 2010 at 7:47 am #
Awesome guys this is a great achievement!
I can’t wait to see it in action and get going using it!
23 February 2010 at 7:49 am #
Fantastic to see this progressing, and the frustration of havng to wait for it to be added to Aperture will be offset by having this available to everyone with WP3.0.
Keep up all the fantastic work, and cheers!
23 February 2010 at 8:04 am #
I’ve been looking at the new navigation in the WP3.0 beta. Looks very good, and is something that’s gonna save time creating the nav.
Now, when I activated the woonav on the default kubrick theme, and changed the sort order of some pages, I don’t see any changes on the frontend. I guess that other template tags have to be used in the theme ? Anybody ?
sidenote: Does anybody use Canvas as theme-framework ? What are your opinions?
Congrats to all woo-staff for accomplishing this and taking the wp community a step further.
Greetz,
ToM.
23 February 2010 at 8:08 am #
Yep, there’s new template tags that need to be used.
23 February 2010 at 8:27 am #
Adii, what a wonderful reply
.. no chance they’re revealed ??
and what about the canvas-question? Or can’t you elaborate on that one too
T.
23 February 2010 at 8:44 am #
Sorry for sounding cryptic about the template tags, but that information just ain’t ready yet (as noted here) since there’s still too many changes that are expected. As soon as the functionality is stable, we’ll release as much information as possible.
And I don’t use Canvas myself, so I figured that the users would answer that for you.
23 February 2010 at 10:47 am #
You guys are studs. Seriously. I’m more excited than ever that I’m a WooThemes user.
Re: Canvas question : I was going to use it as a framework for a client site, but it turned to be tricky, since I’m so used to tweaking code through child themes, and having anything in the Canvas options disrupted it all.
I have recommended it to non-designer folks I know, because it’s exactly what they need… but for those of us who are more comfortable “under the hood”, there may be a better solution elsewhere. It all depends on what you’re trying to accomplish, and how you choose to go about it.
23 February 2010 at 12:26 pm #
You have an option to turn off all CSS in Canvas options if you want to use a child theme
24 February 2010 at 2:50 am #
Thanx Adii, Adam & Magnus. I’ll patiently wait for WP3.0 to come out then. Keep myself busy thinking about using canvas as framework or not
23 February 2010 at 11:21 am #
Congratulations ad thanks, WooTeam!
Since you born, about mid-2008, you improve and going to up!
As a old user and client of you, from Artepick TM want to say a only thing:
Thanks & Congratulations!!!!!
23 February 2010 at 11:21 am #
You guys are AWESOME!
23 February 2010 at 4:01 pm #
I hope Woo gets the business boost you deserve for this work. GPL and OpenSource shouldn’t mean “no profit.”
23 February 2010 at 5:37 pm #
I actually believe that this will be the case.
24 February 2010 at 11:17 am #
Congrats! That is great news for everyone.
24 February 2010 at 1:22 pm #
As a past customer, I just wanted to say thank you to everybody at Woo for all your work on this! It shows why Wordpress is the best publishing platform out there and I give you all massive credit.
I’ll definitely continue to be a customer, this has helped make sure of that.
-Matt
3 March 2010 at 3:48 am #
This is one of the most amazing and most useful tools I have ever seen. Additionally, however, you I cannot find enough praise for you having collaborated with the development team so it can become part of the 3.o release. I can hardly wait …..
Thank you
5 March 2010 at 6:41 pm #
Its great that the navigation issue is finally being addresses, but this could be improved even more.
There is plugin called Simple Sidebar Navigation I use that does one thing better than this which should be incorporated, and that is conditional appearance options. It would be a shame to not get this right the first time.
6 March 2010 at 6:36 am #
What does it do better?
8 March 2010 at 2:29 am #
Conditional appearance. Play with it and see what it can do. I can have different nav on different page if I want. Other than that, I am glad to see theme designers finally get that a custom nav feature is crucial to fully using WP as a robust cms.