Skip to content

Outline of FE Vision Doc

What does this MR do and why?

As our frontend codebase continues to grow, it's essential to have a clear, unified vision for our development journey. This document outlines the desired technical state of GitLab's frontend code over the next few years. It should serve as a guide to help us navigate through the constantly changing world of frontend development, ensuring that we're not only keeping pace but leading in our field.

By detailing our strategies, this document will act as a roadmap for frontend engineering team members and contributors. It highlights areas where we need to adapt, innovate, or maintain our current practices. Most importantly, it will aid in prioritizing our capacity effectively, focusing our global efforts on areas that align with our long-term vision.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #426155

Merge request reports