Direct link to Editor or reframe page to default to the editor

It feels weird that the landing page is on "Basic App" example. I don't mind the code but it gives me an odd feeling when I click the button to share the app when on the "Basic App"'s example page.

"Am I sharing the 'Basic App' example?" ... "Or am I sharing my code?" ... "Will my shared code have a title of 'Basic Example'?"

I'd like something (a button) near the top left that is similar to "Open Editor" or "Editor" that takes you directly to https://shinylive.io/py/editor/ . TypeScript has a query parameter for which example is being run, similar to our hash. They're default is a Playground landing page which can populate with known examples. If you click in the url bar, the code content is updated, just like our editor does. By landing on the editor/playground page, it is clearer to me that the goal is to write code and share it, not edit pre-existing examples.

I'd like the interaction to feel closer to "I'm editing app code, not I'm editing the Example". (I don't mind defaulting the base code to be the "Basic App" code... I'd just like to not be editing code that belongs to the "Basic App".)

Related:

• Typescript's "Playground"
• babel's "Try it out"

cc @gregswinehart

Start by comparing the current landing page with the /py/editor/ entry point and review the TypeScript Playground and Babel examples linked in the issue. Decide whether the landing page should link directly to the editor or be reframed as a playground. Done means users can clearly tell they are editing and sharing their own app code rather than the Basic App example.