Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jekyll #851

Merged
merged 4 commits into from
Sep 23, 2020
Merged

Jekyll #851

merged 4 commits into from
Sep 23, 2020

Conversation

nikolai-b
Copy link
Contributor

Fixes #848

Moving to using a Jekyll. I can incoporate it into the github push workflow but for now I've just done it manually with:

cd jekyll-static
jekyll s -d ../regions_www

@Robinlovelace any thoughts?

Copy link
Member

@Robinlovelace Robinlovelace left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR tackles two issues simultaneously: the need to use Jekyll (I can see the benefits of static site generators but not sure what the benefits would be vs costs of additional complexity for this fairly simple use case and how it would compare with other options such as Hugo) and the need to update the website. I suggest splitting this PR, that adds over 1000 lines and removes 113, into two 'atomic' PRs unless there is a good reason for bundling the two things together. Thinking: that will make it easier to review, with the update to location of links to the accessibility statement being the priority.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Accessibility statement on production
2 participants