The configuration for PageFind needs to respect the relative path to where it is installed for linked content. This will let the PageFind work on an individual site on a development machine and when the website is published via GitHub.
Here's an example script element.
<script>
window.addEventListener('DOMContentLoaded', (event) => {
new PagefindUI({
element: "#search",
basePath: "./",
});
});
</script>
The second problem is that you should be able to link directly to a search result via the q= parameter. I need to integrate that into this JavaScript template.
The configuration for PageFind needs to respect the relative path to where it is installed for linked content. This will let the PageFind work on an individual site on a development machine and when the website is published via GitHub.
Here's an example script element.
The second problem is that you should be able to link directly to a search result via the
q=parameter. I need to integrate that into this JavaScript template.