app/templates/components/page-header.html

{% macro page_header(
  h1,
  size='large'
) %}

  <h1 class="heading-{{ size }}" id="page-header">{{ h1 }}</h1>

{% endmacro %}
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			`{% macro page_header(`
			`h1,`
Update h1 on pill pages to work with new pill Pill pages are: - /notifications - /template-usage - /monthly - /organisations/<organisation_id> - /templates Includes changes to: - the folder-path component - the page-header component ...all their h1s have the same id. 2020-09-03 16:12:25 +01:00			`size='large'`
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			`) %}`

Update h1 on pill pages to work with new pill Pill pages are: - /notifications - /template-usage - /monthly - /organisations/<organisation_id> - /templates Includes changes to: - the folder-path component - the page-header component ...all their h1s have the same id. 2020-09-03 16:12:25 +01:00			`<h1 class="heading-{{ size }}" id="page-header">{{ h1 }}</h1>`
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
			`{% endmacro %}`