Create Design for 90 COS/CYT Landing Page
What problem(s) will it solve?
Users external to the 90 COS/CYT flight may want to know what the flight is about but is currently taken to the MTTL. While the MTTL is the main driver for what CYT does, there's no information on the flights mission, goals, structure, processes, etc. Additionally, links to various pages are put on the MTTL page that may or may not relate to the MTTL. The landing page makes a central location for all links which reduces clutter on the MTTL with unrelated links as well as makes it clear where to post links/information about CYT processes.
What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)."
As an external user to CYT, I'd like a landing page that gives me information about CYT's mission, processes, etc, that allows me to see other information if I desire, so I can more easily understand what CYT does and get to information I deem relevant.
Who is the intended user(s)?
Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas are described here
Users external to the 90 COS/CYT flight
Lay out the expected user experience
What is the single user experience workflow this problem addresses? For example, "The user should be able to use the UI/API/.gitlab-ci.yml with GitLab to " Gitlab UX Docs
- A user navigates to the 90 COS/CYT landing page
- The user reads generic information about the flight, its mission, goals, structure, etc.
- If desired, the user navigates to other areas, such as the MTTL, training roadmap, JQR information, etc.
Proposal
How are we going to solve the problem? Try to include the user journey! Gitlab Journeys
Design a 90 COS/CYT landing page that provides external users with information about the flight in such a way that they can understand what CYT is all about. This page should contain links to other areas such as the MTTL, documentation, Training Roadmap, etc.
Further details
Include use cases, benefits, goals, or any other details that will help us understand the problem better.
Permissions and Security
What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?
The page should be publicly accessible
Documentation
See the Feature Change Documentation Workflow Gitlab Feature Change Workflow
- Add all known Documentation Requirements in this section. See Gitlab Dev Docs
- If this feature requires changing permissions, update the permissions document. See Gitlab Permissions
Update User Documentation
- List any changes necessary to user documentation that this feature affects.
Update Developer Documentation
- List any changes necessary to developer documentation that this feature affects.
Update CYT Overview briefing
- Update overview slides relevant to this feature.
- Is there any other documentation affected?
Availability & Testing
See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: Gitlab Test Planning
This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier.
What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing?
Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance.
- Unit test changes
- Integration test changes
- End-to-end test change
What does success look like, and how can we measure that?
Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this.
- A landing page exists that presents users with information about 90 COS/CYT with links to other areas such as the MTTL, documentation, Training Roadmap, etc.