Implementation details

The code for the lessons doesn't live in the Playground. It lives in the Go Website repo, and all the lessons data is dynamically bundled as a JSON response.

3 approaches are possible to create ~100 links to the Playground:

a. Manually create ~100 links in the Playground, then commit them in the Website repo

This operation would also be needed for individual lessons, every time a lesson is modified or created.

b. Modify the Playground to accept snippet as URL parameter

Playground permalinks contain just an ID, e.g. https://go.dev/play/p/mlJaiM_fEX_Y

If the Playground also accepted the full text of a short program e.g. https://go.dev/play/z/package%20main%0A......., it would be straightforward to have the Tour create a link containing whatever is in the code box.

c. Automate the creation of ~100 links at Website build time

A script may "save" ~100 snippets in the Playground, receive the permalinks, and deploy the list of permalinks alongside the website.

Notes

• a Playground permalink is "stable", as submitting the same full code twice produces the same permalink.
• a Playground permalink is durable, entries don't automatically go away.

cc @jamalc

The need for a Playground link would become somewhat obsolete if/when #1437 is resolved with a proper accessible code editor.