rename "in-page nav"/"sleek nav"/"whole page nav" to 'tabs'

[ninadel]

I would suggest that labels for these headings be more descriptive, as nav could pertain to lots of different UI types

sleek nav => modular tabs
whole page nav => page tabs

we will eventually add a design section that will include navigation patterns (pages 22-27 of the guidelines PDF), so to prevent future confusion would be better to avoid the word 'nav' in the component section if possible.

[peter-mouland]

moved this to milestone 2.3 as a thanks for designs input :)

[peter-mouland]

we would have to work out if the css/js should also change to match and whether or not we keep alias' to the old function so as not to be a breaking change. If we keep the alias, it would be worth starting a 3.0 milestone listing the alias' to remove.

[charypar]

Is there a way to also safely print deprecation warnings without causing issues?

[peter-mouland]

yeah, good point. So docs would need to be updated to the new version and in the code we should detect console and then console.info or something that makes sense to let the dev know.