Open mrchrisadams opened 6 years ago
yo @kirel, can you add me and @thenaturalist to the DSSG repo?
Okay, we've got a rough version of this here now
https://nifty-bartik-2380ba.netlify.com/
The corresponding repo and branch is here https://github.com/mrchrisadams/dssg-berlin.github.io/tree/website_redesign
The correct PR for this is PR 10 on the dssg repo:
https://github.com/dssg-berlin/dssg-berlin.github.io/pull/10
For deployment we have two main options.
It's a free service, you get a CDN, and SSL and it will run compilation server side.
It's already set up, for the dev site, so we would tell it to deploy from master, then update the DNS. That's it.
Github pages works by either using jektll, or deploying whatever is in the gh-pages
branch of a repo.
More here - look for Deployment of Project Pages From Your gh-pages branch
https://gohugo.io/hosting-and-deployment/hosting-on-github/#github-project-pages
We would need a deploy script to run locally, or rely on travis to run a deploy script whenever new code is pushed to maser. I think @thenaturalist has already set up travis to generae code, as a kind of 'build check' for the source , so we'd need to adapt the travis script to then either check in the generated HTML code to the gh_pages
branch, or something similar.
@kirel can you let me know which you're happier with doing? Of the two options, netlify seems the simpler one, is free, and is more aimed at making it easier to update public facing websites, built the way static site generators build sites(see https://www.netlifycms.org)
Okay, here's what I'm thinking.
What's left
Goals
Make it easier to:
Signals that would show people doing this
Concrete ways we'd support the goals above, that we could measure easily would be:
Sketching this out
Here's what I'm thinking at the mo, I'll explain a few bits: