331 MainNavigation Component #341
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit c7448f0:
|
Add a navbar component with sections including header, body, and footer. Also supports creating a list of strings with onclicks that become standard navigation options. Has options for moving and hiding the body to accomodate mobile devices. Also exposes client side functions for getting scroll speed and position. re Headstorm#341
…dry-ui into 331-main-nav
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added a top navigation bar component. It accepts react nodes for header, body, and footer. The body will also accept
navButtons, which are links in the form of buttons withonClicks, for an easy API for simple navigation. The body can also be hidden withhideBodyor placed beneath the main bar withbodyBelow. It also exposes functions for getting scroll position and scroll speed for those utilizing client-side rendering (SSR must be custom).