Add pangeo launch blog to website

[sgibson91]

Summary

This PR adds a blog post announcing the Pangeo GCP JupyterHub going live to the website.

fixes 2i2c-org/team-compass#272

Note

The preview probably won't show the new blog post since its publication date is in the future. To render the website locally with the blog visible, run hugo serve -DF

[choldgraf]

Will take a look today! @sgibson91 is there a particular date you're going to publish by?

[sgibson91]

@choldgraf Yeah, Monday after I change the DNS records!

[choldgraf]

Thanks for putting this post together @sgibson91 ! I took a pass and made a few suggested edits in this PR:

sgibson91#20

A few quick thoughts:

• I think in general we should follow the practice of "soft launches" - in this case, make a DNS switch, wait several days to make sure things are working as expected, and then make an announcement post. So maybe we can push the publication of this post until Thursday. Does that work for you?
• More generally, we have an incident on the Pangeo hub right now ([Solved] Pangeo Hub has several critical issues infrastructure#815) so we should resolve that before posting this one as well.

I'm happy to iterate on this with you a bit! Let me know what you think

[damianavila]

I think in general we should follow the practice of "soft launches" - in this case, make a DNS switch, wait several days to make sure things are working as expected, and then make an announcement post.

I concur with this general idea, btw...

[sgibson91]

@choldgraf Can I ask you to review and checkout my unresolved comments please?

[choldgraf]

@sgibson91 I opened up an issue for discussing and deciding what to do about support for the Pangeo hub - want to discuss there and then we can update this post once we've converged on an answer?

Issue link: 2i2c-org/team-compass#297

[sgibson91]

want to discuss there and then we can update this post once we've converged on an answer?

Yes, with the caveat that I get anxious about blog posts that languish 😅 Meaning I'd rather have something hand-wavy/"good enough" and get the blog out, say within a week?, than get caught up in the weeds of that discussion and this never gets merged. (That discussion should continue on to a non-hand-wavy solution, of course.)

[sgibson91]

Add new date before merging!!!

[sgibson91]

Thanks @choldgraf - I'm happy with your suggestion! If you agree, I think this is good to merge? (Once the publish date has been updated!)

[sgibson91]

Suggested change

	On **15th November 2021**, the old Pangeo GCP JupyterHub will be shut down, and the project will move forward on the new 2i2c Pangeo Hub.
	On **22nd November 2021**, the old Pangeo GCP JupyterHub will be shut down, and the project will move forward on the new 2i2c Pangeo Hub.

Suggesting a new shutdown date of the old cluster

[choldgraf]

OK excellent - in that case, today I will plan to update the necessary metadata in this PR and then merge in an hour or so 👍

[choldgraf]

I got bogged down in un-breaking some of the documentation infrastructure today, so didn't get to this. But I will publish it tomorrow early on! I also tried adding a little custom social media card template, not sure if my hack will work so if it doesn't I'll revert my latest commit.

[rabernat]

This looks great! I a few more suggestions. The name for our cloud service is officially Pangeo Cloud.

[choldgraf]

ok the post is going live! I'll send out a tweet about it on Twitter as well :-)