Epic: Quickstart, Getting Started, Language Pages Restructure

[Cahllagerfeld]

Describe your feature

We should think about a concept about what to do with the quickstarts after reviving the language pages. On the one hand, we have the quickstarts, which link to a Github-Repo, that acts as a reference, on the other hand, these quickstart detail pages are very generic and even unindexed from SEO. When leveraging the language pages, we may have redundant information, which leads to multiple sources of truth.

User impact

We should provide a single point of truth for having quickstarts, so it's clear to users where their language-specific entry point for Gitpod is.

Additional context

No response

---

TODOs

• [ ] #2709
• [ ] #2708

[Nancy-Chauhan]

Next steps:

Merge Getting Started and Language section

• [ ] Create a concept on how to bring these pages together
• [ ] Create Template that can be applied to the languages
• [ ] Apply Template to the language pages
• [ ] Choose 5 languages

Suggested 5 Languages

1. Java
2. Rust
3. Javascript/Typescript
4. Python
5. Go

CC @loujaybee