We have found Chapter Three to be a valuable resource in both training and development of custom Drupal functionality. In addition, getting Chapter Three’s help with scaling Drupal has been a real asset.
Jim Nisbet, CTO Highwire Press
Moblin.org Launches on Drupal 6.0 w/Menu Trails
Josh Koenig | September 26, 2008 - 11:57am (2 comments)
Chapter Three is pleased to announce that Moblin.org, the developer community for a worldwide effort to build a better Embedded Linux platform (with the involvement of the likes of Intel), has re-launched on Drupal 6.0.
This is our first big project to get out the door on Drupal 6, and I've got to say it was a really great experience. Getting oriented was a bit of a challenge at first, but there are so many common-sense improvements to the Module API and Theme layers, it makes development easier than ever.
In addition to utilizing the latest releases of Organic Groups, CCK and Views, Moblin features a completely re-vamped and re-built Menu Trails module, which we've developed to add some usability goodness to Drupal's default Primary/Secondary links and Breadcrumbs. Menu Trails allows individual nodes to automatically appear "under" an existing menu item based on their type, taxonomy, and now Organic Group. This is then reflected throughout the visible nav hierarchy, and now in the breadcrumbs as well:
Look for an official 6.0 release within a few weeks, featuring all of the above, plus pathauto integration and more.
Moblin also features a number of developer-centric innovations such as shared authentication and status updates from Bugzilla, as well as project-level integration with Git for updates via RSS. These were developed on a custom basis since they're particular to the back-end system architecture of the project, but in my opinion a huge part of the appeal of Drupal it's power as a platform which allows for powerful custom integration to be developed rapidly, safely, and extensibly. Drupal performs very well at the center of a Web 3.0 "cloud".
There's sure to be more to come as the Moblin community rallies around their 2.0 launch and begins a big push over the next year. It's quite encouraging to see this kind of synergy between Open Source projects. We at Chapter Three are definitely excited for what's next.
Add comment
Blog Tags
Client Testimonial
Drupalcon SF 2010
Josh: Before I ask, thank you for your contributions to the Drupal community through the Drupal Dojo ... watching those screen-casts really accelerated my quest to grok Drupal many-fold.
Question
----------
Did your amended Menu Trails functionality you mention in this article ever make it into an updated D6.x version of the module?
I have the Menu Trails module working on a dev site, but having to place each node in the menu system in order for it to take on the CSS class=active-trail seems nuts to me. Why is not just base the assignment of that CSS class on the pathauto path instead for example?
Assume you have Menu-Trails module installed. And, you have:
[1]Primary Link Menu Item = Section (path=BASEPATH/section)
[2]Secondary Link Menu Item = Sub-Section (BASEPATH/section/sub-section
Now, create a node with path BASEPATH/section/sub-section/node-title, but do *not* set it's Menu Settings (i.e. do not add it to the menu system). It will not be detected as an active crumb on the trail and assigned the active-trail class on the
Why not just key it off the path-auto path, and ignore the menu settings of the node when not set?
Would be nice to not have to put the onus on the end-user managing/publishing the content to have to remember to set the proper menu settings in order to have UI consistency.
Am I missing something here?