[neovive]

Great job and many thanks for this excellent framework!

I've been waiting for this release for an upcoming project. I assume the use of HTML5 specific tags is optional. I noticed that the page used for the docs uses "<ul class="nav">" instead of "<nav>", but does utilize the "<footer>" tag. Is there a specific advantage to not using the "<nav> tag?

[yeswecan]

If you are using <ul> and <li> elements for your links it's one fewer tag in your HTML:

    <ul class="nav">
        <li></li>
    </ul>

vs

    <nav>
        <ul>
            <li></li>
        </ul>
    </nav>

The only 'danger' is that if someone is specifically looking at your page specifically for <nav> tags to locate your navigation they won't find it.

[neovive]

I can definitely see the semantic advantage of the <nav> tag, especially for robots and screen readers. Is there a way to programmatically treat the <nav> tag like a <ul> wihtout using an extra tag?