darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-09-04 07:48:25 -04:00
Code Issues Packages Projects Releases Wiki Activity
Files
aa8529b5bbeffbf3229aed6fc8ae4ef04e55844e
notifications-admin/app/templates/views/organizations/add-organization.html

38 lines
1.2 KiB
HTML
Raw Normal View History

Use same layout as other organisation pages So it feels consistent from moving from one page to another, rather than jumping in and out of the platform admin view.
2019-07-02 09:49:00 +01:00
{% extends "withoutnav_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 %}
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 %}
a few more organisation edits
2023-01-05 21:33:15 -05:00
New organization
Add organisations pages to show orgs and create/edit them
2018-02-08 12:19:21 +00:00
{% endblock %}
Update content area blocks in descendent pages GOV.UK Frontend's template wraps all content in a `<main>` tag and puts it in the main column. Some of Notify's pages need to reach out of the main column (product page). Some have several blocks of navigation before the main content area. This adjusts the blocks in all the templates where this is the case so those conditions can be met.
2019-10-11 16:44:17 +01:00
{% block main %}
<div class="govuk-width-container">
- Removed links to the gov uk stylesheets - Deleted /stylesheets folder - Removed sass build from gulpfile - Changed gov links to usa links - Changed other govuk styles, like breadcrumbs - Changed name of uk_components file to us_components - Fixed a few tests that broke on account of the changes
2023-08-08 16:19:17 -04:00
<div class="navigation-service usa-breadcrumb">
<a href="{{ url_for('.organizations') }}" class="usa-link navigation-service usa-breadcrumb__link usa-breadcrumb-back-to">All organizations</a>
<a href="{{ url_for('main.choose_account') }}" class="usa-link navigation-service usa-breadcrumb-switch">Switch service</a>
Use same layout as other organisation pages So it feels consistent from moving from one page to another, rather than jumping in and out of the platform admin view.
2019-07-02 09:49:00 +01:00
</div>
Add organisations pages to show orgs and create/edit them
2018-02-08 12:19:21 +00:00
Changing the govuk grid to USWDS
2023-08-23 16:18:25 -04:00
<div class="grid-row">
<div class="grid-col-3">
Update content area blocks in descendent pages GOV.UK Frontend's template wraps all content in a `<main>` tag and puts it in the main column. Some of Notify's pages need to reach out of the main column (product page). Some have several blocks of navigation before the main content area. This adjusts the blocks in all the templates where this is the case so those conditions can be met.
2019-10-11 16:44:17 +01:00
&nbsp;
Use same layout as other organisation pages So it feels consistent from moving from one page to another, rather than jumping in and out of the platform admin view.
2019-07-02 09:49:00 +01:00
</div>
Changing the govuk grid to USWDS
2023-08-23 16:18:25 -04:00
<div class="grid-col-9">
Removing govuk utility classes
2023-08-25 11:38:07 -04:00
<main class="govuk-main-wrapper column-main" id="main-content" role="main" >
Update content area blocks in descendent pages GOV.UK Frontend's template wraps all content in a `<main>` tag and puts it in the main column. Some of Notify's pages need to reach out of the main column (product page). Some have several blocks of navigation before the main content area. This adjusts the blocks in all the templates where this is the case so those conditions can be met.
2019-10-11 16:44:17 +01:00
{% block beforeContent %}{% endblock %}
{% block content %}
a few more organisation edits
2023-01-05 21:33:15 -05:00
{{ page_header('New organization') }}
Update content area blocks in descendent pages GOV.UK Frontend's template wraps all content in a `<main>` tag and puts it in the main column. Some of Notify's pages need to reach out of the main column (product page). Some have several blocks of navigation before the main content area. This adjusts the blocks in all the templates where this is the case so those conditions can be met.
2019-10-11 16:44:17 +01:00
{% call form_wrapper() %}
Update RenameOrganisationForm with new fields Changes its StringFields to GovukTextInputFields. This change also affects NewOrganisationForm, which inherits from RenameOrganisationForm. Also includes changes to templates that use this form and associated tests.
2020-08-04 16:32:40 +01:00
{{ form.name }}
blunt rename of org (#620)
2023-07-12 12:09:44 -04:00
{{ form.organization_type }}
Update content area blocks in descendent pages GOV.UK Frontend's template wraps all content in a `<main>` tag and puts it in the main column. Some of Notify's pages need to reach out of the main column (product page). Some have several blocks of navigation before the main content area. This adjusts the blocks in all the templates where this is the case so those conditions can be met.
2019-10-11 16:44:17 +01:00
{{ page_footer('Save') }}
{% endcall %}
{% endblock %}
</main>
</div>
</div>
Use same layout as other organisation pages So it feels consistent from moving from one page to another, rather than jumping in and out of the platform admin view.
2019-07-02 09:49:00 +01:00
</div>
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 %}
Reference in New Issue Copy Permalink