Initial Search Support #576
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CGBassPlayer
added
enhancement
…dcasting.com into pagefind-search
…terbroadcasting.com into pagefind-search
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #26
Adds initial support for searching the website using Pagefind. This initial implementation uses the default UI provided by the app and I have only done some color changes to make it readable on the site. The plan is to eventually update it to use a custom UI to match the style of the rest of the website (I am thinking of reusing the cards).
To prevent unused generated pages (See #539), the current implementation uses
data-pagefind-bodyto mark what parts of the site are indexed in the search.When doing local development, the search will not work in the dev docker container as it requires an initial build before pagefind can index the site. For the prod image we are using a multistage build and that just didn't feel worth it for the dev server.