Liam Bigelow
Liam Bigelow
Yes! Thanks for pointing that out — I'll need to find a nice way to provide that data through the JS API, but that is very doable 🙂
I think this is probably a good idea, but is something I'll include in a 1.0.0 release, as it might affect users' layouts.
Removing this from the 1.0 epic, but it's something to address in an upcoming Modular UI pivot.
Hi all 👋 I'll be working on this one soon, along with #715 Both will come via a CLI flag to output a file containing information about the index — ...
Hmm, well that needs some more thought 😅 Just to rattle off some thoughts, for context and for myself: Pagefind uses fairly short page IDs, to reduce the size of...
👋 @julbd > you'll have the same bandwidth issue with long ID Correct! That's the limitation. For people loading them all into a client-side bundle, the recommendation would be to...
I don't yet know how to spec this. My initial idea was to have a `data-pagebreak-control` you can add for Page 1. Pagebreak would then add siblings to this element...
Leaving this to simmer until the best spec is established. 1.0 is viable without the page crumbs.
This is a great suggestion, I'll aim to implement this in the next feature release 🙂
Hi @kenmorse — the latest release didn't touch on the UI much, but this is still on my list. There are a few UI-specific tasks lined up that I'll work...