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, change site.data.projects to site.projects everywhere, and change name to title in 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-pages branch should have some more project pages (based on the JSON entries, perhaps).
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).