Refactoring sorting code to use models instead of JSON data... #8
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
…ed a bunch of other stuff to make it work.
Member
Author
|
If we wanted, we could use JavaScript to filter stuff on a single page rather than making separate pages for every single filter. I chose not to because this is more accessible and takes advantage of the Lektor database query system to filter rather than relying entirely on text search. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
.…which resulted in a bunch of other refactoring to make it all work. This is so that we don't store data externally and can edit it all within Lektor's admin. It also involves less repetition of the same information (previous the title of the GSoC project ideas page was repeated in every filter sub-page).