Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Canonical list of standards to reference #177

Open
laras126 opened this issue Apr 8, 2020 · 0 comments
Open

Canonical list of standards to reference #177

laras126 opened this issue Apr 8, 2020 · 0 comments
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed question Further information is requested

Comments

@laras126
Copy link
Contributor

laras126 commented Apr 8, 2020

There is a growing list of established coding standards for working with Larva tools that should worked into our pipeline in some way. In the mean time, these should live in an accessible place for tech leads to reference so these items can be caught in code reviews.

Where should these live?

Some examples of the standards / stylistic guidelines so far:

  • Where to write CSS
    • CSS classes in Twig is the best option
    • Only write CSS classes in prototype JS if they need to be removed in variants, or are from a shared pattern
  • Modules should not include modules
  • Pattern JS:
@laras126 laras126 changed the title List of standards to automate Canonical list of standards to reference Apr 8, 2020
@laras126 laras126 added documentation Improvements or additions to documentation help wanted Extra attention is needed question Further information is requested labels Apr 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant