Reorganize Menus: Get Started and Concepts (no tutorials)

[chendaniely]

Just the get started and concept pages from #250 4751da3
does not include the tutorials.

Does a re-write for the get started introduction, and fixes up the install, create and run pages to include Positron.

• Before we merge this, we should decide where the "Learn Shiny" Button links to on the main index page, or maybe we call that get started and link to the first get started page.

I have a few other ideas for the home page, but that can be a separate PR/discussion.
I put a 👍 on the conversations that have been resolved, and used the 🚀 to signal this conversation was moved to another issue.

TODO

• homepage: Remove install link button
• homepage: Change "Learn" to "Get Started"
• homepage: Use bsicons instead of emoji
• homepage: Use #index p a instead of .homepage-code p a and include color: white
• get-started: alt text for the code snippet
• get-started: maybe resize gallery images to 4x3
• what-is-shiny: check links
  • (built-in theming)
• create-and-run: re-record shiny create video

Bug bash:

• Check links to component #input and #output links to have a slash before the #. e.g., components/#inputs
  • Reorganize Menus: Get Started and Concepts (no tutorials) #261 (comment)
• Review CSS for following appearance and behavior in Safari, desktop and iOS
  • Reorganize Menus: Get Started and Concepts (no tutorials) #261 (comment)
  • Reorganize Menus: Get Started and Concepts (no tutorials) #261 (comment)

[gadenbuie]

• Before we merge this, we should decide where the "Learn Shiny" Button links to on the main index page, or maybe we call that get started and link to the first get started page.

Let's link "Learn Shiny" to the first Get Started page

[cpsievert]

Suggested change

	In fact, Shiny for Python is built on standard HTML
	In fact, a Shiny frontend can be built entirely from HTML, and is compatible with any JavaScript framework.

[gadenbuie]

idk, I think what we're trying to communicate here is the classic, it's just standard web stuff in the end. At this stage, I think that's a compelling thing to say. Two practical consequences of this choice are:

1. you can use Shiny to learn about developing for the web (and lots of people have!) by inspecting our UI elements
2. you're not locked in to what we've made for you, you can always make components or apps that work with things we haven't included.

I like the idea of folding React (or other frameworks) into this section, but I think "compatible with any JavaScript framework" oversells the connection in a way that will miss people who would find the points above compelling, but would be underwhelming to people who are familiar with React or other frameworks and who might think this means it's easy to swap out frameworks.

[gadenbuie]

I updated this section to blend the above ideas

[cpsievert]

LGTM once nitpicks are addressed, thanks!