We need a naming convention for HTML partials

[podliashanyk]

See comments in #2883, starting with #2883 (review).

As mentioned there, we have 4 different ways to indicate partials in NAV:

• Prefix with _ (single underline)
• Postfix filename with -frag
• Postfix filename with -partial
• Put file in /fragments directory

Please, do comment on the reasons why you prefer some options over the other if you have strong opinion on the matter.

[hmpf]

There are two types of partials to consider: those controlled by us, and those not. Those not include the ones django uses to render default form inputs, and whatever templates are in 3rd party apps.

As for /fragments, where? One for all of nav, one per directory, one per app?

[lunkwill42]

Why do we need to consider naming conventions for partials we do not control?

[hmpf]

Django widget templates are partials but never start with an underscore. Have a look at the tree in django.forms.templates. We use this in argus already.

These templates are named after html tags and attributes and can be overridden the same way app templates can be overridden: https://docs.djangoproject.com/en/4.2/ref/forms/renderers/#templatessetting

I like underscore for partials that do more than just one html tag but I also like the django style when using very small partial templates, component style.