Collections-based projects #19
Open
Conversation
This file contains 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
Only one word of difference from the JSON-based one: the main array is just `site.projects` now.
The main collection-based projects file, and again the only difference is the name of the main array.
This is sort of an extended .gitkeep file. Add more posts like that in the gh-pages branch.
A counterpart to projects.md.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The current system for projects is based on a JSON file in _data, which is quite cumbersome to maintain because for the most part it has duplicate data. You mostly want to write about your projects in the very same website you're on, and thus you'd have to copy the name, date, url, image, etc. information to the JSON file verbatim every time. That's not very efficient at all.
This pull request introduces projects based on collections: each project is its own page, and the projects page displays information about each of them by parsing the page metadata instead of the JSON file.
Generally I'd imagine that this approach would be much more useful than the JSON-based approach, and the changes needed are completely minimal (just apply the changes to
_config.yml, changesite.data.projectstosite.projectseverywhere, and changenametotitlein the layout), so it could replace the JSON-based system altogether. But it can live alongside it as well.Also, so that the page looks useful (with more than one entry), the
gh-pagesbranch should have some more project pages (based on the JSON entries, perhaps).