-
Notifications
You must be signed in to change notification settings - Fork 348
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
gh-pages: Update Jekyll #3671
gh-pages: Update Jekyll #3671
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @crhallberg, if you don't mind cherry-picking those accessibility fixes to a separate PR, that seems like a good idea -- then if we have trouble getting these major updates to deploy correctly, we can roll them back without losing the other changes.
See below for a question about the deployment process.
Is there somewhere we can see the updated version of the webpage before we commit to deploying it? Is there a way to confirm that the updated version has successfully deployed after this gets merged?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, here goes something....
Jekyll was out of date enough to make standing up a dev instance difficult. These updates help enormously.