jayfreestone
Sticky items
There has been a request for 'sticky' items, and I'm trying to gauge if there is enough interest to warrant adding them.
Premise
The idea is that you would be able to 'stick' items to the end (possibly the beginning) of the visible navigation. These would not be part of the priority evaluation, and would remain no matter what.
Sticky items would provide a way of always including, for instance, 'Contact' in the navigation. Not only would it always be visible, but it would occupy its traditional space at the end of the nav.
Very rough demo:
If sticky items are added, it essentially allows for a 'squishy' middle part of the navigation:
Opposition
The biggest argument against the feature, other than increased complexity, is that if an item is 'high' priority, should it not just be promoted to higher up the list? The use-cases tend to be quite narrow, e.g. sticking 'Contact' to the far right. If the usefulness is so limited it might not be worth the extra size/complexity or dev time.
Hello, and many thanks for this modern implementation, working with flex, etc, I was searching that since a long time !
I have a huge interrest on this blueprint, and even if there is not so much people following and commenting this project, I can provide some arguments to weight the balance in that direction. :)
The rule saying that important items must be always first, applies more for "webapp", when menu items are functional, and you can swap them easily. But in an editorial website, the choice for items order is also… editorial, and not only drived by "the most used ones". For ex, many association or companies will put a "who we are" in first, even if "contact" or "search input" are most used and must be always visible.
So I consider this sticky option very important in order to use in editorial sites, I always considered that as a lack in other libs I used before finding yours :)
Hello, and many thanks for this modern implementation, working with flex, etc, I was searching that since a long time !
I have a huge interrest on this blueprint, and even if there is not so much people following and commenting this project, I can provide some arguments to weight the balance in that direction. :)
The rule saying that important items must be always first, applies more for "webapp", when menu items are functional, and you can swap them easily. But in an editorial website, the choice for items order is also… editorial, and not only drived by "the most used ones". For ex, many association or companies will put a "who we are" in first, even if "contact" or "search input" are most used and must be always visible.
So I consider this sticky option very important in order to use in editorial sites, I always considered that as a lack in other libs I used before finding yours :)
Hey, sorry for the slow reply — somehow missed it in my inbox.
Thanks for the the +1 on the feature. I did originally have it prototyped back in 2019 (!) but haven't really revisited the library since then. Might be tempted to revive things and see how easy it would be to implement, though 🤔