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

Refresh of webpage #31

Merged
merged 3 commits into from
Jan 6, 2022
Merged

Refresh of webpage #31

merged 3 commits into from
Jan 6, 2022

Conversation

joshmoore
Copy link
Member

fix #29

@joshmoore
Copy link
Member Author

joshmoore commented Dec 14, 2021

While preparing to set the CNAME for this repository, I realized that the old pages will not redirect to the new ones:

https://zarr-developers.github.io/about/ --> https://zarr.dev/about

Options:

  1. don't worry about the redirects. (lose google ranking, etc.)
  2. leave this repo as is and create a new https://github.com/zarr-developers/zarr.dev one, redirecting manually (maybe the best?)
  3. keep this URL but have zarr.dev redirect here (older, longer URLs hang around)
  4. put a proxy at zarr.dev and dynamically host this content (needs work)

@joshmoore
Copy link
Member Author

https://zarr.dev/ is live as a copy as an example of option 2 but the redirection is not yet in place.

@jakirkham
Copy link
Member

Just to confirm how were you setting the CNAME?

@jakirkham
Copy link
Member

jakirkham commented Dec 17, 2021

When we made this change in conda-forge (which was a while back and my memory is fuzzy) ( conda-forge/conda-forge.github.io#402 ), we added an entry to Cloudflare to handle redirections. Guessing we need to do something similar here with Namecheap?

Maybe this is relevant?

@joshmoore
Copy link
Member Author

Guessing we need to do something similar here with Namecheap?

Since the old site is github.io I don't think we will be able to do anything at the DNS level.

@joshmoore
Copy link
Member Author

Just to confirm how were you setting the CNAME?

by setting a CNAME here: https://github.com/zarr-developers/zarr.dev/blob/main/CNAME

@jakirkham
Copy link
Member

We may also need to configure things on this page. In particular "Custom domain" to be the domain we want

https://github.com/zarr-developers/zarr-developers.github.io/settings/pages

@joshmoore
Copy link
Member Author

We may also need to configure things on this page. In particular "Custom domain" to be the domain we want

That will be an option 1 scenario. https://zarr-developers.github.io/ as it currently exists will no longer be reachable, breaking google searches, etc.

@jakirkham
Copy link
Member

Sorry maybe I'm missing something. Was trying to see if we could get to 4. The suggestion above may not be all of the story, but perhaps part of what is needed

@jakirkham
Copy link
Member

Guessing we want 301 from this page, but feel free to correct me if I'm missing something

@joshmoore
Copy link
Member Author

joshmoore commented Dec 17, 2021

Agreed, but I don't know anyway to do that at the site level. #32 will do it page for page which is what we did here: ome/blog#75, effectively replacing this PR.

@jakirkham
Copy link
Member

I think individual sites under the domain reroute automatically after putting in the domain redirection

For example with conda-forge, https://conda-forge.github.io/docs -> https://conda-forge.org/docs

Though maybe I'm misunderstanding the question

@joshmoore
Copy link
Member Author

I think that's correct just we can't do that for something we don't own (github.io)

@jakirkham
Copy link
Member

For clarity, this also works https://conda-forge.github.io/ -> https://conda-forge.org/

Though maybe I'm still not following the concern being raised. Could you please share an example of the kind of thing we are concerned about not working here?

@joshmoore
Copy link
Member Author

joshmoore commented Jan 6, 2022

For clarity, this also works https://conda-forge.github.io/ -> https://conda-forge.org/

@jakirkham: do other sub-pages from conda-forge.github.io redirect?

Edit: Ah, I see they do. But I can only imagine that GitHub is doing this, not conda-forge's DNS entries. So as long as we don't rename the repository to zarr.dev then perhaps just setting the CNAME would suffice.

@joshmoore joshmoore merged commit 3a383b5 into zarr-developers:master Jan 6, 2022
@joshmoore joshmoore deleted the refresh branch January 6, 2022 10:30
@joshmoore
Copy link
Member Author

Update:

  • I disabled github.com/zarr-developers/zarr.dev --> https://zarr.dev
  • Pushed a CNAME of "zarr.dev" to zarr-developers.github.io
  • The redirects worked as John promised (as long as this repo's name never changes!)
  • Then I merged the zarr.dev branch into the mainline here, completing the refresh.

@jakirkham
Copy link
Member

That's great! 🎉 Thanks Josh 😀

@jakirkham
Copy link
Member

Updated the GitHub org URL to link directly to https://zarr.dev ( instead of https://zarr-developers.github.io as it was previously )

Screen Shot 2022-06-01 at 2 17 50 AM

@MSanKeys963
Copy link
Member

Thanks, @jakirkham.

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.

Blog refresh
3 participants