What is the correct way to navigate using the Twitter Bootstrap Navbar? -

i creating webpage using twitter bootstrap 3. instinct using navbar have each item navigate new href. however, i've seen handled in different ways.

some pages navigate new href , trigger page load, presumably using template of sort use same navbar code across html pages, discussed in this question.

other pages i've seen appear hiding or displaying divs content. @ first glance appears come tradeoff--on 1 hand, once loaded, can have snappy, responsive page. on other, initial page loads end being huge on large website.

other pages use navbar items scroll particular place in tall page. when use these pages, find navigation not using navbar items disorienting. solution, too, imagine becomes less attractive page size increases.

still others use navbar items add query parameter reloads page. i'm not sure how these it, , least common approach i've found.

my question is: "bootstrap way" it? no doubt valid. there discussion somewhere of tradeoffs , motivations choosing 1 on other? small pages, hiding divs or scrolling seems solution, end appears quick loading of content user. in big pages seems want approach. perhaps go div approach top level summary items , href approach navigate down level.

does have suggestions has worked them? or pointers articles discussing efficient use of navbar?

i never found discussion on 1 way or other. bootstrap seems use hrefs approach. user, find approach easiest wrap head around.

since couldn't find templates on how use approach efficiently, created own template called bootstrap-baked. html navbar, shared across top-level pages, dryed out in single place using grunt-bake template task. if you're looking create basic site using bootstrap, might place start.

it uses hrefs navigate via navbar, each new page new html file. comes tasks provided yeoman webapp generator (configured play nice grunt-bake), , responsive navbar.