app/templates/views/organisations/add-organisation.html

{% extends "views/platform-admin/_base_template.html" %}
{% from "components/page-header.html" import page_header %}
{% from "components/page-footer.html" import page_footer %}
{% from "components/textbox.html" import textbox %}
{% from "components/form.html" import form_wrapper %}

{% block per_page_title %}
  Create an organisation
{% endblock %}

{% block org_page_title %}
  Create an organisation
{% endblock %}

{% block platform_admin_content %}

  {{ page_header(
    'New organisation',
    back_link=url_for('.organisations')
  ) }}

  {% call form_wrapper() %}
    {{textbox(form.name)}}
    {{ page_footer('Save') }}
  {% endcall %}

{% endblock %}
Add organisations pages to show orgs and create/edit them 2018-02-08 12:19:21 +00:00			`{% extends "views/platform-admin/_base_template.html" %}`
Add GOV.UK Design System style back links The Design System has standardised on back links being at the top of the page, decorated with a small text-coloured arrow. I think this makes more sense than having them at the bottom, because it suggests, in some way, being able to go back before commiting to any of the forms on the page. Whereas the things at the bottom of the page should be performing actions on what’s in the page. The reason for making this change now is that it de-clutters the area around the green buttons. This was presenting a design challenge where multiple levels of interaction were happening in the same form. Moving these back links to the top of the page should mean that, in these complicated forms, there’s one fewer thing to compete for the user’s attention. I’ve componentised this into a `page_header` macro so that the change is easier to roll out and maintain. 2019-04-29 11:44:05 +01:00			`{% from "components/page-header.html" import page_header %}`
Add organisations pages to show orgs and create/edit them 2018-02-08 12:19:21 +00:00			`{% from "components/page-footer.html" import page_footer %}`
organisation dashboard page 2018-02-14 13:08:44 +00:00			`{% from "components/textbox.html" import textbox %}`
Use a macro for form tags This will stop us repeatedly forgetting to add `novalidate` and `autocomplete='off'` to our forms (which is how most of them are set up). It uses sensible defaults, based on how we most-commonly configure forms: - most of our forms are `post`ed (but this can be overridden) - `autocomplete` should only be enabled where it makes sense, otherwise it’s more annoying than useful (but this can be overriden) - we should never be using HTML5 form validation because our own error styles and messages are better 2018-09-19 12:39:36 +01:00			`{% from "components/form.html" import form_wrapper %}`
Add organisations pages to show orgs and create/edit them 2018-02-08 12:19:21 +00:00
Add title 2018-02-08 15:41:31 +00:00			`{% block per_page_title %}`
organisation dashboard page 2018-02-14 13:08:44 +00:00			`Create an organisation`
Add title 2018-02-08 15:41:31 +00:00			`{% endblock %}`

link-service-to-organisations-tweaks 2018-02-14 16:13:11 +00:00			`{% block org_page_title %}`
organisation dashboard page 2018-02-14 13:08:44 +00:00			`Create an organisation`
Add organisations pages to show orgs and create/edit them 2018-02-08 12:19:21 +00:00			`{% endblock %}`

			`{% block platform_admin_content %}`

Add GOV.UK Design System style back links The Design System has standardised on back links being at the top of the page, decorated with a small text-coloured arrow. I think this makes more sense than having them at the bottom, because it suggests, in some way, being able to go back before commiting to any of the forms on the page. Whereas the things at the bottom of the page should be performing actions on what’s in the page. The reason for making this change now is that it de-clutters the area around the green buttons. This was presenting a design challenge where multiple levels of interaction were happening in the same form. Moving these back links to the top of the page should mean that, in these complicated forms, there’s one fewer thing to compete for the user’s attention. I’ve componentised this into a `page_header` macro so that the change is easier to roll out and maintain. 2019-04-29 11:44:05 +01:00			`{{ page_header(`
			`'New organisation',`
			`back_link=url_for('.organisations')`
			`) }}`

Use a macro for form tags This will stop us repeatedly forgetting to add `novalidate` and `autocomplete='off'` to our forms (which is how most of them are set up). It uses sensible defaults, based on how we most-commonly configure forms: - most of our forms are `post`ed (but this can be overridden) - `autocomplete` should only be enabled where it makes sense, otherwise it’s more annoying than useful (but this can be overriden) - we should never be using HTML5 form validation because our own error styles and messages are better 2018-09-19 12:39:36 +01:00			`{% call form_wrapper() %}`
link-services-to-organisations 2018-02-12 09:26:13 +00:00			`{{textbox(form.name)}}`
Add GOV.UK Design System style back links The Design System has standardised on back links being at the top of the page, decorated with a small text-coloured arrow. I think this makes more sense than having them at the bottom, because it suggests, in some way, being able to go back before commiting to any of the forms on the page. Whereas the things at the bottom of the page should be performing actions on what’s in the page. The reason for making this change now is that it de-clutters the area around the green buttons. This was presenting a design challenge where multiple levels of interaction were happening in the same form. Moving these back links to the top of the page should mean that, in these complicated forms, there’s one fewer thing to compete for the user’s attention. I’ve componentised this into a `page_header` macro so that the change is easier to roll out and maintain. 2019-04-29 11:44:05 +01:00			`{{ page_footer('Save') }}`
Use a macro for form tags This will stop us repeatedly forgetting to add `novalidate` and `autocomplete='off'` to our forms (which is how most of them are set up). It uses sensible defaults, based on how we most-commonly configure forms: - most of our forms are `post`ed (but this can be overridden) - `autocomplete` should only be enabled where it makes sense, otherwise it’s more annoying than useful (but this can be overriden) - we should never be using HTML5 form validation because our own error styles and messages are better 2018-09-19 12:39:36 +01:00			`{% endcall %}`
link-services-to-organisations 2018-02-12 09:26:13 +00:00
Add organisations pages to show orgs and create/edit them 2018-02-08 12:19:21 +00:00			`{% endblock %}`