HTML styleguide

To write HTML, we use the slim template language in our project. There is currently no linter set up for it.

Attribute order

For easier reading of code it can help to have a general attribute order in the HTML.

1. class
2. id, name
3. data-*
4. src, for, type, href, value
5. title, alt
6. role, aria-*

This order is taken from Code Guide by @mdo.

Translation

t is the translation helper used:

t(:'string.identifier')

Please use fully qualified keys in all views. The short form is convenient, but also very cumbersome to refactor (e.g. when renaming or moving views).

You can use %{brand} if you need the global portal name.

Using a symbol (:) for the identifier will take that the identifier is not parsed on every template render.