<!-- The first section "Release notes" is required if you want to have your release post blog MR auto generated. Currently in BETA, details on the **release post item generator** can be found in the handbook: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator and this video: https://www.youtube.com/watch?v=rfn9ebgTwKg. The next four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended in your first draft, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> ### Problem to solve As a GitLab user, I need excellent documentation so that I can learn more about GitLab infrastructure oriented features. ### Intended users * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) * [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst) * [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops) * [Priyanka (Platform Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#priyanka-platform-engineer) and our buyer personas. ### User experience goal - Create a new landing page for [the Infrastructure docs](https://docs.gitlab.com/ee/user/project/clusters/) - Fix the menu to make it easy to find subpages based on the user's job ### Proposal ### Iteration 1 - [ ] Come up with an information architecture of the final output - [ ] Rewrite the Infrastructure docs landing page - [ ] Create new, follow-up issues for missing pages ### Iteration 2 - [ ] Schedule the new issues from Iteration 1 ### Further details <!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. -->