### Summary We have been working on improving the Geo first view (Geo node page) and now ready to be implemented! Started from [the team Sketching session](https://gitlab.com/gitlab-org/geo-team/discussions/-/issues/4944), we have discussed the direction in [the design review](https://gitlab.com/gitlab-org/gitlab/-/issues/217958). We also [validated the concept with users](https://gitlab.com/gitlab-org/ux-research/-/issues/985), and this version is good-to-go now :boom: As it goes to the engineering phase :ping_pong:, we need magic 🔮 from both the front-end and backend. This epic is part of [the UI/UX improvement epic](https://gitlab.com/groups/gitlab-org/-/epics/369). ### Intended users * [Sydney - Systems administrator](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator) ### Proposed Design * [Figma Prototype](https://www.figma.com/file/MYEfBPGuLygUMLAMa4UGkI/WIP-Geo?node-id=1%3A90)  ### What is the type of buyer? * Premium * Ultimate ### Documentation * We should update some parts of the documentation by updating the image and some terminologies. ## Implementation Proposal Pulled from comment thread below: https://gitlab.com/groups/gitlab-org/-/epics/4712#note_449512391 #### Strategy 1. Create an entry point and bootstrap a new Vue instance behind a Feature Flag 2. Create a Vuex store that has the expected state, actions, and mutations to behave like the existing event_hub, legacy store, and API proxy. 3. Use a data-driven approach to create each of the UI sections in a general fashion. 4. Implement Actions in the UI 5. Regression test locally with Feature Flag enabled throughout MRs and before final removal of Feature Flag. 6. Remove FF and add New UI Preview Button based on @nhxnguyen suggestion 7. Remove Preview Button and Legacy Code #### Benefits of Option B Strong usage and example of Results and Efficiency. Less cycles as we can implement larger chunks of the new UI per MR size guidelines Quicker Reviews as only testing new code Current UI stays until we feel we are ready for the cutover. #### Drawbacks of Option B Iteration and Transparency are less of a focus here. Feature Flag is Needed No immediate User Feedback Regressions will only be found if we find them rather than iteratively by users as we push code. Increasing the risk there is something we miss.