feat: migrate from Jekyll to VitePress#171
Merged
Merged
Conversation
…rop deprecated MS Tile meta
… and js-yaml 4.1.1
…ne fix to script setup
Member
Author
|
@zarr-developers/steering-council would any one of you have time to review this as the website stewards? Thanks in advance for your time 🙏 |
Merged
Contributor
|
Great work Max! LGTM. |
Contributor
|
Post merge, https://zarr-developers.github.io/ is working but https://zarr.dev/ is not This is what the current configuration looks like 
If I set the domain as zarr.dev, it says it is improperly configured. 
It's puzzling that it was working before... |
Member
|
Seems like we need to add a CNAME record for www.zarr.dev to zarr-developers.github.io. |
Member
|
zarr.dev seems to work now |
Contributor
I'm still getting 404, but I assume that's because DNS changes are still propagating. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR implements the proposal from #167.
Preview: https://zarr-developersgithubio--171.org.readthedocs.build/en/171/
I was motivated to finally do this because I'll be presenting on Zarr at EGU next week and would love to link to more modernized website and it would be nice to have a nicer homepage to advertize the new features in zarr-python 3.2.0.
I deliberately minimized stylistic/content changes to hopefully make the review process easier. Those could be more easily addressed in follow-up PRs with the new VitePress setup.
On merge, the repo's GitHub Pages source should change from "Deploy from a branch" to "GitHub Actions" (Settings → Pages). Without this, the deploy keeps using the old Jekyll build.
Before / After