Convert site to Jekyll. #74
Merged
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
davidzchen
force-pushed
the
site
branch
3 times, most recently
from
bee59fa to
04d1a98
Compare
|
Rebased and resolved merge conflicts. |
|
Thanks. I'm in favor of this but I need to understand better what you've actually done here. We should talk about it face to face next week. |
|
Sounds good to me. |
davidzchen
force-pushed
the
site
branch
3 times, most recently
from
faf6c4e to
501a233
Compare
|
I have rebased this patch and added pages to redirect users visiting the pages at the old URL to the new locations for the pages. I have all the pages locally. |
* Converted Jsonnet website to Jekyll. * Add tooling for building the Jekyll tree, bringing up the site locally, and pushing a new version of the site to gh-pages * Add page to redirect users to the new URL. * Add redirect pages to redirect users visiting the old pages (under /doc) to the new pages. * Add CNAME file for jsonnet.org domain * Add JS to redirect from http://google.github.io/jsonnet to http://jsonnet.org
|
This is all good, you should merge it when you're comfortable doing so |
This was referenced Nov 20, 2023
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.
locally, and pushing a new version of the site to gh-pages
This is a pretty huge diff. It may be easier to digest by looking at the
sitebranch on my fork: https://github.com/davidzchen/jsonnet/tree/siteThe motivation for using Jekyll is that it is the official static site generator that is supported by GitHub. With this new pipeline, the Jsonnet website will be served out of https://google.github.io/jsonnet rather than https://google.github.io/jsonnet/doc
The way the new pipeline for publishing the site works is the following (see
tools/scripts/push_docs.sh):doc/and the included Jsonnet files fromexamples/andbenchmarks/.git checkout gh-pagesI have also added a script that just builds the Jekyll tree, unzips it in a temp directory, and runs
jekyll serve, which will bring up the site locally, viewable athttp://localhost:4000.