[go: up one dir, main page]

Skip to content

[Meta] Identify emerging modern techniques and best-practices to follow during Rapid Diffs frontend development

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Goal

As we're starting to write the styling portion of Rapid Diffs, it's imperative that we all align on what are the techniques we'd like to take the opportunity to employ.

Criteria

Apart from the techniques already in usage in GitLab's monolith monorepo, we're looking to identify techniques that fall under the following criteria:

  • Improve maintenance
  • Improve accessibility
  • Improve flexibility
  • Have a wide browser support

In essence, assists with complying with our blueprint's Frontend acceptance criteria.

Examples

  • :where() pseudo-class CSS selector (spec)
  • @container directive / Container queries (spec)

How to propose techniques?

In order to keep discussions succinct and to the point:

  1. If your proposal isn't submitted yet:
    1. Add a new thread in this issue if your proposal isn't submitted yet.
    2. Use the following template:
Template
## Proposal: `name of the technique`

* What it is: `explain what it is`
* Why: `explain why this helps us`
* Browser support: `link to a page documenting browser support`
* Examples:  `write some code examples on how this can be used`
* Justification (optional): `if you want, explain in your own words why you think this should be followed by the Rapid Diffs`

How to participate?

Go through the list and vote up with 👍 any proposals you agree with + add comments to the thread as you see fit.

Edited by 🤖 GitLab Bot 🤖