Separate field tips by division

[dfaulken]

I suggested that if VATCo-oriented field tips were to prove to be confusing for SATCo drivers, it might be possible to develop a system to have separate hardcoded field tips for separate divisions.

[dfaulken]

Jamin / Dave K to send us a list.

[sherson]

We should remind them for this.

[dfaulken]

I don't believe we've received this input.

Once we have it, the best approach would likely be to create a file similar to locales/en.yml, but rather than storing the English 'translation' of each attribute, it would store the SATCo and VATCo field tips where applicable, perhaps organized by the internal ID of the division objects.

Then create a view helper which will display a given field in the form and dynamically look up its corresponding tip based on the division of the driver/supervisor currently viewing the edit page.

Finally use this view helper in the edit view.

[sherson]

Another item for the list of things to remind PVTA about