Tighten docs for 2i2c access

[jules32]

https://nasa-openscapes.github.io/earthdata-cloud-cookbook/policies-admin/leading-workshops.html#using-the-openscapes-2i2c-hub-in-a-workshop

Looking for the "freshdesk" email with Mahsa, hard to find the above page here - went to the Workshops & Hackathons subpage (let's rename that one)

Also to add and build out from ESIP fledging slides

And, update JupyterHub form with text about Usage policies (for tutorials, not bigger dev) and maybe another column about which DAAC working with?

[jules32]

@mjami00 - when you prepare for your next workshop, shall we cowork and maybe I can help update these docs as you prepare and reach out to 2i2c? I'm sure others would want to join too to learn and help

[ateucher]

Re renaming "Workshops and Hackathons", we could call it "Previous Workshops and Hackathons" or something - that's probably a bit long but to disambiguate from administration of workshops.

[jules32]

Other thoughts from Coworking: Better flow If you're organizing a workshop, there's no "Step 1, Step 2, Step 3"

• could likely merge 2i2c Hub access and Leading workshops
• navbar titles
• 2i2c Hub access is a subset of leading workshops
• maybe "leading" workshops is wrong word

Luis: how to make this forkable - structure this in a way

• hey you want to org a workshop, here are the steps

[jules32]

Slides from ESIP session on Fledging; 42-51 are about Fledging