Active navbar css only about pkgpage.jl HOT 9 CLOSED

PS: of course we could just have both types (side navbar and top navbar) and let the users choose. As long as both options are polished and nice and don't differ too much so that we don't make our life miserable to maintain it 😹

from pkgpage.jl.

right yeah I think for now these would be linked to, I think the scope of this project would (at least now to begin with) to only have a "landing page" that gathers links to e.g. documents :)

(e.g.: https://binarybuilder.org with options)

from pkgpage.jl.

It is a bit problematic because it isn't supported by all browsers. See https://caniuse.com/#feat=css-sticky.

Wouldn't a simple side navbar like on https://getbootstrap.com/docs/4.5/getting-started/introduction/ work better? In any case, I'd not focus on this now, since this is useful only for very long pages.

from pkgpage.jl.

Ok so the only thing I've added thus far is the "smooth" scroll; I've not added the rest maybe have a look and let me know? I think it's cool to highlight which section you're on 🤷‍♂️

I do think the top navbar is nice for a landing page but open to suggestions!

from pkgpage.jl.

ha it's the sticky topnav that you say is not fully supported... hmm, well I'll let you have a go and we can see :D

Edit: it seems supported by most browsers though? (IE11 and opera mini can be ignored...)

from pkgpage.jl.

this: https://github.com/cferdinandi/gumshoe#accounting-for-fixed-headers looks like a simple way to highlight nav items based on scrolling.

from pkgpage.jl.

That is good, just like in https://getbootstrap.com/docs/4.5/components/scrollspy/.

My initial idea is to work on the front-page only (which can be done without JavaScript), then move on to more complex things. But this issue stays as part of working on those more complex things.

from pkgpage.jl.

ha nice scroll spy is great, I assumed it always required jQuery.

and yes definitely, front page only. great if it's js-free! I think the key points of what we would like are:

• single page
• looks good
• limited cruft & responsive
• simple standard entry points so that a nice page can be set up in < 10 minutes by a dev who doesn't want to touch CSS or HTML if s/he can avoid it.

what more complex things are you thinking about?

from pkgpage.jl.

@tlienart Docs and other custom pages, that's what I meant by complex.

from pkgpage.jl.