navire
Simple, elegant navigation.
Last updated 8 months ago by claudenegm .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install navire 
SYNC missed versions from official npm registry.

navire

Simple, elegant navigation.

Navire ships with typings out of the box and can be used both server and client-side.


Usage

npm

npm i navire

and then you can require it:

const Navire = require("navire");

Browser

Download /browser/dist/navire-browser.js and import in the browser like:

<script src="navire-browser.js"></script>
<!-- `Navire` is now a global variable. -->

Instructions


Navire is the main class that is used for managing the full navigation tree. When initialized, we use navire to represent it. It contains methods such as findByHref(), findByTitle(), get(), and traverse(). These are essential to using navire effectively. Navire also shares some methods with NavireItem such as append(), appendCategory(), appendDivider(), appendLink().

NavireItem is the class that is used for navigation items such as links, categories and dividers. When initialized, we use nav to represent it. It contains methods such as append(), appendCategory(), appendDivider(), appendLink(), and more.


navire uses a simple two-step approach to build navigation:

  1. Build the full navigation tree.
  2. Traverse the tree and build the front-end.

Let's take a look at Step 1:

// whether to display the category nav item
const shouldShowCategory = false;

// Initialize navire
const navire = new Navire(
  // The first parameter initializes navire, you can pass:
  //  - A function, which gives you the Navire instance as its first parameter
  //  - An array directly
  navire => [
    // Every nav item needs to have a type.
    // The types navire currently support are:
    //   ["category", "link", "divider"]
    //   - "category" is used as a container for other nav items.
    //   - "link" is used to represent a navigation link.
    //   - "divider" is used to represent a divider. It can also have a title.
    // More details on each type can be found later in the documentation.
    //
    // We append links and dividers to categories, and we can also append categories
    // to other categories. You can build a navigation tree as deep as you want.
    // Every navire item comes with a "level" property. The level starts at 0 for
    // the root items and increases by one on every nested item, example:
    //  - Link        (index 0, level 0)
    //  - Category    (index 1, level 0)
    //    -- Link     (index 0, level 1)
    //    -- Divider  (index 1, level 1)
    //    -- Link     (index 2, level 1)
    //  - Link        (index 2, level 0)
    //
    // We will now build this tree in code:
    //
    // This is the first item in the navigation menu (index 0, level 0):
    {
      type: "link",
      title: "Title",
      // Since the href of this nav is /title?search=45, currently, this
      // item can only be found by: navire.findByHref("/title?search=45").
      href: "/title?search=45",
      // The `match` field helps navire identify this nav item by href,
      // so navire.findByHref("/title") now matches this element.
      // navire.findByHref("/title?foo=world"), also works, etc...
      match: /\/title/
    },
    {
      // Type "category" is a container for other nav elements, it can have
      // a title and children. (index 1, level 0)
      type: "category",
      title: "Category 1",
      // `show` is a field that can accept a function or boolean.
      // It can be used on any nav item just like you specify `type` and `title`.
      // If the field evaluates to true, the nav item is displayed,
      // otherwise, it is not shown and neither are its children.
      show: shouldShowCategory, // can also be () => shouldShowCategory
      // Just like we passed a function to initialize navire, we can also pass a function
      // here to append children. We can return an array like we did before, or we can use
      // navire's functional style of appending children. The function is invoked with its
      // first parameter `nav`- an instance of `NavireItem`.
      children: /* "Category 1" */ nav => {
        // Anything appended here will be appended to "Category 1" as a child.
        // If the `show` field above evaluates to false, none of these items
        // would be displayed.

        // Note how in the next statement we do not pass { "type": "..." }, since we are
        // explicitly specifying the types by calling the `append${type}` methods.

        // /link1 is the first child (index 0, level 1)
        nav.appendLink({ title: "Link 1", href: "/link1" });
        // equivalent to: { type: "link", title: ... }

        // this is a "divider" with a title (index 1, level 1)
        nav.appendDivider({ title: navire.props.title });
        // equivalent to: { type: "divider", title: ... }

        // /link2 (index 2, level 1)
        nav.appendLink({ title: "Link 2", href: "/link2" });
        // equivalent to: { type: "link", title: ... }
      }
    }
  ],
  // These are props that might be needed while rendering the navigation
  // For example, a web app usually has a title and is placed in the
  // navigation bar. If you are rendering the navigation bar and would like
  // to keep all data related to navbar in one place, you can pass these
  // attributes here. They can then be accessed later as `navire.props.field`.
  // Look at the divider above, the title of the divider will be "Foo".
  { props: { title: "Foo" } }
);

Now that we initialized navire, we can do all sorts of things, ex:

// find category by title
const category1 = navire.findByTitle("Category 1");
// find "Link 1" by href
const link1 = navire.findByHref("/link1");

category1.level; // 0
category1.active; // false

link1.level; // 1
link1.active; // false

// This will set "Link 1" as the active navigation item.
// "Category 1" is the parent of "Link 1" so both will be active
link1.activate();

category1.active; // true
link1.active; // true

Now that you understand the structure of navire a little, we can proceed to Step 2, where we traverse the navigation tree and generate the front-end:

navire.traverse((item, traverseChildren) => {
  // traverse
});

Usage with React.js

An example on using this project with React.js can be found at: navire-react-demo.


Usage with jQuery

An example on using this project with jQuery and Bootstrap can be found at /browser/example/nav.js.

You can start the dev server to see the example by running:

npm run browser:dev

Plugins

Current Tags

  • 1.6.12                                ...           latest (8 months ago)

49 Versions

  • 1.6.12                                ...           8 months ago
  • 1.6.11                                ...           8 months ago
  • 1.6.9                                ...           8 months ago
  • 1.6.8                                ...           8 months ago
  • 1.6.7                                ...           8 months ago
  • 1.6.6                                ...           8 months ago
  • 1.6.5                                ...           8 months ago
  • 1.6.4                                ...           8 months ago
  • 1.6.3                                ...           8 months ago
  • 1.6.2                                ...           8 months ago
  • 1.6.1                                ...           8 months ago
  • 1.6.0                                ...           8 months ago
  • 1.5.2                                ...           8 months ago
  • 1.5.1                                ...           9 months ago
  • 1.5.0                                ...           9 months ago
  • 1.4.2                                ...           9 months ago
  • 1.4.1                                ...           9 months ago
  • 1.4.0                                ...           9 months ago
  • 1.3.0                                ...           9 months ago
  • 1.2.11                                ...           9 months ago
  • 1.2.10                                ...           9 months ago
  • 1.2.9                                ...           9 months ago
  • 1.2.8                                ...           9 months ago
  • 1.2.7                                ...           9 months ago
  • 1.2.6                                ...           9 months ago
  • 1.2.5                                ...           9 months ago
  • 1.2.4                                ...           9 months ago
  • 1.2.3                                ...           9 months ago
  • 1.2.2                                ...           9 months ago
  • 1.2.1                                ...           9 months ago
  • 1.2.0                                ...           9 months ago
  • 1.1.2                                ...           9 months ago
  • 1.1.1                                ...           9 months ago
  • 1.1.0                                ...           9 months ago
  • 1.0.14                                ...           9 months ago
  • 1.0.13                                ...           9 months ago
  • 1.0.12                                ...           9 months ago
  • 1.0.11                                ...           9 months ago
  • 1.0.10                                ...           9 months ago
  • 1.0.9                                ...           9 months ago
  • 1.0.8                                ...           9 months ago
  • 1.0.7                                ...           9 months ago
  • 1.0.6                                ...           9 months ago
  • 1.0.5                                ...           9 months ago
  • 1.0.4                                ...           9 months ago
  • 1.0.3                                ...           9 months ago
  • 1.0.2                                ...           9 months ago
  • 1.0.1                                ...           9 months ago
  • 1.0.0                                ...           9 months ago
Maintainers (1)
Downloads
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 0
Dependencies (3)
Dev Dependencies (6)
Dependents (1)

Copyright 2014 - 2016 © taobao.org |