Document the home_as_tab: true to a-navigation from tabs component

[rickybanister]

The old navigation component had an app.yml feature where you could turn the 'home' tab on in the main nav tabs.

The new a-navigation component, while being more flexible and awesome, does not listen to that yml setting.

Could it be ported over so that the first tab in your navigation be home if you've set that to true?

[dordille]

So I would prefer to create something that is a little more expandable then a setting in app.yml. My first thought was to do something like the following in your templates.

include_component('aNavigation', 'tabs', array('custom' => array(
  '/' => 'Home', 'http://www.google.com' => 'Google')));

[boutell]

It's baaaaaaaack (I had this custom tabs feature in there away back when)

Implementing a 'current' class for the custom URLs is going to be interesting. Have to be careful not to get confused by the frontend controller in the URL

[dordille]

Rick can you give me confirmation that this is working now.

[dordille]

This functionality exists for pages within the page hierarchy as follows. By passing the option extras to the tabs navigation component you can add additional pages to a navigation element.

Example:

<?php include_component('aNavigation', 'tabs', array('root' => '/', 'active' => $page['slug'], 'name' => 'main', 'draggable' => true, 'dragIcon' => false, 'extras' => array('/m' => 'Home'))) # Top Level Navigation ?>

[dordille]

You can also specify external urls instead of page slugs in the extras options.

Example:

<?php include_component('aNavigation', 'tabs', array('root' => '/', 'active' => $page['slug'], 'name' => 'main', 'draggable' => true, 'dragIcon' => false, 'extras' => array('http://www.google.com' => 'Google'))) # Top Level Navigation ?>

[boutell]

This got done yesterday