Frontend Development Guidelines
This document describes various guidelines to ensure consistency and quality across the GitLab frontend team.
Be wary of the limitations that come with using Hamlit.
Working with our frontend assets requires Node (v12.22.1 or greater) and Yarn (v1.10.0 or greater). You can find information on how to install these on our installation guide.
For supported browsers, see our requirements.
Current high-level frontend goals are listed on Frontend Epics.
High-level guidelines for contributing to GitLab.
How we plan and execute the work on the frontend.
How we go about making fundamental design decisions in the GitLab frontend team or make changes to our frontend development guidelines.
How we write frontend tests, run the GitLab test suite, and debug test related issues.
Pajamas Design System
Reusable components with technical and usage guidelines can be found in our Pajamas Design System.
Vue.js Best Practices
Vue specific design patterns and practices.
Vuex specific design patterns and practices.
Axios specific practices and gotchas.
How to use GraphQL.
How to use HAML.
Icons and Illustrations
How we use SVG for our Icons and Illustrations.
General information about frontend dependencies and how we manage them.
How we implement keyboard shortcuts that can be customized and disabled.
Read the frontend's FAQ for common small pieces of helpful information.
See the relevant style guides for our guidelines and for information on linting:
SCSS: our SCSS conventions which are enforced through
- HTML. Guidelines for writing HTML code consistent with the rest of the codebase.
- Vue. Guidelines and conventions for Vue code may be found here.
Best practices for monitoring and maximizing frontend performance.
Frontend security practices.
Best practices for client-side logging for GitLab frontend development.
Running into a Frontend development problem? Check out this guide to help resolve your issue.