app/templates/views/verify.html

{% extends "admin_template.html" %}
{% from "components/textbox.html" import textbox %}
{% from "components/page-footer.html" import page_footer %}

{% block page_title %}
GOV.UK Notify | Confirm email address and mobile number
{% endblock %}

{% block fullwidth_content %}

<div class="grid-row">
	<div class="column-two-thirds">
		<h1 class="heading-xlarge">Activate your account</h1>

		<p>We've sent you confirmation codes by email and text message. You need to enter both codes here.</p>

		<form autocomplete="off" method="post">
			{{ textbox(form.email_code) }}
			<span class="font-xsmall"><a href="{{ url_for('.check_and_resend_email_code')}}">I haven't received an email</a></span>
			{{ textbox(form.sms_code) }}
			<span class="font-xsmall"><a href="{{ url_for('.check_and_resend_text_code') }}">I haven't received a text</a></span>
			{{ page_footer("Continue") }}
		</form>
	</div>
</div>

{% endblock %}
Create base forms for registration and sign in Created routes and forms for registration, sign in, and registration from an invite. Also tidied up assets folder, removed copy of fronted toolkit. 2015-11-25 16:21:28 +00:00			`{% extends "admin_template.html" %}`
Add a WTForms-compatible textbox macro This macro: - accepts a WTForm form field as a parameter - renders a form field which follows the GOV.UK Elements patterns, both visually and in markup terms It then changes any page which uses either: - the old, non-WTForms macro or - the old, WTFforms `render_field` macro …to use this new macro and removes both of the old ones. It also adds the option to display hint text above the textbox. 2016-01-11 13:15:10 +00:00			`{% from "components/textbox.html" import textbox %}`
Rename `submit_form` component to `page_footer` Submit form was - a confusing name in itself - not descriptive, because it also has an optional ‘back’ link This commit also puts this component in as many pages as possible, stripping out any hard-coded buttons and links. It replaces any usage of buttons for ‘back’, because these are links, not buttons (ie they don’t change any data). 2016-01-07 20:11:22 +00:00			`{% from "components/page-footer.html" import page_footer %}`
Create base forms for registration and sign in Created routes and forms for registration, sign in, and registration from an invite. Also tidied up assets folder, removed copy of fronted toolkit. 2015-11-25 16:21:28 +00:00
			`{% block page_title %}`
Updated html title [ci skip] 2015-12-01 09:56:46 +00:00			`GOV.UK Notify \| Confirm email address and mobile number`
Create base forms for registration and sign in Created routes and forms for registration, sign in, and registration from an invite. Also tidied up assets folder, removed copy of fronted toolkit. 2015-11-25 16:21:28 +00:00			`{% endblock %}`

Use a Node-based tools for handling assets …or how to move a bunch of things from a bunch of different places into `app/static`. There are three main reasons not to use Flask Assets: - It had some strange behaviour like only - It was based on Ruby SASS, which is slower to get new features than libsass, and meant depending on Ruby, and having the SASS Gem globally installed—so you’re already out of being a ‘pure’ Python app - Martyn and I have experience of doing it this way on Marketplace, and we’ve ironed out the initial rough patches The specific technologies this introduces, all of which are Node-based: - Gulp – like a Makefile written in Javascript - NPM – package management, used for managing Gulp and its related dependencies - Bower – also package management, and the only way I can think to have GOV.UK template as a proper dependency …speaking of which, GOV.UK template is now a dependency. This means it can’t be modified at all (eg to add a global `#content` wrapper), so every page now inherits from a template that has this wrapper. But it also means that we have a clean upgrade path when the template is modified. Everything else (toolkit, elements) I’ve kept as submodules but moved them to a more logical place (`app/assets` not `app/assets/stylesheets`, because they contain more than just SASS/CSS). 2015-12-15 08:20:25 +00:00			`{% block fullwidth_content %}`
Create base forms for registration and sign in Created routes and forms for registration, sign in, and registration from an invite. Also tidied up assets folder, removed copy of fronted toolkit. 2015-11-25 16:21:28 +00:00
			`<div class="grid-row">`
			`<div class="column-two-thirds">`
Amend heading text New heading corresponds to design pattern for confirming accounts 2015-12-02 15:44:07 +00:00			`<h1 class="heading-xlarge">Activate your account</h1>`
Create base forms for registration and sign in Created routes and forms for registration, sign in, and registration from an invite. Also tidied up assets folder, removed copy of fronted toolkit. 2015-11-25 16:21:28 +00:00
Amend line of text 2015-12-02 16:03:31 +00:00			`<p>We've sent you confirmation codes by email and text message. You need to enter both codes here.</p>`
Create base forms for registration and sign in Created routes and forms for registration, sign in, and registration from an invite. Also tidied up assets folder, removed copy of fronted toolkit. 2015-11-25 16:21:28 +00:00
Add a WTForms-compatible textbox macro This macro: - accepts a WTForm form field as a parameter - renders a form field which follows the GOV.UK Elements patterns, both visually and in markup terms It then changes any page which uses either: - the old, non-WTForms macro or - the old, WTFforms `render_field` macro …to use this new macro and removes both of the old ones. It also adds the option to display hint text above the textbox. 2016-01-11 13:15:10 +00:00			`<form autocomplete="off" method="post">`
			`{{ textbox(form.email_code) }}`
Refactor for code_not_received, sign_in, two_factor and verify. 2016-01-05 17:08:50 +00:00			`<span class="font-xsmall"><a href="{{ url_for('.check_and_resend_email_code')}}">I haven't received an email</a></span>`
Add a WTForms-compatible textbox macro This macro: - accepts a WTForm form field as a parameter - renders a form field which follows the GOV.UK Elements patterns, both visually and in markup terms It then changes any page which uses either: - the old, non-WTForms macro or - the old, WTFforms `render_field` macro …to use this new macro and removes both of the old ones. It also adds the option to display hint text above the textbox. 2016-01-11 13:15:10 +00:00			`{{ textbox(form.sms_code) }}`
Refactor for code_not_received, sign_in, two_factor and verify. 2016-01-05 17:08:50 +00:00			`<span class="font-xsmall"><a href="{{ url_for('.check_and_resend_text_code') }}">I haven't received a text</a></span>`
Rename `submit_form` component to `page_footer` Submit form was - a confusing name in itself - not descriptive, because it also has an optional ‘back’ link This commit also puts this component in as many pages as possible, stripping out any hard-coded buttons and links. It replaces any usage of buttons for ‘back’, because these are links, not buttons (ie they don’t change any data). 2016-01-07 20:11:22 +00:00			`{{ page_footer("Continue") }}`
109526520: Implement verify flow When a person registers with a valid mobile number and email address, a code will be sent to each. That person can enter the verify codes and continue to the add-service page. 2015-12-07 16:08:30 +00:00			`</form>`
Create base forms for registration and sign in Created routes and forms for registration, sign in, and registration from an invite. Also tidied up assets folder, removed copy of fronted toolkit. 2015-11-25 16:21:28 +00:00			`</div>`
			`</div>`

Updated html title [ci skip] 2015-12-01 09:56:46 +00:00			`{% endblock %}`