TODO

- Add https://github.com/RevoTale/no-js as a required way to do the non complex UI
- Add the priority for the techonogies usage for the UI. try to use the pure htmkl first. -> not enoung -> try to achieve it with the html+css -> not enough? -> try to achieve it with html+css + htmx -> not enough? try to achieve it with html+css+htmx+alpine.js->not enough? use NextJs. 
- Reivew the ability to use pattern when `no-js` global class stylesheet defined:
```templ
package components

css cardRoot:hover {
  color: red;
}

css cardRoot() {
  @media (width >= 48rem) {
    padding: 1.5rem;
  }
}
```
- MUST extract repeated typography treatment into shared templ primitives and compose them with local classes. Keep shared font family, weight, casing, and tracking in the primitive; keep per-component size, spacing, and color deltas local unless they are identical too.
  Example: `class={ DisplayHeading(), cardTitle() }` is preferred over repeating `font-family: var(--font-display)` and the same heading tracking in every card, board, and footer title rule.

-  I want rules regarding artchitecture, that abstraction should be created as a reusable module, and being deteministic, even if there is littl ebut more code repeated for the same featue.
- https://chatgpt.com/share/69eca650-3328-832e-b017-382f1d3fc5ab

-----
- ## Translation rules
- Translate UI copy by meaning and page context, not word-for-word.
- Prefer natural product language in the target language over literal technical terms.
- For Ukrainian, translate software “utility/utilities” as “інструмент/інструменти” unless the context specifically means a low-level system utility.
- Avoid infinitive fragments for section descriptions when the English source implies an active subject. Example: “We are sharing code…” -> “Ми ділимося кодом…”, not “Ділитися кодом…”.
- If an English source string is grammatically ambiguous, rewrite the English source first before translating other locales.