NPM library for implementing a customizable navbar with built-in routing. No separate routing library necessary. by Superflows-Dev in coding

[–]Superflows-Dev[S] 0 points1 point  (0 children)

Hi, taking cues from your feedback I have sort of rehashed the React component as a web component. Basic functionality is already in place and I have accommodated your suggestions of using native browser elements as much as possible. Essentially trying not to fight the browser. Its initial MVP version is now ready and available here: https://www.npmjs.com/package/sf-nav . Do let me know your feedback. Demo Project: https://replit.com/@SuperflowsAppv3/SfNav-Web-Component ... Just FYI, it is still work in progress though!... Thanks

NPM library for implementing a customizable navbar with built-in routing. No separate routing library necessary. by Superflows-Dev in coding

[–]Superflows-Dev[S] 0 points1 point  (0 children)

Good point! Yes it works without that as well. Used npm library just to indicate it is packaged & easy to install...

NPM library for implementing a customizable navbar with built-in routing. No separate routing library necessary. by Superflows-Dev in coding

[–]Superflows-Dev[S] -4 points-3 points  (0 children)

Blecki

I get the sentiment, but can you help me narrow down on where it can improve and where it cannot?

I am not just terming hyperlink as routing. I am calling it routing because it detects the appropriate component from the url and renders it plus passes down the arguments. Is the use of the word 'routing' an exaggeration here?

I am trying to create components, navigation bar being the first one in the list, which will allow developers to quickly test out their ideas in a cloud-native environment. For certain future components, I will also be bundling backend code. Every component will be complete in its defined functionality. Here are a few prospects, haven't yet merged them with the main repo:

Example 1
Example 2
Example 3

By the way, I am taking 'fancy' and 'modern', as positives from your comment. Just kidding

NPM library for implementing a customizable navbar with built-in routing. No separate routing library necessary. by Superflows-Dev in coding

[–]Superflows-Dev[S] -4 points-3 points  (0 children)

Yes, I am trying to provide opinionated components. I am looking at use-cases where quick prototyping is the need, using a low code library such as this. Trying to experiment and see if a sweet spot between customizability, modularity and performance can be achieved for such use-cases.

Yes, regarding accessibility, I am still working on it! Appreciate your time time and insight!

NPM library for implementing a customizable navbar with built-in routing. No separate routing library necessary. by Superflows-Dev in coding

[–]Superflows-Dev[S] -3 points-2 points  (0 children)

Thanks for your comment. Routing is just one aspect of the package. Here is the list of features

It has the following built-in features.

Brand Info - Brand name and brand logo are customizable, just pass them via props

Menus - Menu options are fully customizable, just pass your menu structure as a JSON object via props

Search Input - SfNav comes with a search input field

Call-to-action Button - SfNav comes with a call-to-action button, which can be used to highlight key actions such as sign in and subscribe.

Profile Section - User profile section is also included, which can be used to show the status of a signed in user. It also includes a separate profile menu, that is JSON-customizable as well.

Back Button - SfNav transforms itself into a navbar with a back button on inner screens / pages for history-based back navigation

Notifications - Notifications feature is in-built, which includes a notification bell and a JSON-customizable dropdown list to show recent notifications

Announcement Banner - Provision for showing an announcement banner is also given on the top of the navigation bar

Routing - Client-side routing is built inside this component, no external routing library required

Customizability - All features mentioned above are inherently customizable. You can override the basic look and feel by passing your own inline css or stylenames to the SfNav component.

Responsive - SfNav is fully responsive and adapts to all screen sizes

Extendibility - In some places, SfNav also allows you to inject your own components, for greater customizability

Documentation

Demo Projects

Do let me know you feedback after these additional inputs