Handling of static files, styling,...

[koeaw]

I think we should discuss/decide on how static files or styling more generally,... should be handled now that most of our JS and CSS has been moved out of our templates and into separate files.

Discussion points:

• file naming scheme
• where should code go/how should it be split up – relevant for overrideability, reusability
  • if/how to divide up Core code (1 file per app or more, if more: how/when/what),
  • file placement, file order, settings which impact load order (event listeners, defer attribute),
  • blocks (placement) for overrides (external code, external code + Core overrides, custom Core code),
• custom styling for custom CSS vs. built-in semantic labelling (e.g. "warning", "danger" colours for elements)

[koeaw]

Related recent comments re: naming of files https://github.com/acdh-oeaw/apis-core-rdf/pull/1234#pullrequestreview-2336720128, re: template tags https://github.com/acdh-oeaw/apis-core-rdf/pull/1242#pullrequestreview-2337663008

[sennierer]

we put all JS in the header and use event listeners and defer to decide when to execute the JS