├── .github ├── DISCUSSION_TEMPLATE │ └── rfc.yml ├── PULL_REQUEST_TEMPLATE.md ├── PULL_REQUEST_TEMPLATE │ ├── adr_pr_template.md │ └── research_pr_template.md └── workflows │ └── trello_poster.yml ├── .gitignore ├── ADR ├── ADR000-record-architecture-decisions.md ├── ADR001-implement-continuous-deployment.md ├── ADR002-use-govuk-notify.md ├── ADR003-use-govuk-signon.md ├── ADR004-store-form-schemas-in-an-api.md ├── ADR005-use-shared-runner.md ├── ADR006-use-rust-for-api.md ├── ADR007-store-form-text-data-as-objects.md ├── ADR008-page-ordering-defined-by-pointers.md ├── ADR009-replatforming-to-ECS.md ├── ADR010-rds-configuration.md ├── ADR011-deployment-pipelines.md ├── ADR012-use-rails-api-for-api.md ├── ADR013-use-paper-trail-gem-for-auditing-and-record-backups.md ├── ADR014-add-conditions-to-pages.md ├── ADR015-idp-authentication.md ├── ADR016-use-vite-rails-for-frontend-build.md ├── ADR017-use-paper-trail-for-draft-live-or-some-other-solution.md ├── ADR018-use-govuk-organisation-api.md ├── ADR019-use-amazon-ses.md ├── ADR020-e2e-tests-get-own-repo.md ├── ADR021-use-auth0.md ├── ADR022-use-postgresql-for-form-creation-in-form-admin.md ├── ADR023-use-uid-in-urls.md ├── ADR024-store-allowed-domain-list-as-file-in-forms-deploy.md ├── ADR025-remove-papertrail.md ├── ADR025-use-aasm-to-manage-form-state.md ├── ADR026-paramaterise-common-terraform-roots.md ├── ADR027-scheduled-smoke-tests.md ├── ADR028-use-notify-for-users.md ├── ADR029-use-shield-advanced.md ├── ADR030-use-aws-lambda-to-run-glue-code.md ├── ADR031-use-pagerduty.md ├── ADR032-use-statuspage.md ├── ADR033-swapping-jest-vitest.md ├── ADR034-api-v2-for-forms.md ├── ADR035-offer-amazon-s3-form-submissions.md ├── ADR036-automate-patch-version-bumps.md ├── ADR037-implement-review-apps.md ├── ADR038-add-psql-database-and-solid-queue-to-forms-runner.md ├── ADR039-add-aurora-for-runner.md ├── ADR040-make-container-image-tags-mutable.md ├── ADR041-grant-review-apps-workflow-pull-request-write-access.md ├── ADR041-use-activerecord-encryption.md ├── ADR042-use-amazon-s3-file-uploads.md ├── ADRXXX-architecture-decision-record-template.md └── README.md ├── LICENCE ├── README.md ├── decision-record ├── DR000-use-github-and-the-adr-process.md ├── DR002-no-charges-for-lower-volume-services.md ├── DR003-enough-common-features.md ├── DR004-our-own-designer.md ├── DR005-choosing-insolvency-service-as-first-partner.MD ├── DR006-epics-focus-on-specific-forms.MD ├── DR007-form-is-live-first-then-add-draft.MD ├── DR008-no-charges-at-all-for-using-GOV.UK-Forms.md ├── DR009-who-can-access-authentication.md ├── DRXXX-decision-record-template.md └── README.md ├── design ├── README.md ├── features │ ├── README.md │ ├── confirmation-email-for-form-fillers │ │ ├── README.md │ │ ├── screenshots-v2 │ │ │ ├── README.md │ │ │ ├── confirmation-email-mural-mockup-notify-template.png │ │ │ ├── provide-contact-details-for-support-page-updated-content.png │ │ │ └── what-happens-next-page-new-page-title-and-updated-content.png │ │ ├── version-1.md │ │ └── version-2.md │ ├── detailed-guidance │ │ ├── README.md │ │ ├── screenshots-v2.md │ │ ├── screenshots-v2 │ │ │ ├── README.md │ │ │ ├── add-guidance-help-text.png │ │ │ ├── give-your-page-a-heading-on-add-guidance-page.png │ │ │ ├── hint-text-guidance-text-on-edit-question-page.png │ │ │ └── updated-formatting-markdown-help-text.png │ │ ├── version-1.md │ │ └── version-2.md │ ├── early-access │ │ ├── README.md │ │ ├── screenshots-v1 │ │ │ ├── 001.Editor-notification-banner.png │ │ │ ├── 002.Get-started.png │ │ │ ├── 003.Mou.png │ │ │ ├── 004.Requirements-page.png │ │ │ ├── 005.What-happens-next.png │ │ │ ├── 006.Agreeing-to-mou.png │ │ │ ├── 007.Trial-notification-banner.png │ │ │ ├── forms-product-site-homepage-call-to-action.png │ │ │ └── screenshots │ │ └── version-1.md │ ├── editing-drafts │ │ ├── README.md │ │ └── version-1.md │ ├── form-metrics │ │ ├── README.md │ │ └── version-1.md │ ├── live-draft │ │ ├── README.md │ │ ├── screenshots-v1 │ │ │ ├── 001.Create-a-form-tasklist.png │ │ │ ├── 002.Add-and-edit-questions.png │ │ │ ├── 003.Live-form-view-only.png │ │ │ ├── 004.Your-questions-view-only.png │ │ │ ├── 005.Landing-page-forms-list.png │ │ │ ├── 006.Edit-form-in-draft-tasklist-in-progress.png │ │ │ ├── 007.Edit-form-in-draft-tasklist-completed.png │ │ │ ├── 008.Preview-draft-form.png │ │ │ ├── 009.Make-changes-live.png │ │ │ ├── 010.Changes-are-live-confirmation.png │ │ │ ├── 011.Preview-live-form.png │ │ │ └── 012.Live-form-form-filler-view.png │ │ └── version-1.md │ ├── long-list-autocomplete │ │ ├── README.md │ │ ├── diagrams.md │ │ └── screenshots-v1 │ │ │ ├── 000-what-kind-of-answer-do-you-need.png │ │ │ ├── 001-what-is-your-question.png │ │ │ ├── 002-how-many-options-can-people-select.png │ │ │ ├── 003-create-a-list-of-options-select-one-only-single-fields.png │ │ │ ├── 004-create-a-list-of-options-select-many-single-fields.png │ │ │ ├── 005-create-a-list-of-options-select-many-single-fields.png │ │ │ ├── 006-create-a-list-of-options-select-one-only-text-box.png │ │ │ ├── 007-change-seletion-type-warnings.png │ │ │ ├── 008-change-selection-type-reduce-options-list-edit-options.png │ │ │ ├── 009-change-selection-type-reduce-option-list-on-edit-question.png │ │ │ ├── 010-edit-question-options-list.png │ │ │ └── README.md │ ├── payment-links │ │ ├── README.md │ │ ├── screenshots-v1 │ │ │ ├── 001-create-a-form-optional-task.png │ │ │ ├── 002-add-a-link-to-a-payment-page-on-govuk-pay-error-summary.png │ │ │ ├── 002-add-a-link-to-a-payment-page-on-govuk-pay-error.png │ │ │ ├── 002-add-a-link-to-a-payment-page-on-govuk-pay.png │ │ │ ├── 003-create-a-form-added-payment-link.png │ │ │ ├── 003-success-notification.png │ │ │ ├── 004-create-a-form-return.png │ │ │ ├── 1000-preview-confirmation-still-need-to-pay.png │ │ │ ├── 1001-preview-journey.png │ │ │ ├── 1002-preview-test-email-with-payment-link.png │ │ │ └── README.md │ │ └── version-1.md │ ├── previewing-a-question │ │ ├── README.md │ │ ├── screenshots-v1 │ │ │ ├── 001-Helping users preview their form Mural design.png │ │ │ ├── 002-check-your-question-simple-answer-type.png │ │ │ ├── 002-preview-question-simple-answer-type.png │ │ │ ├── 003-check-your-question-complex-answer-type.png │ │ │ ├── 003-preview-question-complex-answer-type.png │ │ │ └── README.md │ │ └── version-1.md │ ├── routing │ │ ├── README.md │ │ ├── screenshots-v3 │ │ │ ├── 001-create-a-form-question-route-created.png │ │ │ ├── 001-create-a-form.png │ │ │ ├── 002-add-route-from-question.png │ │ │ ├── 003-edit-route-1-is-answered-as.png │ │ │ ├── 003-edit-route-1-take-the-person-to.png │ │ │ ├── 003-edit-route-1.png │ │ │ ├── 004-edit-exit-page.png │ │ │ ├── 005-edit-question-2s-route-branch.png │ │ │ ├── 005-edit-question2s-route.png │ │ │ ├── 006-set-questions-to-skip-after-question.png │ │ │ ├── 006-set-questions-to-skip-take-the-person-to.png │ │ │ ├── 006-set-questions-to-skip.png │ │ │ └── README.md │ │ ├── screenshots-v4 │ │ │ ├── README.md │ │ │ ├── add-a-route-from-a-question.png │ │ │ ├── add-and-edit-your-questions-page-with-routes.png │ │ │ ├── question-xs-routes-with-1-route.png │ │ │ ├── questions-xs-routes-with-2-routes.png │ │ │ ├── set-questions-to-skip-page.png │ │ │ └── your-questions-page-for-a-live-form-with-routes.png │ │ ├── version-1.md │ │ ├── version-2.md │ │ ├── version-3.md │ │ └── version-4-branching-iteration-2.md │ └── user-management │ │ ├── editor │ │ └── readme.md │ │ ├── group-admin │ │ └── readme.md │ │ ├── organisation-admin │ │ └── readme.md │ │ ├── readme.md │ │ └── screenshots-v1 │ │ ├── editor-screenshots │ │ ├── 001-selectorganisation.png │ │ ├── 002-enteryourfullname.png │ │ ├── 003-yourgroup.png │ │ ├── 003-yourgroupswithrequests.png │ │ ├── 004-createanewgroup.png │ │ ├── 005-membersofthisgroup.png │ │ ├── 006-grouppageforatrialgroup.png │ │ ├── 007-tasklistpage-livegroup.png │ │ ├── 007-tasklistpage-trial.png │ │ └── readme.md │ │ ├── group-admin-screenshots │ │ ├── 001-selectorganisation.png │ │ ├── 002-enteryourfullname.png │ │ ├── 003-yourgroup.png │ │ ├── 003-yourgroupswithrequests.png │ │ ├── 004-createanewgroup.png │ │ ├── 005-grouplandingpagefortrialgroup.png │ │ ├── 005-grouplandingpagefortrialgroup2.png │ │ ├── 006-membersofthisgroup.png │ │ ├── 007-Upgraderequest.png │ │ ├── 007-upgraderequest1.png │ │ ├── 008-activegroup.png │ │ ├── 009-addaneditororgroupadmin.png │ │ ├── 010-tasklistpage-active.png │ │ ├── 010-tasklistpage-trial.png │ │ └── readme.md │ │ └── organisation-admin-screenshots │ │ ├── 001.Selectorganisation.png │ │ ├── 002-Entername.png │ │ ├── 003-Grouplandingpage.png │ │ ├── 004-Grouplandingpage.png │ │ ├── 005-Membersofthisgroup.png │ │ ├── 007-Upgradethisgroup.png │ │ ├── 007-Upgradethisgroup2.png │ │ ├── 008-Activegroup.png │ │ ├── 009-Addmembers.png │ │ ├── 010-tasklistpage-active.png │ │ ├── 010-tasklistpage-trial.png │ │ └── readme.md ├── prototype-version-1 │ ├── README.md │ └── screenshots │ │ ├── 001-Form-Home.png │ │ ├── 002-Create-a-form.png │ │ ├── 003-Form-Apply-for-a-juggling-licence.png │ │ ├── 004-Edit-summary-page.png │ │ ├── 005-Edit-confirmation-page.png │ │ ├── 006-Edit-question-1-hint-open.png │ │ ├── 006-Edit-question-1.png │ │ ├── 007-Edit-question-2.png │ │ ├── 008-Form-Apply-for-a-juggling-licence-added-questions.png │ │ ├── 009-Publish-form-Apply-for-a-juggling-licence.png │ │ ├── 101-Preview-start-page.png │ │ ├── 102-Preview-question-1.png │ │ ├── 103-Preview-final-question.png │ │ ├── 104-Preview-Check-your-answers.png │ │ └── 105-Preview-Form-submitted.png ├── prototype-version-2 │ ├── README.md │ ├── edit-question │ │ └── README.md │ ├── form-overview │ │ └── README.md │ ├── name-your-form │ │ └── README.md │ └── screenshots │ │ ├── 001-Form-Home.png │ │ ├── 002-Create-a-form.png │ │ ├── 003-Form-Apply-for-a-juggling-licence.png │ │ ├── 004-Edit-question-1.png │ │ ├── 005-Edit-question-1-hint-open.png │ │ ├── 006-Edit-question-2-What-is-your-date-of-birth.png │ │ ├── 007-Form-Apply-for-a-juggling-licence-added-questions.png │ │ ├── 008-Edit-check-your-answers.png │ │ ├── 009-Edit-form-submitted.png │ │ ├── 010-Publish-form-Apply-for-a-juggling-licence.png │ │ ├── 101-Preview-start-page.png │ │ ├── 102-Preview-question-1.png │ │ ├── 103-Preview-final-question.png │ │ ├── 104-Preview-Check-your-answers.png │ │ └── 105-Preview-Form-submitted.png ├── prototype-version-3 │ ├── README.md │ ├── form-overview │ │ └── README.md │ └── screenshots │ │ ├── 001-GOV.UK-Forms.png │ │ ├── 002-What-is-the-name-of-your-form.png │ │ ├── 003-Form-overview-Apply-for-a-juggling-licence.png │ │ ├── 004-Edit-question-1.png │ │ ├── 005-Edit-question-1-hint-open.png │ │ ├── 006-Edit-question-2-What-is-your-date-of-birth.png │ │ ├── 007-Form-overview-Apply-for-a-juggling-licence-added-questions.png │ │ ├── 008-Edit-check-your-answers.png │ │ ├── 009-Edit-form-submitted.png │ │ ├── 010-Delete-page.png │ │ ├── 011-Publish-form-Apply-for-a-juggling-licence.png │ │ ├── 101-Preview-question-1.png │ │ ├── 102-Preview-final-question.png │ │ ├── 103-Preview-Check-your-answers.png │ │ └── 104-Preview-Form-submitted.png ├── prototype-version-4 │ ├── README.md │ ├── edit-question │ │ └── README.md │ └── screenshots │ │ ├── 001-GOV.UK-Forms-added-forms.png │ │ ├── 001-GOV.UK-Forms.png │ │ ├── 002-What-is-the-name-of-your-form.png │ │ ├── 003-Form-overview-Apply-for-a-juggling-licence.png │ │ ├── 004-Edit-question-1.png │ │ ├── 005-Edit-question-2-What-is-your-date-of-birth.png │ │ ├── 006-Form-overview-Apply-for-a-juggling-licence-added-questions.png │ │ ├── 007-Edit-check-your-answers.png │ │ ├── 008-Edit-form-submitted.png │ │ ├── 009-Delete-page.png │ │ ├── 010-Publish-form-Apply-for-a-juggling-licence.png │ │ ├── 101-Preview-question-1.png │ │ ├── 102-Preview-final-question.png │ │ ├── 103-Preview-Check-your-answers.png │ │ └── 104-Preview-Form-submitted.png ├── prototype-version-5 │ ├── README.md │ └── screenshots │ │ ├── .DS_Store │ │ ├── 001-GOV.UK-Forms-added-forms.png │ │ ├── 001-GOV.UK-Forms.png │ │ ├── 002-What-is-the-name-of-your-form.png │ │ ├── 003-Form-overview-Apply-for-a-juggling-licence.png │ │ ├── 004-Edit-question-1.png │ │ ├── 005-Edit-question-2-What-is-your-date-of-birth.png │ │ ├── 006-Form-overview-Apply-for-a-juggling-licence-added-questions.png │ │ ├── 007-Edit-check-your-answers.png │ │ ├── 008-Edit-form-submitted.png │ │ ├── 009-Delete-page.png │ │ ├── 010-Publish-form-Apply-for-a-juggling-licence.png │ │ ├── 101-Preview-question-1.png │ │ ├── 102-Preview-final-question.png │ │ ├── 103-Preview-Check-your-answers.png │ │ └── 104-Preview-Form-submitted.png ├── prototype-version-6 │ ├── README.md │ └── screenshots │ │ ├── 001-GOV.UK-Forms-added-forms.png │ │ ├── 001-GOV.UK-Forms.png │ │ ├── 002-What-is-the-name-of-your-form.png │ │ ├── 003-1-Task-list-page-tags-focus-create-your-form.png │ │ ├── 003-Create-a-form-Apply-for-a-juggling-licence.png │ │ ├── 004-Add-and-edit-your-questions.png │ │ ├── 005-Edit-question-1.png │ │ ├── 006-Edit-question-2-What-is-your-date-of-birth.png │ │ ├── 007-Add-and-edit-your-questions-added-questions.png │ │ ├── 008-Delete-page.png │ │ ├── 009-Create-a-form-questions-in-progress.png │ │ ├── 010-Edit-form-summary-page-iframe.png │ │ ├── 010-Edit-form-summary-page.png │ │ ├── 011-Create-a-form-declaration-completed.png │ │ ├── 012-Edit-form-submitted-page-iframe.png │ │ ├── 012-Edit-form-submitted-page.png │ │ ├── 013-Create-a-form-what-happens-next-completed.png │ │ ├── 014-Set-the-email-address-for-completed-forms.png │ │ ├── 015-Confirmation-code-sent.png │ │ ├── 016-Create-a-form-email-address-completed.png │ │ ├── 017-Enter-the-confirmation-code.png │ │ ├── 018-Email-address-confirmed.png │ │ ├── 018-The-confirmation-code-has-expired.png │ │ ├── 019-Create-a-form-email-confirmation-completed.png │ │ ├── 020-Are-you-sure-you-want-to-change-this-email-address.png │ │ ├── 021-Publish-form-Apply-for-a-juggling-licence.png │ │ ├── 101-Preview-question-1.png │ │ ├── 102-Preview-final-question.png │ │ ├── 103-Preview-Check-your-answers-before-submitting-your-form.png │ │ └── 104-Preview-Your-form-has-been-submitted.png ├── prototype-version-7 │ ├── README.MD │ ├── screenshots │ │ ├── 001-form-home-landing.png │ │ ├── 001-form-home-with-form.png │ │ ├── 002-form-create-a-form.png │ │ ├── 003-create-form-create-form-statuses-focus.png │ │ ├── 003-create-form-create-form-statuses.png │ │ ├── 003-create-form-including-email-statuses.png │ │ ├── 003-create-form-make-live-focus.png │ │ ├── 003-create-form-privacy-contact-statuses-focus.png │ │ ├── 003-create-form-set-email-statuses-focus.png │ │ ├── 003-create-form.png │ │ ├── 004-form-index-no-questions.png │ │ ├── 005-delete-question-1.png │ │ ├── 005-edit-page-1.png │ │ ├── 006-edit-page-2-saved.png │ │ ├── 007-form-index-questions.png │ │ ├── 008-create-form-question-in-progress.png │ │ ├── 1001-page-preview-new-tab-1.png │ │ ├── 1002-page-preview-new-tab-3.png │ │ ├── 1003-check-answers-page-preview-new-tab.png │ │ ├── 1004-confirmation-page-preview-new-tab.png │ │ ├── 101-edit-page-check-answers.png │ │ ├── 102-edit-page-check-answers-preview-pane.png │ │ ├── 201-edit-page-confirmation.png │ │ ├── 202-edit-page-confirmation-preview-pane.png │ │ ├── 301-set-completed-forms-email.png │ │ ├── 302-confirmation-code-sent.png │ │ ├── 401-add-confirmation-code.png │ │ ├── 402-confirmation-code-expired.png │ │ ├── 403-email-confirmation.png │ │ ├── 501-provide-link-to-privacy-information.png │ │ ├── 601-provide-support-details.png │ │ ├── 701-make-your-form-live.png │ │ ├── 702-form-is-live.png │ │ ├── 703-create-form-live.png │ │ ├── 801-are-you-sure-you-want-to-edit-live-questions.png │ │ └── 802-form-index-live.png │ └── task-list │ │ └── README.md └── service-maps.md ├── diagrams ├── architecture.md ├── class-diagrams │ ├── README.md │ ├── admin.md │ ├── api.md │ └── runner.md ├── form-states-and-events.md ├── images │ └── ADR037-architecture-diagram.png └── sequence-diagrams │ ├── README.md │ ├── authentication.md │ ├── changing-a-form.md │ ├── creating-a-form.md │ ├── file-upload.md │ ├── filling-in-a-form.md │ ├── publishing-a-form.md │ └── review-apps-workflow.md ├── engagement └── README.md ├── product └── readme.md └── research ├── 2021-08-22-complex-logic.md ├── 2022-03-15-EPIC-A-TESTING-SECURITY-FEATURES.md ├── 2022-05-03_Basic_Form_Building.md ├── 2022-05-23_Basic_Form_Building.md ├── 2022-06-16_Accessibility_Testing.md ├── 2022-06-28_Basic_Form_Building.md ├── 2022-06-28_The_Review_Process.md ├── 2022-07-04_Form_Processing.md ├── 2022-08-15_Task_list_and_steps_to_make_form_live.md ├── 2022-08-29_Testing_form_processing_efficiency.md ├── 2022-09-12-MCA_Processing.md ├── 2022-10-17_Mental_Model_Of_Document_Based_Form_Creators.md ├── 2022-10-24_Form_Builder_Usability_Testing.md ├── 2022-10-25_Accessibility_Testing.md ├── 2022-11-23-Feedback_on_processing_of_the_first_form.md ├── 2022-12-05-Autofill_feature.md ├── 2022-12-08_File_Upload_And_Optional_Questions_Processing.md ├── 2022-9-12_Testing_form_processing_efficiency.md ├── 2023-01-31_Usability_testing_with_private_beta_partner_form_creator.md ├── 2023-02-06_Testing_options_for_select-from_list_questions.md ├── 2023-03-03_Accessiblity_Testing.md ├── 2023-04-14_Usability_Testing_Draft_Live_Feature.md ├── 2023-06-07_Usability_testing_Simple_routing.md ├── 2023-08-01_Usability_Testing_Form_Completers copy.md ├── 2023-08-09-Usability_Testing_Authentication.md ├── 2023-08-30_Detailed_Guidance_Usability_Testing.md ├── 2023-09-26-Early_Access_Journey.md ├── 2023-09-26-Form_Completers_Accessibility.md ├── 2023-10-11-Data_And_Analytics.md ├── 2023-11-10-Confirmation_Emails.md ├── 2023-11-17-Accessibility_Testing_Detailed_Guidance_and_Routing.md ├── 2023-11-20-Barriers_to_adoption_research.md ├── 2024-04-15_Usability_Testing_User_Management ├── 2024-06-18-concept_testing_add_another_answer.md ├── 2024-08-28-Add-another-answer-round-2.md ├── 2024-10-24_Branching_round_1.md ├── 2024-11-26-Branching-round-2-usability-testing.md ├── 2024-12-23-Support_Model.md ├── 2024-2-21-Add_a_Payment_Link.md ├── 2025-02-03-Branching_feedback_round_1.md ├── 2025-02-17_Branching_feedback_round_2.md ├── EPIC B MANAGING TWO VERSIONS OF THE SAME FORM.md ├── EPIC-6-HOW TO HELP USERS WHEN THEY CREATE BAD FORMS.md.md └── YYYY-MM-DD-template.md /.github/DISCUSSION_TEMPLATE/rfc.yml: -------------------------------------------------------------------------------- 1 | labels: [rfc] 2 | body: 3 | - type: textarea 4 | id: summary 5 | attributes: 6 | label: Summary 7 | description: | 8 | An abstract, tl;dr, or executive summary of your RFC. 9 | validations: 10 | required: true 11 | - type: textarea 12 | id: problem 13 | attributes: 14 | label: Problem 15 | description: | 16 | Describe the problem your RFC is trying to solve 17 | validations: 18 | required: true 19 | - type: textarea 20 | id: proposal 21 | attributes: 22 | label: Proposal 23 | description: | 24 | Describe your proposal, with a focus on clarity of meaning. You MAY use [RFC2119-style](https://www.ietf.org/rfc/rfc2119.txt) MUST, SHOULD and MAY language to help clarify your intentions. 25 | validations: 26 | required: true -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | # PR Checklist 2 | 3 | - [ ] If you are proposing a new decision record document, used the right template for that 4 | - ([ADR](https://github.com/alphagov/forms/blob/main/ADR/ADRXXX-architecture-decision-record-template.md), [decision-record](https://github.com/alphagov/forms/blob/main/decision-record/DRXXX-decision-record-template.md), engagement, [research](https://github.com/alphagov/forms/blob/main/research/YYYY-MM-DD-template.md)) 5 | - [ ] Set yourself as the Assignee 6 | - [ ] Tag anyone you would like to review, or @forms-design or @forms-devs 7 | - [ ] Fill in the template below 8 | 9 | 10 | --- 11 | 12 | # What 13 | 14 | Describe what you have changed and why. 15 | 16 | # How to review 17 | 18 | Describe the steps required to test the changes. 19 | 20 | For example: 21 | 22 | 1. Semantic: Do you agree with the changes? 23 | 1. Syntactic: Spelling, grammar, etc. 24 | 25 | # Who can review 26 | 27 | Describe who can review the changes. Or more importantly, list the people 28 | that can't review, because they worked on it. 29 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE/adr_pr_template.md: -------------------------------------------------------------------------------- 1 | # This is an ADR PR template 2 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE/research_pr_template.md: -------------------------------------------------------------------------------- 1 | # This is a research PR template 2 | -------------------------------------------------------------------------------- /.github/workflows/trello_poster.yml: -------------------------------------------------------------------------------- 1 | name: Trello Poster 2 | on: 3 | pull_request: 4 | types: [opened, edited] 5 | jobs: 6 | trello-poster: 7 | runs-on: ubuntu-latest 8 | steps: 9 | - uses: lfdebrux/trello-poster-action@26a89a913f861d355dc2867a13c0c013e42d4c77 10 | with: 11 | comment-body: ${{ github.event.pull_request.body }} 12 | github-url: ${{ github.event.pull_request.html_url }} 13 | trello-api-token: ${{ secrets.TRELLO_API_TOKEN }} 14 | trello-api-key: ${{ secrets.TRELLO_API_KEY }} 15 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | **/.DS_Store -------------------------------------------------------------------------------- /ADR/ADR000-record-architecture-decisions.md: -------------------------------------------------------------------------------- 1 | # ADR000: Record architecture decisions 2 | 3 | Date: 2022-01-24 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | As the project progresses, we will make decisions that will have implications for our architecture. It is important that we understand the reasons for these decisions in the future, so that we can understand whether they are still relevant. 12 | 13 | Human memory is unreliable, and our team will change, so we need to document these decisions. 14 | 15 | ## Decision 16 | 17 | We will use Architecture Decision Records, as described in Michael Nygard's [Documenting Architecture Decisions](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions). 18 | 19 | We will keep ADRs in the `ADR` directory of this repository. 20 | 21 | Decisions will be written using Markdown and named `ADR{number}-{name}.md` - for example, `ADR000-record-architecture-decisions.md`. 22 | 23 | ## Consequences 24 | Team members will be able to view the entire decision history of our project. 25 | -------------------------------------------------------------------------------- /ADR/ADR001-implement-continuous-deployment.md: -------------------------------------------------------------------------------- 1 | # ADR001: Implement continuous deployment 2 | 3 | Date: 2022-01-26 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | The GDS Way recommends that teams [use continuous delivery](https://gds-way.cloudapps.digital/standards/continuous-delivery.html#use-continuous-delivery). 12 | 13 | All of our code is currently stored in Github, and our team already has a GOV.UK PaaS account. 14 | 15 | ## Decision 16 | 17 | We will use Github Actions to run our workflows. When we create a new repository, we should set up a deployment workflow which will run after commits on the main branch. 18 | 19 | We will use GOV.UK PaaS for our environments where this is possible. 20 | 21 | ## Consequences 22 | 23 | We expect this to reduce the time between iterations and allow us to get more frequent feedback on our changes. 24 | 25 | We will be able to add automated tests where apppropriate to validate our changes. 26 | -------------------------------------------------------------------------------- /ADR/ADR002-use-govuk-notify.md: -------------------------------------------------------------------------------- 1 | # ADR002: Use GOV.UK Notify 2 | 3 | Date: 2022-04-07 4 | 5 | ## Status 6 | 7 | Superseded by [ADR019 Use Amazon SES](ADR019-use-amazon-ses.md) 8 | 9 | ## Context 10 | 11 | The initial delivery mechanism of GOV.UK Forms submissions will be via email to the form processors. Additionally, to begin with we will be tackling more simple forms, notably ones without additional supporting documents being required on submission (e.g. attaching a photo). 12 | 13 | For people filling in the forms we require a way to send them confirmation emails that their answers were submitted. 14 | 15 | These requirements mean we need a way of sending emails to any email address with multiple different formats, though attachments are optional to begin with. 16 | 17 | The approaches possible consist of using GOV.UK Notify, Amazon SES, or other similar platforms. 18 | 19 | ## Decision 20 | 21 | We have decided to use GOV.UK Notify to send emails to our users for the following reasons 22 | - It's readily used within government 23 | - It has the features we require for early on in our private beta 24 | - Easy to integrate with 25 | 26 | ## Consequences 27 | 28 | As a result of this decision, we will need to create a live GOV.UK Notify account and then in the future we can integrate with this to send our emails. 29 | 30 | However, things we need to keep in mind as we go through private beta and will need to investigate in the future, for example: 31 | 32 | - GOV.UK Notify does not support email attachments, we will need to consider how best manage file uploads and whether or not direct email attachments will be required when those forms are being worked on for the platform. 33 | - GOV.UK Notify does not support adding reply-to email addresses over the API, though you can specify them per email if they've been added in the web UI. 34 | - There are workarounds possible for this, however as we scale these will be less realistic and being able to add them over the API by the user would be required. 35 | - Data sent in the emails will be stored for 7 days, this should be reflected in any relevant policies. 36 | - Although this is only visible to people with API keys, API keys themselves are not scoped from email creation/email history viewing and we should keep this in mind when managing API keys. 37 | -------------------------------------------------------------------------------- /ADR/ADR003-use-govuk-signon.md: -------------------------------------------------------------------------------- 1 | # ADR003: Use GOV.UK Signon 2 | 3 | Date: 2022-04-07 4 | 5 | ## Status 6 | 7 | Superseded by [ADR015: Use an Identity Provider for authentication and implement authorisation](ADR015-idp-authentication.md). 8 | 9 | ## Context 10 | 11 | GOV.UK Forms needs a way of authenticating users who will create and manage forms. 12 | 13 | It would be preferable to make use of an existing authentication system rather than create a new one. We created 2 prototypes to better understand the effort to onboard and the account creation process. 14 | 15 | ## Decision 16 | 17 | Use GOV.UK Signon to authenticate user access to GOV.UK Forms for form creation and management. 18 | 19 | ## Consequences 20 | 21 | We don't have to build a new authentication system, and can start using the GOV.UK Signon Integration environment straight away. 22 | 23 | We still need to decide if/how to use GOV.UK Signon Permissions for authorisation. 24 | 25 | We still need to understand the process for creating accounts in private beta. 26 | 27 | We don't yet know if/how self-service account creation could work. 28 | -------------------------------------------------------------------------------- /ADR/ADR005-use-shared-runner.md: -------------------------------------------------------------------------------- 1 | # ADR005: Use shared runner 2 | 3 | Date: 2022-04-07 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | The forms platform has a "runner", the service that runs the forms itself to the user who is filling them in. 12 | 13 | There are two different ways to approach the runner - a shared runner or a single runner per form. Two existing forms creation services (MOJ Forms, XGovFormBuilder) both use the single tenant approach. 14 | 15 | ### Runner per form 16 | 17 | ```mermaid 18 | flowchart TD 19 | Manager[Form Manager] 20 | A[Form A] 21 | B[Form B] 22 | C[Form C] 23 | D[Form D] 24 | 25 | subgraph RunnerA[Runner] 26 | A 27 | end 28 | 29 | subgraph RunnerB[Runner] 30 | B 31 | end 32 | 33 | subgraph RunnerC[Runner] 34 | C 35 | end 36 | 37 | subgraph RunnerD[Runner] 38 | D 39 | end 40 | 41 | Manager --> RunnerA 42 | Manager --> RunnerB 43 | Manager --> RunnerC 44 | Manager --> RunnerD 45 | ``` 46 | 47 | In this structure, each form has its own runner which serves each form to the end user. This: 48 | 49 | - Limits the impact if one form runner encounters an error 50 | - Makes it more complicated to roll out updates to each runner as we scale 51 | - Requires us to run a server consistently for all forms regardless of traffic, using up money + energy when not required 52 | 53 | ### Shared runner 54 | 55 | ```mermaid 56 | flowchart LR 57 | Manager[FormManager] 58 | subgraph Runner 59 | A[Form A] 60 | B[Form B] 61 | C[Form C] 62 | D[Form D] 63 | end 64 | Manager --> Runner 65 | ``` 66 | 67 | In this structure, there is one runner service that serves forms to the end user. This: 68 | 69 | - Enables us to have easier control over updating the runner where required (dependency version increases, service updates, etc.) 70 | - Enables the ability to scale to the overall load on the forms service, removing the need to run idle servers for forms that have no traffic 71 | - Increases the risk of a problem with one form affecting the performance of others 72 | 73 | ## Decision 74 | 75 | We have decided to use a shared runner to host and run multiple forms. 76 | 77 | ## Consequences 78 | 79 | We will be able to deploy updates to the runner more easily. 80 | 81 | We will be able to scale the service to the total number of people filling in forms, rather than having idle servers for every low use form, reducing energy usage. 82 | 83 | If the runner service encounters an error, all forms will be impacted rather than just one. 84 | -------------------------------------------------------------------------------- /ADR/ADR008-page-ordering-defined-by-pointers.md: -------------------------------------------------------------------------------- 1 | # ADR008: Page ordering defined by pointers to the next page in form objects 2 | 3 | Date: 2022-05-31 4 | 5 | ## Status 6 | 7 | > Accepted 8 | 9 | ## Context 10 | 11 | When the forms runner is reading forms - it needs to be aware of the ordering of pages and how to navigate from one page to the other. 12 | 13 | During private beta we're only considering forms which have no branching paths, however we know this is a future requirement and want to consider how any solution we choose may get extended in the future to support branching. 14 | 15 | ### Option one: Return pages in an array and progress to the next page based on array position 16 | 17 | ```json 18 | { 19 | "pages": [ 20 | { 21 | "id": "first-page" 22 | }, 23 | { 24 | "id": "second-page" 25 | } 26 | ] 27 | } 28 | ``` 29 | 30 | ### Option two: Give pages an "position" value, progress based on the next position value 31 | 32 | ```json 33 | { 34 | "pages": [ 35 | { 36 | "id": "second-page", 37 | "position": 2 38 | }, 39 | { 40 | "id": "first-page", 41 | "position": 1 42 | 43 | } 44 | ] 45 | } 46 | ``` 47 | 48 | ### Option three: Treat pages as a linked list, with a pointer to the next page 49 | 50 | ```json 51 | { 52 | "pages": [ 53 | { 54 | "id": "second-page", 55 | "next": "final-page" 56 | }, 57 | { 58 | "id": "first-page", 59 | "next": "second-page" 60 | }, 61 | { 62 | "id": "final-page" 63 | } 64 | ] 65 | } 66 | ``` 67 | 68 | This takes inspiration from the original submit JSON structure: 69 | 70 | https://github.com/alphagov/submit-prototype-kit/blob/master/examples/simple.json 71 | 72 | ---- 73 | 74 | Of the three options only option 3 gives the ability to extend it in the future for branching purposes as both 1 and 2 are based on a linear ordering whereas 3 gives us the opportunity to expand it in the future, by replacing the string value with an object which can provide the rules for branching. 75 | 76 | ## Decision 77 | 78 | The team has opted to go with option 3. 79 | 80 | ## Consequences 81 | 82 | - We will be able to navigate from one page to the next 83 | - Navigating backwards will be more challenging as we don't have a pointer backwards 84 | - We will be able to support branching in the future 85 | -------------------------------------------------------------------------------- /ADR/ADR009-replatforming-to-ECS.md: -------------------------------------------------------------------------------- 1 | # ADR009: Re-platforming GOV.UK Forms to AWS ECS Fargate 2 | 3 | Date: 2022-10-27 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | GOV.UK Forms currently runs on [GOV.UK PaaS which is being decommissioned in 12 | December 2023](https://gds.blog.gov.uk/2022/07/12/why-weve-decided-to-decommission-gov-uk-paas-platform-as-a-service/) 13 | and all tenants must re-platform. 14 | 15 | ## Decision 16 | 17 | Move GOV.UK Forms onto AWS Elastic Container Service (ECS) with Fargate and supporting 18 | AWS services such as RDS and Elasticache. All infrastructure to be managed with 19 | Terraform. Continuous integration and deployment patterns will be implemented 20 | (technology choices are TBD). 21 | 22 | ## Consequences 23 | 24 | - AWS ECS and supporting AWS services are well understood and used by a number 25 | of other GDS products. We can make use of existing experience and expertise. 26 | - The current and expected future infrastructure requirements of GOV.UK Forms can be met. 27 | - Fargate deployment mode takes care of the underlying VM management to reduce 28 | the maintenance burden. 29 | - High level of confidence that GOV.UK Forms will work as-is with AWS services because they 30 | are already being used by the GOV.UK PaaS implementation (e.g. RDS and 31 | Elasticache). 32 | - Feature development will continue throughout the migration with GOV.UK Forms 33 | being dual deployed to PaaS and ECS until cut-over. 34 | - The GOV.UK Forms team will need to manage more infrastructure since GOV.UK PaaS 35 | will no longer be taking care of much of it. This will require more engineering 36 | time to be spent on building and maintaining infrastructure which will likely 37 | require either up-skilling developers with Site Reliability Engineering (SRE) 38 | skills or adding extra Site Reliability Engineers to the team. 39 | - Some team members will need to learn more about working with AWS services directly. 40 | - The effort required to design and migrate to new infrastructure will reduce 41 | the amount of road map features that can be developed during the migration. -------------------------------------------------------------------------------- /ADR/ADR014-add-conditions-to-pages.md: -------------------------------------------------------------------------------- 1 | # ADR014: Add conditions table to the database 2 | 3 | Date: 2023-02-28 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | In order to implement the simple routing work, we need to store conditions in our database. A condition is a data structure that needs to contain information about how the runner should calculate whether a user should be skipped forward to a certain page in the form, based on their answers to previous questions. For the simple routing information, the IDs for the question being checked, the question where the routing takes place, and the destination question in the case of the condition being met all need to be stored. Additionally, the matching answer to the question being checked also needs to be included. An example of a JSON object condition would look like this. 12 | 13 | ``` 14 | { 15 | "prior_question_id": 1, 16 | "current_question_id": 2, 17 | "goto_question_id": 4, 18 | "answer_value": "Yes", 19 | } 20 | ``` 21 | 22 | We have different options for how we store this information, either as a field on the Page table, or in a separate Conditions table. 23 | 24 | ## Decision 25 | 26 | The team has decided to go with the option of a new Conditions table, which will be associated with Pages. Pages will be able to have multiple conditions, each of which will be represented by a new row in the Conditions table. 27 | 28 | ## Consequences 29 | 30 | Storing conditions as a separate table will allow us to utilise Rails' relational ActiveRecord tools more easily. This means that identifying any and all conditions associated with a given Page will be easy, and will make checking for logical routing errors and alternative routing paths simpler. 31 | 32 | However, if in the future we decide to introduce more complex types of conditions, we may find ourselves slightly constrained by having conditions stored in a table, as opposed to a more freeform JSON object. We may need to introduce a variety of columns to account for different sorts of conditions. 33 | -------------------------------------------------------------------------------- /ADR/ADR015-idp-authentication.md: -------------------------------------------------------------------------------- 1 | # ADR015: Use an Identity Provider for authentication and implement authorisation 2 | 3 | Date: 2023-02-06 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | In [ADR003 Use GOV.UK Signon](ADR003-use-govuk-signon.md) we recognised that 12 | 13 | > We don't yet know if/how self-service account creation could work 14 | 15 | Self-service account management is essential to allow adoption to scale in public beta. This is not going to be possible with GOV.UK Signon so we need to find an alternative way to authenticate our users. 16 | 17 | GOV.UK Signon requires an existing user with an Admin role to either create a new user or give an existing user permission to access GOV.UK Forms. We are looking to implement a self-service model similar to GOV.UK Notify and GOV.UK Pay where users can get initial access without needing an account to be created for them by someone else. User permissions are then managed by other users within the product itself. 18 | 19 | ## Decision 20 | 21 | We will evaluate different [Identity Providers](https://en.wikipedia.org/wiki/Identity_provider) and select one to use instead of GOV.UK Signon. 22 | 23 | ## Consequences 24 | 25 | GOV.UK Forms will need to support multiple identity providers simultaneously so that Signon can continue to be used whilst we evaluate alternatives. 26 | 27 | Authorisation now needs to be implemented directly in GOV.UK Forms. Currently Signon is used to authorise access to Forms and to determine which organisation a user belongs to, so an equivalent concept of Admin roles in GOV.UK Signon needs to be implemented in GOV.UK Forms. 28 | -------------------------------------------------------------------------------- /ADR/ADR020-e2e-tests-get-own-repo.md: -------------------------------------------------------------------------------- 1 | # ADR020: Move the e2e tests into their own repo 2 | 3 | Date: 2023-07-14 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | We have a set of end to end tests which are currently located in the `forms-deploy` repo [here](https://github.com/alphagov/forms-deploy/tree/main/capybara). 12 | 13 | With the constant attention that the tests require, and the expansion of their coverage, it could be beneficial to separate them into their own github repository. This will make updating them; running them; and referring to them easier. 14 | 15 | ### Naming 16 | 17 | Based on other `alphagov` e2e repos, we could go with something like ***`forms-e2e-tests`*** for the repo name. This leaves plenty of room for other test formats i.e. `forms-smoke-tests`. 18 | 19 | ## Decision 20 | 21 | We've decided to create a new repo for the e2e testsg 22 | 23 | ## Consequences 24 | 25 | - We have to (/get to) keep track of a new repo 26 | - Tests can be updated without requiring the `forms-deploy` repo to be in order 27 | - Test repo can have clearer dependencies and environment management 28 | - End to end tests can be public (forms-deploy repo is private) 29 | -------------------------------------------------------------------------------- /ADR/ADR021-use-auth0.md: -------------------------------------------------------------------------------- 1 | # ADR021: Use Auth0 as an Identity Provider for Authentication 2 | 3 | Date: 2023-08-09 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | Following [ADR015: Use an Identity Provider for authentication and implement authorisation](ADR015-idp-authentication.md) we looked into alternatives to GOV.UK Signon. 12 | 13 | [NCSC guidance on Enterprise authentication policy](https://www.ncsc.gov.uk/collection/device-security-guidance/infrastructure/enterprise-authentication-policy) states: 14 | 15 | > Where possible, reduce reliance on passwords and implement passwordless authentication 16 | 17 | and there is [NCSC guidance on one time passwords](https://www.ncsc.gov.uk/guidance/authentication-methods-choosing-the-right-type#section_5). 18 | 19 | [UK Government Security Single Sign-On](https://sso.service.security.gov.uk/) was considered, but is still in an "Alpha" phase. 20 | 21 | [Auth0 offers Passwordless Authentication Methods](https://auth0.com/docs/authenticate/passwordless/authentication-methods) so was also considered, and a DPIA (Data Protection Impact Assessment) was carried out. 22 | 23 | [User research on authentication](../research/2023-08-Usability_Testing_Authentication.md) showed that participants were comfortable using a passwordless process and preferred the Auth0 journey. 24 | 25 | ## Decision 26 | 27 | We will use [Auth0 passwordless authentication with email](https://auth0.com/docs/authenticate/passwordless#email) to authenticate users who access GOV.UK Forms. 28 | 29 | (Note that this is only for users creating and managing forms. Users who fill in forms are currently unauthenticated.) 30 | 31 | ## Consequences 32 | 33 | We make use of the [Auth0 OmniAuth Strategy gem](https://github.com/auth0/omniauth-auth0). 34 | 35 | Auth0 offers limited [customisation of the login pages](https://auth0.com/docs/customize/universal-login-pages/universal-login-page-templates), which may restrict use of the [GOV.UK Design System](https://design-system.service.gov.uk/). 36 | 37 | We need to [configure Auth0 to use Amazon SES as an external SMTP email provider](https://auth0.com/docs/customize/email/smtp-email-providers/configure-amazon-ses-as-external-smtp-email-provider) (we decided to use SES as part of [ADR019: Use Amazon SES](ADR019-use-amazon-ses.md)). 38 | 39 | The Auth0 DPIA needs to be reviewed and updated when GOV.UK Forms moves into Public Beta phase and beyond. 40 | 41 | An Enterprise Subscription may be required in the future, e.g. for SLA and support, or to use advanced features. 42 | 43 | We can decide to use a different OIDC-compatible identity provider in the future, e.g. to align with other government systems. 44 | -------------------------------------------------------------------------------- /ADR/ADR023-use-uid-in-urls.md: -------------------------------------------------------------------------------- 1 | # ADR23: Use UIDs in URLs to replace form-id 2 | 3 | Date: 08/01/24 4 | 5 | ## Status 6 | Accepted 7 | 8 | ## Context 9 | 10 | See this spike for details about the required changes https://trello.com/c/BruuEN5Z/1225-spike-change-ids-in-urls-of-forms-to-not-be-the-primary-key 11 | 12 | We need to switch away from putting database ids in our URLs. Currently, form urls look something like this: 13 | `https://submit.forms.service.gov.uk/form/1234/apply-for-an-apple/5678` 14 | 15 | Where `1234` is the form-id. 16 | 17 | We instead want to change our URLs so that they look like this: 18 | 19 | `https://submit.forms.service.gov.uk/form/51f5b6f7/apply-for-an-apple/5678` 20 | 21 | where the 8 char hex code `51f5b6f7` has replaced the form-id. 22 | 23 | We also have to handle existing form URLs, and how we want to maintain them. 24 | 25 | In order to achieve this change, we'll add an `external_id` to all of our forms, which will be used to identify from the exterior of the API. For pre-existing live forms, they will be given their current `id` as their `external_id` which will maintain their current URLs as a result. 26 | 27 | For example, a new form will have it's `external_id` as `51f5b6f7` whereas an old form will use it's current `id` of `1234` as its `external_id`. 28 | 29 | ## Decision 30 | 31 | We will be using an external ID to retrieve forms from forms-api 32 | 33 | ## Consequences 34 | 35 | URLs will no longer expose our database primary key IDs, and our API will not find objects by their primary key ID. Instead, their external ID will need to be used. 36 | 37 | URLs for forms-runner and forms-admin will use the external ID, which will change their appearance. 38 | -------------------------------------------------------------------------------- /ADR/ADR025-remove-papertrail.md: -------------------------------------------------------------------------------- 1 | # ADR025: Decision Record Title (a description of the decision, not the problem) 2 | 3 | Date: 2024-02-01 4 | 5 | ## Status 6 | 7 | > Accepted 8 | 9 | ## Context 10 | 11 | Previously we added [PaperTrail](ADR013-use-paper-trail-gem-for-auditing-and-record-backups.md) with the intention to support reinstating from previous versions. We are not using it for that at all and we are not certain we're using it for the right models. Note that the previous ADR was added over a year ago. 12 | 13 | Until we have a need for versioning, we should remove it from our code base to reduce complexity and code rot. We can easily re-add Papertrail when we get to implementing versioning. 14 | 15 | ## Decision 16 | 17 | Remove Papertrail and clean up our code and database. 18 | 19 | ## Consequences 20 | We will not be able to use PaperTrail to change a form from the `live_with_draft` state to the `live` state. 21 | 22 | We will not be able to use PaperTrail for audit purposes. 23 | 24 | We will need to implement a different way of determining if a user has been upgraded from a trial account to a full account. We currently check versions of a user and display a banner to them on their next login. 25 | -------------------------------------------------------------------------------- /ADR/ADR027-scheduled-smoke-tests.md: -------------------------------------------------------------------------------- 1 | # ADR027: Scheduled Smoke Tests 2 | 3 | Date: 2024-02-22 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | We want to run scheduled smoke tests that check critical user journeys like a 12 | user completing and submitting a form. If a smoke test fails then the team 13 | should be alerted through various channels depending on the required response 14 | (e.g. Slack or Pager Duty out of hours). 15 | 16 | ## Decision 17 | 18 | 1. Use Ruby and Capybara to write the test code to maintain consistency with 19 | the end-to-end and application code already in use. 20 | 2. Use AWS CodeBuild to run the tests from an image containing the smoke test 21 | code along with Chrome and ChromeDriver; this is consistent with how the 22 | end-to-end tests are run in our pipelines during deployment. AWS Synthetic 23 | Canaries do not support Ruby at this time. 24 | 3. Schedule the running of the CodeBuild project with an AWS Event Bridge 25 | scheduled rule. 26 | 4. Use AWS CloudWatch Metric Alarm to alarm when a smoke test fails or when 27 | they stop running. The alarm will send to an appropriate SNS topic sending 28 | to either Slack or PagerDuty as required. 29 | 5. The smoke test infrastructure will exist in the same AWS account as the 30 | environment it is testing. This aligns with the strategy of self-contained 31 | accounts and environments. 32 | 33 | ## Consequences 34 | 35 | 1. Using Ruby and Capybara aligns with the existing team technology choices. 36 | 2. The tests run on infrastructure provisioned by AWS. This should improve 37 | reliability and reduce the maintenance burden over running on team 38 | maintained virtual machines. 39 | 3. Alerting remains consistent with existing solutions and can be modified to 40 | alert the appropriate channel from Slack to PagerDuty. 41 | 4. Engineers will need to access the production AWS account to begin debugging 42 | smoke test failures in production however this access would be necessary to 43 | debug the underlying cause anyway. 44 | -------------------------------------------------------------------------------- /ADR/ADR028-use-notify-for-users.md: -------------------------------------------------------------------------------- 1 | # ADR029: Use GOV.UK Notify for emails sent to users for simple notifications 2 | 3 | Date: 2024-03-28 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | 10 | ## Context 11 | 12 | This is an addendum to [ADR019](ADR019-use-amazon-ses.md) which set out the intention to use Amazon's Simple Email Service instead of GOV.UK Notify to send emails. 13 | 14 | GOV.UK Forms has continued to use GOV.UK Notify to send emails including: 15 | - submission confirmation emails to members of the public who have completed a form. 16 | - the submitted forms to the service processing them. 17 | - One Time Passcodes to verify the ownership of the submission email address when creating or editing a form. 18 | 19 | Amazon SES is currently used during the authentication process when logging into the form builder via Auth0, a third party authentication service, to send One Time Passcodes since Auth0 does not offer integration with the GOV.UK Notify API. Using Amazon SES also provides enforced TLS. 20 | 21 | GOV.UK Forms now needs to send notifications to users relating to account management (such as when they are upgraded from a trial to full user account). 22 | 23 | ## Decision 24 | 25 | GOV.UK Forms will use GOV.UK Notify where the service is appropriate and does not require the additional features that Amazon SES offers. 26 | 27 | ## Consequences 28 | 29 | - GOV.UK Forms does not need to invest in building additional monitoring, alert and administrative interfaces related to sending email which GOV.UK Notify already provide. 30 | - GOV.UK Forms will be dependent upon the support, reliability and feature roadmap of GOV.UK Notify, for example if and when they offer enforced TLS to the recipients inbox. 31 | -------------------------------------------------------------------------------- /ADR/ADR029-use-shield-advanced.md: -------------------------------------------------------------------------------- 1 | # ADR029: Use AWS Shield Advanced 2 | 3 | Date: 2024-04-15 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | The review of our Business Continuity and Disaster Recovery (BCDR) plans highlighted the need to mitigate against a malicious attack from outside our organisation. Such malicious attacks, for example a Distributed Denial of Service (DDoS) attack, would potentially degrade the service and impact end users unless measures were taken to prevent them. 12 | 13 | The team investigated[AWS Shield Advanced](https://docs.aws.amazon.com/waf/latest/developerguide/shield-chapter.html) as a possible tool to address this issue since AWS Shield Standard was already enabled on GOV.UK Forms. 14 | 15 | AWS Shield Advanced is a managed service that helps protect application against external threats, like DDoS attacks, volumetric bots, and vulnerability exploitation attempts. 16 | 17 | ## Decision 18 | 19 | The team decided to use AWS Shield Advanced and implement it on the relevant infrastructure components. 20 | 21 | ## Consequences 22 | 23 | We will enable AWS Shield Advanced on our ingress traffic-facing components (e.g., AWS CloudFront, load balancers, etc.). AWS Shield Advanced works in tandem with GOV.UK Form's existing Web Application Firewall (WAF) and web Access Control Lists (ACL) rules to better protect our services. 24 | 25 | ### Advantages 26 | 27 | Implementing AWS Shield Advanced allows GOV.UK Forms to mitigate against potential malicious attacks from outside our organisation and therefore improve our BCP/DR abilities. 28 | 29 | Moreover, GOV.UK Forms will benefit from the Shield Advanced automatic application layer mitigation as well as a dedicated Shield Response Team. This team will proactively contact GOV.UK Forms if the availability or performance of our applications are impacted by a possible attack. 30 | 31 | ### Disadvantages 32 | 33 | There are two main disadvantages: 34 | 35 | * Maintaining the new resources in our Terraform codebase 36 | * Cost (although this is expected to be minimal) 37 | -------------------------------------------------------------------------------- /ADR/ADR031-use-pagerduty.md: -------------------------------------------------------------------------------- 1 | # ADR031: Use PagerDuty 2 | 3 | Date: 2024-05-22 4 | 5 | ## Status 6 | 7 | > Accepted or Rejected 8 | > 9 | > Valid ADR statuses are: "Proposed", "Accepted", "Rejected", "Deprecated", "Superseded by ADRzzz", but since we use the GitHub Pull request mechanism to approve ADRs, "Proposed" isn't applicable. 10 | 11 | ## Context 12 | 13 | As GOV.UK Forms goes into public beta, we plan to begin out-of-hours support for the service. To do this, we need to be 14 | able to have a number of things: 15 | 16 | * a rota for who is responsible for out-of-hours support on any given day 17 | * a way to notify the support person that something requires their attention 18 | * a way to escalate to a second layer of support if the first person does not answer 19 | 20 | These are not features we want to build for ourselves, so we must find a product which meets these needs. 21 | 22 | ## Decision 23 | 24 | We have decided pay for the [PagerDuty](https://www.pagerduty.com/) service. This is the conventional approach within GDS, 25 | however that fact is not documented anywhere currently. 26 | 27 | ## Consequences 28 | We are reliant on PagerDuty being operational to alert us to failures in our own service. The beneficial trade-off we 29 | get for this is a managed rotas and phone alerts system. -------------------------------------------------------------------------------- /ADR/ADR032-use-statuspage.md: -------------------------------------------------------------------------------- 1 | # ADR032: Use StatusPage 2 | 3 | Date: 2024-05-22 4 | 5 | ## Status 6 | 7 | > Accepted or Rejected 8 | > 9 | > Valid ADR statuses are: "Proposed", "Accepted", "Rejected", "Deprecated", "Superseded by ADRzzz", but since we use the GitHub Pull request mechanism to approve ADRs, "Proposed" isn't applicable. 10 | 11 | ## Context 12 | 13 | As GOV.UK Forms goes in to public beta and beyond, we expect our user base to expand, and to be overall less directly 14 | engaged with our users. We have good means for broadcasting product news to our users, but we don't yet have a way of 15 | broadcasting information about ongoing incidents. We will need that ability, and it should be external to the service 16 | so that a service outage is not also on outage to our ability to communicate about said outage. 17 | 18 | ## Decision 19 | 20 | We have decided to pay for the [StatusPage](https://www.atlassian.com/software/statuspage) service. This is the 21 | conventional approach within GDS, however that fact is not documented anywhere currently. 22 | 23 | 24 | ## Consequences 25 | We are reliant on StatusPage being operational to alert our users to ongoing incidents. The beneficial trade-off we 26 | get for this is a managed and reliable service for reporting incidents. -------------------------------------------------------------------------------- /ADR/ADR033-swapping-jest-vitest.md: -------------------------------------------------------------------------------- 1 | # ADR032: Swapping JS Test Framework Jest for Vitest 2 | 3 | Date: 2024-06-17 4 | 5 | ## Status 6 | 7 | > Accepted 8 | 9 | ## Context 10 | 11 | Jest tests are compatible with Vitest, but rather than running in a separate pipeline this allows us to consolidate into one run. It also means we have one less moving part to maintain. 12 | 13 | This is a retroactive record of this [PR](https://github.com/alphagov/forms-admin/pull/1209). 14 | 15 | ## Decision 16 | 17 | Adopt Vitest for our JS testing framework. 18 | 19 | ## Consequences 20 | 21 | One less pipeline and addition to our Javascript build. Everything is Vite based. 22 | -------------------------------------------------------------------------------- /ADR/ADR039-add-aurora-for-runner.md: -------------------------------------------------------------------------------- 1 | # ADR039: Add another Aurora cluster to provide database to Forms Runner 2 | 3 | Date: 2025-01-27 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | To support using SolidQueue (see [ADR38](ADR038-add-psql-database-and-solid-queue-to-forms-runner.md)) and for supporting storing of user's answers before they complete a submission (Save and Return) we will need a database. However we don't want to store alongside the data for forms. One reason being is if we need to recover, that affects both the submissions data and the data on forms themselves, leading to potential loss of data on both sides. We will provision a separate Aurora cluster for a stronger partition of data. The pre-submission data is inherently transient anyway (once it's sent, we won't store it for long), whereas we cannot lose the definitions of forms, users (form creators), groups and orgs. 12 | 13 | ## Decision 14 | 15 | We will provision another Aurora cluster and store data relating to submissions there, separate to the cluster where the databases for API and Admin live. 16 | 17 | ## Consequences 18 | 19 | * We will need more infrastructure to support the Aurora cluster 20 | * We will have 2 clusters to maintain 21 | * Runner will store and read data separate to the API and Admin apps 22 | -------------------------------------------------------------------------------- /ADR/ADR042-use-amazon-s3-file-uploads.md: -------------------------------------------------------------------------------- 1 | # ADR042: Use Amazon S3 and GuardDuty Malware Protection for file upload 2 | 3 | Date: 2024-12-04 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | Sometimes users need to upload a file as part of completing a form. These files need to be stored temporarily until the form is sent to the receiving organisation. It's possible that uploaded files may contain malware, so they should be checked first before sending them on. 12 | 13 | ## Decision 14 | 15 | Store uploaded files in [Amazon S3](https://aws.amazon.com/s3/), and enable [GuardDuty Malware Protection for S3](https://docs.aws.amazon.com/guardduty/latest/ug/gdu-malware-protection-s3.html) to check for malware. 16 | 17 | ## Consequences 18 | 19 | A new S3 bucket needs to be created which `forms-runner` can access. 20 | 21 | There is a cost associated with the use of GuardDuty Malware Protection, [$0.95 per GB per month in Europe (London) Region](https://aws.amazon.com/guardduty/pricing/#GuardDuty_protection_plans) as of December 2024. 22 | 23 | Data retention for files uploaded to S3 must be considered. 24 | -------------------------------------------------------------------------------- /ADR/ADRXXX-architecture-decision-record-template.md: -------------------------------------------------------------------------------- 1 | # ADRxxx: Decision Record Title (a description of the decision, not the problem) 2 | 3 | Date: YYYY-MM-DD 4 | 5 | ## Status 6 | 7 | > Accepted or Rejected 8 | > 9 | > Valid ADR statuses are: "Proposed", "Accepted", "Rejected", "Deprecated", "Superseded by ADRzzz", but since we use the GitHub Pull request mechanism to approve ADRs, "Proposed" isn't applicable. 10 | 11 | ## Context 12 | 13 | > the facts behind the need to make the decision 14 | 15 | ## Decision 16 | 17 | > what the team has decided to do 18 | 19 | ## Consequences 20 | 21 | > both positive and negative consequences of the decision 22 | -------------------------------------------------------------------------------- /ADR/README.md: -------------------------------------------------------------------------------- 1 | We use Architecture Decision Records. 2 | 3 | You can read about the general approach on the [GDS Way page on Architecture Decisions](https://gds-way.cloudapps.digital/standards/architecture-decisions.html) and specifics about our implementation at [ADR000 - Record Architecture Decisions](https://github.com/alphagov/cifu/blob/main/ADR/ADR000-record-architecture-decisions.md). Our template ADR is [ADRXXX](https://github.com/alphagov/forms/blob/main/ADR/ADRXXX-architecture-decision-record-template.md). 4 | 5 | In general we will follow [the GDS Way](gds-way.cloudapps.digital/), so these records will cover decisions that: 6 | - are not already covered in the GDS Way 7 | - are covered in the GDS Way, but have specific implementation details which need to be captured 8 | - diverge from the guidance in the GDS Way 9 | -------------------------------------------------------------------------------- /LICENCE: -------------------------------------------------------------------------------- 1 | The MIT License (MIT) 2 | 3 | Copyright (c) 2022 Crown Copyright (Government Digital Service) 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # GOV.UK Forms 2 | 3 | We record our work and decisions in this repo. 4 | 5 | You can find: 6 | 7 | - product decisions in [decision-record/](decision-record/) 8 | - technical decisions in [ADR/](ADR) 9 | - technical diagrams in [diagrams/](diagrams/) 10 | - user research findings in [research/](research/) 11 | - documentation of our designs in [design/](design/) 12 | 13 | We also have: 14 | - [a private wiki](https://github.com/alphagov/forms-team/wiki) for team documentation (set-up, onboarding etc) 15 | - [a public wiki](https://github.com/alphagov/forms/wiki) that we don't use all that much 16 | 17 | You can find our code in the following repositories: 18 | - [forms-admin](https://github.com/alphagov/forms-admin) - our application for building forms. 19 | - [forms-api](https://github.com/alphagov/forms-api) - our application for storing and serving form definitions. 20 | - [forms-runner](https://github.com/alphagov/forms-runner) - our application for hosting forms, so that they can be filled in by members of the public. 21 | - [forms-e2e-tests](https://github.com/alphagov/forms-e2e-tests) - end-to-end tests for the service. 22 | - [forms-product-page](https://github.com/alphagov/forms-product-page) - our product pages, as seen at [https://forms.service.gov.uk](https://forms.service.gov.uk) 23 | - [forms-prototypes](https://github.com/alphagov/forms-prototypes) - our prototypes, used for user research and design exploration. 24 | - [govuk-forms-markdown](https://github.com/alphagov/govuk-forms-markdown) - our gem for rendering the limited subset of markdown we support. 25 | 26 | ## License 27 | 28 | Unless stated otherwise, the codebase is released under [the MIT License](LICENCE). This covers both the codebase and any sample code in the documentation. 29 | 30 | The documentation is [© Crown copyright](https://www.nationalarchives.gov.uk/information-management/re-using-public-sector-information/uk-government-licensing-framework/crown-copyright/) and available under the terms of the [Open Government 3.0 licence](https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/). 31 | -------------------------------------------------------------------------------- /decision-record/DR000-use-github-and-the-adr-process.md: -------------------------------------------------------------------------------- 1 | # DR000: Recording our project decisions on GitHub Files using the ADR Process 2 | 3 | Date: 2022-02-10 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | Various decision have been made during the Discovery and Alpha phases by the GOV.UK Forms team, but until now they have not been recorded consistently or centrally. 12 | 13 | ## Decision 14 | 15 | Use the Architecture Decision Records approach to record all significant decisions that are made, using GitHub files on the public repository, with a decision record template. 16 | 17 | ## Consequences 18 | 19 | Everyone on the team needs to have access to and be familiar with using GitHub Files so that they can record decisions. 20 | Consistent and accurate records of decisions will ensure that the team members and others interested in our work have a clear grasp of core decisions and aims of the GOV.UK Forms project. 21 | -------------------------------------------------------------------------------- /decision-record/DR002-no-charges-for-lower-volume-services.md: -------------------------------------------------------------------------------- 1 | # DR002: We won't charge lower volume services to use our platform. 2 | 3 | Date: 2021-08-20 4 | 5 | ## Status 6 | 7 | Superseded by DR008 8 | 9 | ## Context 10 | 11 | Related to [Epic 1](https://docs.google.com/document/d/1y5iSEumAuLBaKtgvyhNaGagboN7XziAnQMfuwdVpiZM/edit#) and our [second and fifth riskiest assumptions](https://docs.google.com/spreadsheets/d/1gUZeEXSU8uhPcNJxQWGZ4oxOzANx0-EolDnVqZ0qsMg/edit?pli=1#gid=0) (ID16, ID30), we wanted to know if we can make adoption of forms cost-effective during private beta and beyond. 12 | We tested different price points with decision-makers and different business models with our sponsors during spending review. 13 | 14 | ## Decision 15 | 16 | We will not charge government services with fewer than 10,000 form transactions per year to use our platform. If higher volume services choose to use our platform once we open in public beta, or if a form's transactions are higher than first forecast, we could decide to charge for forms with 10,000 transactions and above. 17 | 18 | ## Consequences 19 | 20 | Positive - most form creators will be able to use GOV.UK Forms at no cost. 21 | 22 | This decision relates to [Plan form production](https://app.mural.co/t/gaap0347/m/gaap0347/1640103843400/cce4d74dc3ea2dd8916b8921a435b115a1c9e488?sender=u95c067cf6f303eaa90553018) part of our service. 23 | -------------------------------------------------------------------------------- /decision-record/DR005-choosing-insolvency-service-as-first-partner.MD: -------------------------------------------------------------------------------- 1 | # DR005: Choosing The Insolvency Service as our first private beta partner 2 | 3 | Date: 2022-03-30 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | We are fortunate to have lots of organisations that have said they’d like to partner with us for our private beta. We were considering which comparatively simple forms we could start with so we can start testing the GOV.UK Forms platform as soon as possible. The Insolvency Service were keen to improve their ["Amend my redundancy payment claim"](https://www.gov.uk/government/publications/amend-your-redundancy-claim) set of forms, some of which were quite simple. 12 | 13 | ## Decision 14 | 15 | We chose The Insolvency Service as our first private beta partner, and think specifically that the "Amend my personal details on my redundancy claim" form would be the simplest form for them to tackle first. 16 | 17 | ## Consequences 18 | 19 | We prioritised starting our private beta phase by designing, building and testing user stories with The Insolvency Service that should allow them to tackle the “Amend my personal details on my redundancy claim” form. We’re telling other organisations that we’ll be in touch soon to kick off subsequent partnerships. 20 | -------------------------------------------------------------------------------- /decision-record/DR006-epics-focus-on-specific-forms.MD: -------------------------------------------------------------------------------- 1 | # DR006: Initially using epics to focus on specific forms 2 | 3 | Date: 2022-04-14 4 | 5 | ## Status 6 | 7 | Accepted 8 | 9 | ## Context 10 | 11 | It took a lot of work during alpha to develop and iterate epics that were useful for the team. While they were quite useful during alpha, we probably want to avoid using riskiest assumptions as our private beta epics, as we have a much clearer idea of what platform and service we’re building. 12 | 13 | To make our private beta epics useful, it’s important to acknowledge that we’re not only writing our epics, but also making a choice about what kind of epics we want to use. 14 | 15 | We discussed three different types of epics we could use during private beta: 16 | 17 | 1. An epic is a phase of our proposed user journey 18 | 2. An epic is a group of complementary user stories that together should allow us to test a specific form with a partner 19 | 3. An epic is a themed group of user stories that when successfully delivered, offer a new, improved or ongoing capability 20 | 21 | We discussed these [options in more detail](https://docs.google.com/document/d/15FLVHdveuzXmQ-EgJMBsnijGZ5hDn3IiLWV7SSwP7Qw/edit#heading=h.2jg7znofkzxp). 22 | 23 | ## Decision 24 | 25 | We decided to start with epic type 2, "An epic is a group of complementary user stories that together should allow us to test a specific form with a partner". 26 | 27 | We also recognised that after the first few forms have been created or published during private beta, we are likely to want to bring in epics that fit with epic type 1. So we should review this decision at this later point. 28 | 29 | ## Consequences 30 | 31 | Our first epic is called, "Amend my personal details on my redundancy claim". Once we’ve agreed which other specific document-based forms we’ll use with our partners to test GOV.UK Forms, we’ll create more epics with the necessary user stories we need to design, build and test. 32 | -------------------------------------------------------------------------------- /decision-record/DR009-who-can-access-authentication.md: -------------------------------------------------------------------------------- 1 | # DR009: Deciding who can access GOV.UK Forms 2 | 3 | Date: 2023-06-27 4 | 5 | ## Status 6 | 7 | Proposed 8 | 9 | ## Context 10 | 11 | While looking at replacing Signon with either CDDO's SSO, or Auth0, it was raised that restricting users to gov.uk email accounts only would still allow non-central government organisations, such as local councils, access to create an account. 12 | 13 | We are currently restricting GOV.UK Forms to central government departments, so this was discussed as a risk of inadvertently expanding our scope. 14 | 15 | ## Decision 16 | 17 | It was decided that this was not an issue - users from local government will only be able to make an account with trial permission. Anything further would require a Super Admin (ie. the GOV.UK Forms team) to set up an organisation for them, and set up admins for that org. Therefore, we still have control over access to just central government for now. 18 | 19 | ## Consequences 20 | 21 | It means when we do eventually expand to allow other public sector organisations like local councils, we don't need to do too much extra work to allow this. However, we need to manage expectations before users sign up, so they're aware who will have access, or what access they'll have if they're not from a central government department. 22 | -------------------------------------------------------------------------------- /decision-record/DRXXX-decision-record-template.md: -------------------------------------------------------------------------------- 1 | # DRxxx: Decision Record Title (a description of the decision, not the problem) 2 | 3 | Date: YYYY-MM-DD 4 | 5 | ## Status 6 | 7 | > Proposed, Accepted, Rejected, Deprecated, Superseded by DRzzz 8 | 9 | ## Context 10 | 11 | > the facts behind the need to make the decision 12 | 13 | ## Decision 14 | 15 | > what the team has decided to do 16 | 17 | ## Consequences 18 | 19 | > both positive and negative consequences of the decision 20 | -------------------------------------------------------------------------------- /decision-record/README.md: -------------------------------------------------------------------------------- 1 | # Decision Records 2 | 3 | As recorded in [DR000-use-github-and-the-adr-process.md](DR000-use-github-and-the-adr-process.md) we are using the [ADR process](../ADR/) to record significant decisions for GOV.UK Forms in addition to architectural ones. 4 | 5 | Proposing and reviewing decisions requires an understanding of the GitHub and [pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests). 6 | 7 | ## Proposing a new decision 8 | 9 | 1. Add a new file with the naming convention `DRXXX-short-decision-description.md` where `XXX` is the highest existing DR number + 1 10 | 2. Use the [decision record Markdown template](DRXXX-decision-record-template.md) for the structure, "Raw" allows you to view the Markdown 11 | 3. Set the Status to "Proposed" 12 | 4. Set the branch name to match the new filename 13 | 5. Propose the new file and start the pull request process 14 | 15 | ## Reviewing a decision 16 | 17 | 1. Find the decision record in the list of [pull requests](https://github.com/alphagov/forms/pulls) 18 | 2. Add a comment and / or approve the pull request 19 | 20 | ## Approving / superseding / rejecting a decision 21 | 22 | 1. Set the Status to either 23 | - "Approved" (and where appropriate set the status of any superceded decision to "Superseded by DRXXX"), or 24 | - "Rejected" 25 | 3. Merge the pull request 26 | -------------------------------------------------------------------------------- /design/README.md: -------------------------------------------------------------------------------- 1 | # Design documentation 2 | 3 | We use this part of the GOV.UK Forms repo to record design work and decisions we’ve made. 4 | 5 | You can explore our initial versions of GOV.UK Forms, the prototypes we tested, and new features as they’ve been iterated and adapted based on user research, data and new design patterns. 6 | 7 | ## Prototype version history 8 | 9 | At the start of alpha we explored the wider product, focusing on quick iterations across whole journeys. This helped us get a clearer picture of our minimum viable product (MVP) so we could baseline where we wanted to start work from. 10 | 11 | * [Prototype version 1](prototype-version-1) 12 | * [Prototype version 2](prototype-version-2) 13 | * [Prototype version 3](prototype-version-3) 14 | * [Prototype version 4](prototype-version-4) 15 | * [Prototype version 5](prototype-version-5) 16 | * [Prototype version 6](prototype-version-6) 17 | 18 | ## Features 19 | 20 | Once we had a baseline that worked for form creators we shifted focus onto key features. The aim was to help align GOV.UK Forms with the key functionality that would help form creators make more of their forms with our product. We used the team’s analysis of feature coverage of forms across GOV.UK to help us priorititse this work. 21 | 22 | You can explore the [features](features) as we’ve designed them and see how they’ve been iterated based on user research and feedback through private beta and ‘early access’. ('Early access' is the period in which we’re encouraging people to try out GOV.UK Forms to see if it’s suitable for them). 23 | -------------------------------------------------------------------------------- /design/features/README.md: -------------------------------------------------------------------------------- 1 | # Features 2 | 3 | We use this area to record design work and decisions made, and any iterations made to improve usability for form creators and form fillers. 4 | 5 | ## Explore the features we’ve designed 6 | 7 | ### [Confirm that a form’s been submitted (form fillers)](confirmation-email-for-form-fillers) 8 | This feature introduces new functionality to the form filler’s journey, allowing them to request an email confirming that they’ve successfully submitted a form. 9 | 10 | ### [Add guidance to help people answer the question (‘detailed guidance’)](detailed-guidance) 11 | This feature introduces new functionality to the form building tool, allowing form creators to add more complex help text to a question page. This ‘guidance’ text will appear above the question, on the same page. 12 | 13 | ### [Early access journey](early-access) 14 | This journey is designed to allow people to create a trial account and request an upgrade to an editor account - so they can make live forms to be published on GOV.UK. 15 | 16 | ### [Editing pages when looking at a preview of a form](editing-drafts) 17 | This feature introduces functionality in the form building tool to help form creators return to edit their questions more quickly when previewing the form as if they’re someone who’s filling it in. It introduces a clearer, simpler route for form creators to navigate between previewing and editing their form. 18 | 19 | ### [Metrics for form creators](form-metrics) 20 | This feature introduces new functionality to the form building tool to allow form creators to see how their form is performing. We’ll be starting with a minimum offering of: number of forms started, number of forms submitted, and completion rate. 21 | 22 | ### [Live and draft](live-draft) 23 | This feature introduces the ability to make a draft of a live form so that you can prepare changes to it. You can then make all the changes live at the same time, when appropriate. 24 | 25 | ### [Previewing a question](previewing-a-question) 26 | This feature introduces a clear and quick way to help form creators understand what an answer type will look like and how it’ll be formatted alongside other content they’ve added - including hint text and additional guidance. 27 | 28 | ### [Routing, branching and exit pages](routing) 29 | Functionality to allow form creators to skip someone to a later question, or an exit page, based on an answer to a radio question. 30 | 31 | ### [User management journey](user-management) 32 | This journey enables other departments having more control over who creates and publishes forms. 33 | -------------------------------------------------------------------------------- /design/features/confirmation-email-for-form-fillers/screenshots-v2/README.md: -------------------------------------------------------------------------------- 1 | This folder is for screenshots for v2 of the 'confirmation email for form fillers' feature 2 | -------------------------------------------------------------------------------- /design/features/confirmation-email-for-form-fillers/screenshots-v2/confirmation-email-mural-mockup-notify-template.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/confirmation-email-for-form-fillers/screenshots-v2/confirmation-email-mural-mockup-notify-template.png -------------------------------------------------------------------------------- /design/features/confirmation-email-for-form-fillers/screenshots-v2/provide-contact-details-for-support-page-updated-content.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/confirmation-email-for-form-fillers/screenshots-v2/provide-contact-details-for-support-page-updated-content.png -------------------------------------------------------------------------------- /design/features/confirmation-email-for-form-fillers/screenshots-v2/what-happens-next-page-new-page-title-and-updated-content.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/confirmation-email-for-form-fillers/screenshots-v2/what-happens-next-page-new-page-title-and-updated-content.png -------------------------------------------------------------------------------- /design/features/detailed-guidance/screenshots-v2.md: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /design/features/detailed-guidance/screenshots-v2/README.md: -------------------------------------------------------------------------------- 1 | This folder is for screenshots for detailed guidance v2 2 | -------------------------------------------------------------------------------- /design/features/detailed-guidance/screenshots-v2/add-guidance-help-text.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/detailed-guidance/screenshots-v2/add-guidance-help-text.png -------------------------------------------------------------------------------- /design/features/detailed-guidance/screenshots-v2/give-your-page-a-heading-on-add-guidance-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/detailed-guidance/screenshots-v2/give-your-page-a-heading-on-add-guidance-page.png -------------------------------------------------------------------------------- /design/features/detailed-guidance/screenshots-v2/hint-text-guidance-text-on-edit-question-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/detailed-guidance/screenshots-v2/hint-text-guidance-text-on-edit-question-page.png -------------------------------------------------------------------------------- /design/features/detailed-guidance/screenshots-v2/updated-formatting-markdown-help-text.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/detailed-guidance/screenshots-v2/updated-formatting-markdown-help-text.png -------------------------------------------------------------------------------- /design/features/early-access/screenshots-v1/001.Editor-notification-banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/early-access/screenshots-v1/001.Editor-notification-banner.png -------------------------------------------------------------------------------- /design/features/early-access/screenshots-v1/002.Get-started.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/early-access/screenshots-v1/002.Get-started.png -------------------------------------------------------------------------------- /design/features/early-access/screenshots-v1/003.Mou.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/early-access/screenshots-v1/003.Mou.png -------------------------------------------------------------------------------- /design/features/early-access/screenshots-v1/004.Requirements-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/early-access/screenshots-v1/004.Requirements-page.png -------------------------------------------------------------------------------- /design/features/early-access/screenshots-v1/005.What-happens-next.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/early-access/screenshots-v1/005.What-happens-next.png -------------------------------------------------------------------------------- /design/features/early-access/screenshots-v1/006.Agreeing-to-mou.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/early-access/screenshots-v1/006.Agreeing-to-mou.png -------------------------------------------------------------------------------- /design/features/early-access/screenshots-v1/007.Trial-notification-banner.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/early-access/screenshots-v1/007.Trial-notification-banner.png -------------------------------------------------------------------------------- /design/features/early-access/screenshots-v1/forms-product-site-homepage-call-to-action.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/early-access/screenshots-v1/forms-product-site-homepage-call-to-action.png -------------------------------------------------------------------------------- /design/features/early-access/screenshots-v1/screenshots: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /design/features/editing-drafts/README.md: -------------------------------------------------------------------------------- 1 | # Editing pages when looking at a preview of a form 2 | 3 | ## Status 4 | 5 | Date created: *2023-06-01* 6 | 7 | Epic trello card: No epic card at this time 8 | Feature trello cards: 9 | 10 | - https://trello.com/c/K3X2uDWp/545-spike-explore-options-for-editing-pages-when-looking-at-a-preview-of-a-form-in-a-separate-tab 11 | 12 | Mural working board: https://app.mural.co/invitation/mural/gaap0347/1679397321141?sender=ue1ef9fc3c2ad3697c3c93132&key=7b4b09f5-cd65-49a1-9758-02b732afa098 13 | 14 | ___ 15 | 16 | ## Contents 17 | 18 | - [Editing pages when looking at a preview of a form](#editing-pages-when-looking-at-a-preview-of-a-form) 19 | - [Status](#status) 20 | - [Contents](#contents) 21 | - [What](#what) 22 | - [Why](#why) 23 | - [Hypothesis](#hypothesis) 24 | 25 | ___ 26 | 27 |
28 | 29 | ## What 30 | 31 | This feature introduces functionality in the form building tool to help form creators return to edit their questions more quickly when previewing the form as if they’re someone who’s filling it in. It introduces a clearer, simpler route for form creators to navigate between previewing and editing their form. 32 | 33 |
34 | 35 | ## Why 36 | 37 | When users were testing their forms in preview they wanted to step through the pages and view them as an end user (form filler) would. As they travelled through their form, they spotted mistakes within certain pages and wanted to quickly get back to the edit screen for that particular page in order to change it. 38 | 39 | This is currently causing issues as some users with lower digital confidence are not realising that they're in a new window/tab. They're therefore trying to click the back button to return to the edit screen but finding that this is not possible. 40 | 41 | Once they do manage to get back to the form overview page they've often forgotten which page they saw the error on. 42 | 43 | ## Hypothesis 44 | 45 | We believe that by offering form creators an "Edit this page" option somewhere within the test/preview journey they'll be able to fix mistakes more quickly and easily. 46 | 47 |
48 | 49 | ___ 50 | 51 |
52 | 53 | [Back to the top](#editing-pages-when-looking-at-a-preview-of-a-form) 54 | -------------------------------------------------------------------------------- /design/features/form-metrics/README.md: -------------------------------------------------------------------------------- 1 | # Metrics for form creators 2 | 3 | ## Status 4 | 5 | Date created: *2023-10-18* 6 | 7 | Epic trello card: https://trello.com/c/WNHj1sUd/999-epic-metrics-for-form-creators 8 | Mural working board: https://app.mural.co/t/gaap0347/m/gaap0347/1691482625906/2bb9a15696904b5dedd99f77611c83986d993e89?sender=ue1ef9fc3c2ad3697c3c93132 9 | ___ 10 | 11 | ## Contents 12 | 13 | - [Metrics for form creators](#metrics-for-form-creators) 14 | - [Status](#status) 15 | - [Contents](#contents) 16 | - [What](#what) 17 | - [Why](#why) 18 | - [Hypothesis](#hypothesis) 19 | 20 | ___ 21 | 22 |
23 | 24 | ## What 25 | 26 | This feature introduces new functionality to the form building tool to allow form creators to see how their form is performing. We’ll be starting with a minimum offering of: number of forms started, number of forms submitted, and completion rate. 27 | 28 | This information should cover at least a week of data collected. We’ll look to improve this offering over time and will investigate introducing filters to help form creators adapt data for their needs. 29 | 30 | ### User stories 31 | 32 | **As a form creator**, I need to see how well my form is doing, so that I can make improvements to it and/or create reports. 33 | 34 |
35 | 36 | ## Why 37 | 38 | Currently form creators, or a designated contact within the department or team, receive a spreadsheet created manually by our performance analyst. This spreadsheet shows basic metrics such as weekly submissions, completion rate and page dropouts. This information has helped form creators make improvements to their forms shortly after launching, meaning they’re able to reduce dropouts on problem pages and get better data overall. 39 | 40 | ## Hypothesis 41 | 42 | We believe that by offering form creators a self-serve view of basic metrics they’ll be able to improve their forms without needing our performance analyst to provide manual reports. 43 | 44 | We believe that by doing this before we get into early access (and private beta later on) we’ll hopefully reduce the impact on the team of new GOV.UK Forms adoptions. 45 | 46 |
47 | 48 | ___ 49 | 50 |
51 | 52 | [Back to the top](#metrics-for-form-creators) 53 | -------------------------------------------------------------------------------- /design/features/live-draft/screenshots-v1/001.Create-a-form-tasklist.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/live-draft/screenshots-v1/001.Create-a-form-tasklist.png -------------------------------------------------------------------------------- /design/features/live-draft/screenshots-v1/002.Add-and-edit-questions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/live-draft/screenshots-v1/002.Add-and-edit-questions.png -------------------------------------------------------------------------------- /design/features/live-draft/screenshots-v1/003.Live-form-view-only.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/live-draft/screenshots-v1/003.Live-form-view-only.png -------------------------------------------------------------------------------- /design/features/live-draft/screenshots-v1/004.Your-questions-view-only.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/live-draft/screenshots-v1/004.Your-questions-view-only.png -------------------------------------------------------------------------------- /design/features/live-draft/screenshots-v1/005.Landing-page-forms-list.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/live-draft/screenshots-v1/005.Landing-page-forms-list.png -------------------------------------------------------------------------------- /design/features/live-draft/screenshots-v1/006.Edit-form-in-draft-tasklist-in-progress.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/live-draft/screenshots-v1/006.Edit-form-in-draft-tasklist-in-progress.png -------------------------------------------------------------------------------- /design/features/live-draft/screenshots-v1/007.Edit-form-in-draft-tasklist-completed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/live-draft/screenshots-v1/007.Edit-form-in-draft-tasklist-completed.png -------------------------------------------------------------------------------- /design/features/live-draft/screenshots-v1/008.Preview-draft-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/live-draft/screenshots-v1/008.Preview-draft-form.png -------------------------------------------------------------------------------- /design/features/live-draft/screenshots-v1/009.Make-changes-live.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/live-draft/screenshots-v1/009.Make-changes-live.png -------------------------------------------------------------------------------- /design/features/live-draft/screenshots-v1/010.Changes-are-live-confirmation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/live-draft/screenshots-v1/010.Changes-are-live-confirmation.png -------------------------------------------------------------------------------- /design/features/live-draft/screenshots-v1/011.Preview-live-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/live-draft/screenshots-v1/011.Preview-live-form.png -------------------------------------------------------------------------------- /design/features/live-draft/screenshots-v1/012.Live-form-form-filler-view.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/live-draft/screenshots-v1/012.Live-form-form-filler-view.png -------------------------------------------------------------------------------- /design/features/long-list-autocomplete/diagrams.md: -------------------------------------------------------------------------------- 1 | ## Create a question with a select from list answers 2 | 3 | ```mermaid 4 | 5 | flowchart LR 6 | A["Start"] --> B["Add a question"] 7 | B --> C["What kind of answer do you need to this question?"] 8 | C -- Selection from a list of options --> D@{ label: "What's your question" } 9 | F{"How many options should people be able to select?"} -- One or more options --> G["Create a list of options
1000 limit"] 10 | F -- One option only --> H["Create a list of options
30 limit"] 11 | G -.-o I@{ label: "Enter your list's options into a textbox" } 12 | G --> n3["Edit question"] 13 | D --> F 14 | H --> n3 15 | H -.-o n4@{ label: "Enter your list's options into a textbox" } 16 | n3 --> n5["Save question"] 17 | n5 --> n6["End"] 18 | n4 --> n3 19 | I --> n3 20 | 21 | ``` -------------------------------------------------------------------------------- /design/features/long-list-autocomplete/screenshots-v1/000-what-kind-of-answer-do-you-need.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/long-list-autocomplete/screenshots-v1/000-what-kind-of-answer-do-you-need.png -------------------------------------------------------------------------------- /design/features/long-list-autocomplete/screenshots-v1/001-what-is-your-question.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/long-list-autocomplete/screenshots-v1/001-what-is-your-question.png -------------------------------------------------------------------------------- /design/features/long-list-autocomplete/screenshots-v1/002-how-many-options-can-people-select.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/long-list-autocomplete/screenshots-v1/002-how-many-options-can-people-select.png -------------------------------------------------------------------------------- /design/features/long-list-autocomplete/screenshots-v1/003-create-a-list-of-options-select-one-only-single-fields.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/long-list-autocomplete/screenshots-v1/003-create-a-list-of-options-select-one-only-single-fields.png -------------------------------------------------------------------------------- /design/features/long-list-autocomplete/screenshots-v1/004-create-a-list-of-options-select-many-single-fields.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/long-list-autocomplete/screenshots-v1/004-create-a-list-of-options-select-many-single-fields.png -------------------------------------------------------------------------------- /design/features/long-list-autocomplete/screenshots-v1/005-create-a-list-of-options-select-many-single-fields.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/long-list-autocomplete/screenshots-v1/005-create-a-list-of-options-select-many-single-fields.png -------------------------------------------------------------------------------- /design/features/long-list-autocomplete/screenshots-v1/006-create-a-list-of-options-select-one-only-text-box.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/long-list-autocomplete/screenshots-v1/006-create-a-list-of-options-select-one-only-text-box.png -------------------------------------------------------------------------------- /design/features/long-list-autocomplete/screenshots-v1/007-change-seletion-type-warnings.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/long-list-autocomplete/screenshots-v1/007-change-seletion-type-warnings.png -------------------------------------------------------------------------------- /design/features/long-list-autocomplete/screenshots-v1/008-change-selection-type-reduce-options-list-edit-options.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/long-list-autocomplete/screenshots-v1/008-change-selection-type-reduce-options-list-edit-options.png -------------------------------------------------------------------------------- /design/features/long-list-autocomplete/screenshots-v1/009-change-selection-type-reduce-option-list-on-edit-question.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/long-list-autocomplete/screenshots-v1/009-change-selection-type-reduce-option-list-on-edit-question.png -------------------------------------------------------------------------------- /design/features/long-list-autocomplete/screenshots-v1/010-edit-question-options-list.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/long-list-autocomplete/screenshots-v1/010-edit-question-options-list.png -------------------------------------------------------------------------------- /design/features/long-list-autocomplete/screenshots-v1/README.md: -------------------------------------------------------------------------------- 1 | This folder is for screenshots for creating long lists of options v1 -------------------------------------------------------------------------------- /design/features/payment-links/screenshots-v1/001-create-a-form-optional-task.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/payment-links/screenshots-v1/001-create-a-form-optional-task.png -------------------------------------------------------------------------------- /design/features/payment-links/screenshots-v1/002-add-a-link-to-a-payment-page-on-govuk-pay-error-summary.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/payment-links/screenshots-v1/002-add-a-link-to-a-payment-page-on-govuk-pay-error-summary.png -------------------------------------------------------------------------------- /design/features/payment-links/screenshots-v1/002-add-a-link-to-a-payment-page-on-govuk-pay-error.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/payment-links/screenshots-v1/002-add-a-link-to-a-payment-page-on-govuk-pay-error.png -------------------------------------------------------------------------------- /design/features/payment-links/screenshots-v1/002-add-a-link-to-a-payment-page-on-govuk-pay.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/payment-links/screenshots-v1/002-add-a-link-to-a-payment-page-on-govuk-pay.png -------------------------------------------------------------------------------- /design/features/payment-links/screenshots-v1/003-create-a-form-added-payment-link.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/payment-links/screenshots-v1/003-create-a-form-added-payment-link.png -------------------------------------------------------------------------------- /design/features/payment-links/screenshots-v1/003-success-notification.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/payment-links/screenshots-v1/003-success-notification.png -------------------------------------------------------------------------------- /design/features/payment-links/screenshots-v1/004-create-a-form-return.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/payment-links/screenshots-v1/004-create-a-form-return.png -------------------------------------------------------------------------------- /design/features/payment-links/screenshots-v1/1000-preview-confirmation-still-need-to-pay.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/payment-links/screenshots-v1/1000-preview-confirmation-still-need-to-pay.png -------------------------------------------------------------------------------- /design/features/payment-links/screenshots-v1/1001-preview-journey.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/payment-links/screenshots-v1/1001-preview-journey.png -------------------------------------------------------------------------------- /design/features/payment-links/screenshots-v1/1002-preview-test-email-with-payment-link.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/payment-links/screenshots-v1/1002-preview-test-email-with-payment-link.png -------------------------------------------------------------------------------- /design/features/payment-links/screenshots-v1/README.md: -------------------------------------------------------------------------------- 1 | This folder is for screenshots for payment link work undertaken for version 1 (MVP) as part of GOV.UK Forms private beta phase. 2 | -------------------------------------------------------------------------------- /design/features/previewing-a-question/screenshots-v1/001-Helping users preview their form Mural design.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/previewing-a-question/screenshots-v1/001-Helping users preview their form Mural design.png -------------------------------------------------------------------------------- /design/features/previewing-a-question/screenshots-v1/002-check-your-question-simple-answer-type.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/previewing-a-question/screenshots-v1/002-check-your-question-simple-answer-type.png -------------------------------------------------------------------------------- /design/features/previewing-a-question/screenshots-v1/002-preview-question-simple-answer-type.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/previewing-a-question/screenshots-v1/002-preview-question-simple-answer-type.png -------------------------------------------------------------------------------- /design/features/previewing-a-question/screenshots-v1/003-check-your-question-complex-answer-type.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/previewing-a-question/screenshots-v1/003-check-your-question-complex-answer-type.png -------------------------------------------------------------------------------- /design/features/previewing-a-question/screenshots-v1/003-preview-question-complex-answer-type.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/previewing-a-question/screenshots-v1/003-preview-question-complex-answer-type.png -------------------------------------------------------------------------------- /design/features/previewing-a-question/screenshots-v1/README.md: -------------------------------------------------------------------------------- 1 | This folder is for screenshots for previewing a question v1 2 | -------------------------------------------------------------------------------- /design/features/routing/screenshots-v3/001-create-a-form-question-route-created.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v3/001-create-a-form-question-route-created.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v3/001-create-a-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v3/001-create-a-form.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v3/002-add-route-from-question.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v3/002-add-route-from-question.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v3/003-edit-route-1-is-answered-as.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v3/003-edit-route-1-is-answered-as.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v3/003-edit-route-1-take-the-person-to.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v3/003-edit-route-1-take-the-person-to.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v3/003-edit-route-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v3/003-edit-route-1.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v3/004-edit-exit-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v3/004-edit-exit-page.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v3/005-edit-question-2s-route-branch.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v3/005-edit-question-2s-route-branch.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v3/005-edit-question2s-route.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v3/005-edit-question2s-route.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v3/006-set-questions-to-skip-after-question.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v3/006-set-questions-to-skip-after-question.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v3/006-set-questions-to-skip-take-the-person-to.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v3/006-set-questions-to-skip-take-the-person-to.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v3/006-set-questions-to-skip.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v3/006-set-questions-to-skip.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v3/README.md: -------------------------------------------------------------------------------- 1 | This folder contains screenshots from our [User research Oct 24 (Mural board)](https://app.mural.co/t/gaap0347/m/gaap0347/1729773162641/fbe698a2b44f833842196c252bb254abbb806042). These screens were tested with 4 users. 2 | -------------------------------------------------------------------------------- /design/features/routing/screenshots-v4/README.md: -------------------------------------------------------------------------------- 1 | This folder contains screenshots from our [Branching designs Mural board](https://app.mural.co/t/gaap0347/m/gaap0347/1728478914347/6a7e0b709f50f00f81cab37414fdf44ec8601a70). These screens are documented in [Branching and exit pages iteration 2](design/features/routing/version-4-branching-iteration-2.md). 2 | -------------------------------------------------------------------------------- /design/features/routing/screenshots-v4/add-a-route-from-a-question.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v4/add-a-route-from-a-question.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v4/add-and-edit-your-questions-page-with-routes.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v4/add-and-edit-your-questions-page-with-routes.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v4/question-xs-routes-with-1-route.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v4/question-xs-routes-with-1-route.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v4/questions-xs-routes-with-2-routes.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v4/questions-xs-routes-with-2-routes.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v4/set-questions-to-skip-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v4/set-questions-to-skip-page.png -------------------------------------------------------------------------------- /design/features/routing/screenshots-v4/your-questions-page-for-a-live-form-with-routes.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/routing/screenshots-v4/your-questions-page-for-a-live-form-with-routes.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/editor-screenshots/001-selectorganisation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/editor-screenshots/001-selectorganisation.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/editor-screenshots/002-enteryourfullname.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/editor-screenshots/002-enteryourfullname.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/editor-screenshots/003-yourgroup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/editor-screenshots/003-yourgroup.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/editor-screenshots/003-yourgroupswithrequests.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/editor-screenshots/003-yourgroupswithrequests.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/editor-screenshots/004-createanewgroup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/editor-screenshots/004-createanewgroup.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/editor-screenshots/005-membersofthisgroup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/editor-screenshots/005-membersofthisgroup.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/editor-screenshots/006-grouppageforatrialgroup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/editor-screenshots/006-grouppageforatrialgroup.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/editor-screenshots/007-tasklistpage-livegroup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/editor-screenshots/007-tasklistpage-livegroup.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/editor-screenshots/007-tasklistpage-trial.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/editor-screenshots/007-tasklistpage-trial.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/editor-screenshots/readme.md: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/001-selectorganisation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/group-admin-screenshots/001-selectorganisation.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/002-enteryourfullname.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/group-admin-screenshots/002-enteryourfullname.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/003-yourgroup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/group-admin-screenshots/003-yourgroup.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/003-yourgroupswithrequests.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/group-admin-screenshots/003-yourgroupswithrequests.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/004-createanewgroup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/group-admin-screenshots/004-createanewgroup.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/005-grouplandingpagefortrialgroup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/group-admin-screenshots/005-grouplandingpagefortrialgroup.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/005-grouplandingpagefortrialgroup2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/group-admin-screenshots/005-grouplandingpagefortrialgroup2.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/006-membersofthisgroup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/group-admin-screenshots/006-membersofthisgroup.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/007-Upgraderequest.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/group-admin-screenshots/007-Upgraderequest.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/007-upgraderequest1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/group-admin-screenshots/007-upgraderequest1.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/008-activegroup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/group-admin-screenshots/008-activegroup.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/009-addaneditororgroupadmin.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/group-admin-screenshots/009-addaneditororgroupadmin.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/010-tasklistpage-active.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/group-admin-screenshots/010-tasklistpage-active.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/010-tasklistpage-trial.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/group-admin-screenshots/010-tasklistpage-trial.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/group-admin-screenshots/readme.md: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/organisation-admin-screenshots/001.Selectorganisation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/organisation-admin-screenshots/001.Selectorganisation.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/organisation-admin-screenshots/002-Entername.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/organisation-admin-screenshots/002-Entername.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/organisation-admin-screenshots/003-Grouplandingpage.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/organisation-admin-screenshots/003-Grouplandingpage.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/organisation-admin-screenshots/004-Grouplandingpage.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/organisation-admin-screenshots/004-Grouplandingpage.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/organisation-admin-screenshots/005-Membersofthisgroup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/organisation-admin-screenshots/005-Membersofthisgroup.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/organisation-admin-screenshots/007-Upgradethisgroup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/organisation-admin-screenshots/007-Upgradethisgroup.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/organisation-admin-screenshots/007-Upgradethisgroup2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/organisation-admin-screenshots/007-Upgradethisgroup2.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/organisation-admin-screenshots/008-Activegroup.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/organisation-admin-screenshots/008-Activegroup.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/organisation-admin-screenshots/009-Addmembers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/organisation-admin-screenshots/009-Addmembers.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/organisation-admin-screenshots/010-tasklistpage-active.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/organisation-admin-screenshots/010-tasklistpage-active.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/organisation-admin-screenshots/010-tasklistpage-trial.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/features/user-management/screenshots-v1/organisation-admin-screenshots/010-tasklistpage-trial.png -------------------------------------------------------------------------------- /design/features/user-management/screenshots-v1/organisation-admin-screenshots/readme.md: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/001-Form-Home.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/001-Form-Home.png -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/002-Create-a-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/002-Create-a-form.png -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/003-Form-Apply-for-a-juggling-licence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/003-Form-Apply-for-a-juggling-licence.png -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/004-Edit-summary-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/004-Edit-summary-page.png -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/005-Edit-confirmation-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/005-Edit-confirmation-page.png -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/006-Edit-question-1-hint-open.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/006-Edit-question-1-hint-open.png -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/006-Edit-question-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/006-Edit-question-1.png -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/007-Edit-question-2.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/007-Edit-question-2.png -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/008-Form-Apply-for-a-juggling-licence-added-questions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/008-Form-Apply-for-a-juggling-licence-added-questions.png -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/009-Publish-form-Apply-for-a-juggling-licence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/009-Publish-form-Apply-for-a-juggling-licence.png -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/101-Preview-start-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/101-Preview-start-page.png -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/102-Preview-question-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/102-Preview-question-1.png -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/103-Preview-final-question.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/103-Preview-final-question.png -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/104-Preview-Check-your-answers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/104-Preview-Check-your-answers.png -------------------------------------------------------------------------------- /design/prototype-version-1/screenshots/105-Preview-Form-submitted.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-1/screenshots/105-Preview-Form-submitted.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/001-Form-Home.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/001-Form-Home.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/002-Create-a-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/002-Create-a-form.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/003-Form-Apply-for-a-juggling-licence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/003-Form-Apply-for-a-juggling-licence.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/004-Edit-question-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/004-Edit-question-1.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/005-Edit-question-1-hint-open.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/005-Edit-question-1-hint-open.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/006-Edit-question-2-What-is-your-date-of-birth.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/006-Edit-question-2-What-is-your-date-of-birth.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/007-Form-Apply-for-a-juggling-licence-added-questions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/007-Form-Apply-for-a-juggling-licence-added-questions.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/008-Edit-check-your-answers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/008-Edit-check-your-answers.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/009-Edit-form-submitted.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/009-Edit-form-submitted.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/010-Publish-form-Apply-for-a-juggling-licence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/010-Publish-form-Apply-for-a-juggling-licence.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/101-Preview-start-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/101-Preview-start-page.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/102-Preview-question-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/102-Preview-question-1.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/103-Preview-final-question.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/103-Preview-final-question.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/104-Preview-Check-your-answers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/104-Preview-Check-your-answers.png -------------------------------------------------------------------------------- /design/prototype-version-2/screenshots/105-Preview-Form-submitted.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-2/screenshots/105-Preview-Form-submitted.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/001-GOV.UK-Forms.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/001-GOV.UK-Forms.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/002-What-is-the-name-of-your-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/002-What-is-the-name-of-your-form.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/003-Form-overview-Apply-for-a-juggling-licence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/003-Form-overview-Apply-for-a-juggling-licence.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/004-Edit-question-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/004-Edit-question-1.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/005-Edit-question-1-hint-open.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/005-Edit-question-1-hint-open.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/006-Edit-question-2-What-is-your-date-of-birth.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/006-Edit-question-2-What-is-your-date-of-birth.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/007-Form-overview-Apply-for-a-juggling-licence-added-questions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/007-Form-overview-Apply-for-a-juggling-licence-added-questions.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/008-Edit-check-your-answers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/008-Edit-check-your-answers.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/009-Edit-form-submitted.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/009-Edit-form-submitted.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/010-Delete-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/010-Delete-page.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/011-Publish-form-Apply-for-a-juggling-licence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/011-Publish-form-Apply-for-a-juggling-licence.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/101-Preview-question-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/101-Preview-question-1.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/102-Preview-final-question.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/102-Preview-final-question.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/103-Preview-Check-your-answers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/103-Preview-Check-your-answers.png -------------------------------------------------------------------------------- /design/prototype-version-3/screenshots/104-Preview-Form-submitted.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-3/screenshots/104-Preview-Form-submitted.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/001-GOV.UK-Forms-added-forms.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/001-GOV.UK-Forms-added-forms.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/001-GOV.UK-Forms.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/001-GOV.UK-Forms.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/002-What-is-the-name-of-your-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/002-What-is-the-name-of-your-form.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/003-Form-overview-Apply-for-a-juggling-licence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/003-Form-overview-Apply-for-a-juggling-licence.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/004-Edit-question-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/004-Edit-question-1.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/005-Edit-question-2-What-is-your-date-of-birth.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/005-Edit-question-2-What-is-your-date-of-birth.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/006-Form-overview-Apply-for-a-juggling-licence-added-questions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/006-Form-overview-Apply-for-a-juggling-licence-added-questions.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/007-Edit-check-your-answers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/007-Edit-check-your-answers.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/008-Edit-form-submitted.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/008-Edit-form-submitted.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/009-Delete-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/009-Delete-page.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/010-Publish-form-Apply-for-a-juggling-licence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/010-Publish-form-Apply-for-a-juggling-licence.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/101-Preview-question-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/101-Preview-question-1.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/102-Preview-final-question.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/102-Preview-final-question.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/103-Preview-Check-your-answers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/103-Preview-Check-your-answers.png -------------------------------------------------------------------------------- /design/prototype-version-4/screenshots/104-Preview-Form-submitted.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-4/screenshots/104-Preview-Form-submitted.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/.DS_Store: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/.DS_Store -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/001-GOV.UK-Forms-added-forms.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/001-GOV.UK-Forms-added-forms.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/001-GOV.UK-Forms.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/001-GOV.UK-Forms.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/002-What-is-the-name-of-your-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/002-What-is-the-name-of-your-form.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/003-Form-overview-Apply-for-a-juggling-licence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/003-Form-overview-Apply-for-a-juggling-licence.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/004-Edit-question-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/004-Edit-question-1.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/005-Edit-question-2-What-is-your-date-of-birth.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/005-Edit-question-2-What-is-your-date-of-birth.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/006-Form-overview-Apply-for-a-juggling-licence-added-questions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/006-Form-overview-Apply-for-a-juggling-licence-added-questions.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/007-Edit-check-your-answers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/007-Edit-check-your-answers.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/008-Edit-form-submitted.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/008-Edit-form-submitted.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/009-Delete-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/009-Delete-page.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/010-Publish-form-Apply-for-a-juggling-licence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/010-Publish-form-Apply-for-a-juggling-licence.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/101-Preview-question-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/101-Preview-question-1.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/102-Preview-final-question.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/102-Preview-final-question.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/103-Preview-Check-your-answers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/103-Preview-Check-your-answers.png -------------------------------------------------------------------------------- /design/prototype-version-5/screenshots/104-Preview-Form-submitted.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-5/screenshots/104-Preview-Form-submitted.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/001-GOV.UK-Forms-added-forms.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/001-GOV.UK-Forms-added-forms.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/001-GOV.UK-Forms.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/001-GOV.UK-Forms.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/002-What-is-the-name-of-your-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/002-What-is-the-name-of-your-form.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/003-1-Task-list-page-tags-focus-create-your-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/003-1-Task-list-page-tags-focus-create-your-form.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/003-Create-a-form-Apply-for-a-juggling-licence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/003-Create-a-form-Apply-for-a-juggling-licence.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/004-Add-and-edit-your-questions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/004-Add-and-edit-your-questions.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/005-Edit-question-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/005-Edit-question-1.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/006-Edit-question-2-What-is-your-date-of-birth.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/006-Edit-question-2-What-is-your-date-of-birth.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/007-Add-and-edit-your-questions-added-questions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/007-Add-and-edit-your-questions-added-questions.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/008-Delete-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/008-Delete-page.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/009-Create-a-form-questions-in-progress.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/009-Create-a-form-questions-in-progress.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/010-Edit-form-summary-page-iframe.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/010-Edit-form-summary-page-iframe.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/010-Edit-form-summary-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/010-Edit-form-summary-page.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/011-Create-a-form-declaration-completed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/011-Create-a-form-declaration-completed.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/012-Edit-form-submitted-page-iframe.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/012-Edit-form-submitted-page-iframe.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/012-Edit-form-submitted-page.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/012-Edit-form-submitted-page.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/013-Create-a-form-what-happens-next-completed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/013-Create-a-form-what-happens-next-completed.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/014-Set-the-email-address-for-completed-forms.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/014-Set-the-email-address-for-completed-forms.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/015-Confirmation-code-sent.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/015-Confirmation-code-sent.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/016-Create-a-form-email-address-completed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/016-Create-a-form-email-address-completed.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/017-Enter-the-confirmation-code.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/017-Enter-the-confirmation-code.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/018-Email-address-confirmed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/018-Email-address-confirmed.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/018-The-confirmation-code-has-expired.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/018-The-confirmation-code-has-expired.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/019-Create-a-form-email-confirmation-completed.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/019-Create-a-form-email-confirmation-completed.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/020-Are-you-sure-you-want-to-change-this-email-address.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/020-Are-you-sure-you-want-to-change-this-email-address.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/021-Publish-form-Apply-for-a-juggling-licence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/021-Publish-form-Apply-for-a-juggling-licence.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/101-Preview-question-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/101-Preview-question-1.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/102-Preview-final-question.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/102-Preview-final-question.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/103-Preview-Check-your-answers-before-submitting-your-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/103-Preview-Check-your-answers-before-submitting-your-form.png -------------------------------------------------------------------------------- /design/prototype-version-6/screenshots/104-Preview-Your-form-has-been-submitted.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-6/screenshots/104-Preview-Your-form-has-been-submitted.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/001-form-home-landing.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/001-form-home-landing.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/001-form-home-with-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/001-form-home-with-form.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/002-form-create-a-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/002-form-create-a-form.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/003-create-form-create-form-statuses-focus.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/003-create-form-create-form-statuses-focus.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/003-create-form-create-form-statuses.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/003-create-form-create-form-statuses.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/003-create-form-including-email-statuses.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/003-create-form-including-email-statuses.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/003-create-form-make-live-focus.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/003-create-form-make-live-focus.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/003-create-form-privacy-contact-statuses-focus.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/003-create-form-privacy-contact-statuses-focus.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/003-create-form-set-email-statuses-focus.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/003-create-form-set-email-statuses-focus.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/003-create-form.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/003-create-form.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/004-form-index-no-questions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/004-form-index-no-questions.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/005-delete-question-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/005-delete-question-1.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/005-edit-page-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/005-edit-page-1.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/006-edit-page-2-saved.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/006-edit-page-2-saved.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/007-form-index-questions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/007-form-index-questions.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/008-create-form-question-in-progress.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/008-create-form-question-in-progress.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/1001-page-preview-new-tab-1.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/1001-page-preview-new-tab-1.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/1002-page-preview-new-tab-3.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/1002-page-preview-new-tab-3.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/1003-check-answers-page-preview-new-tab.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/1003-check-answers-page-preview-new-tab.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/1004-confirmation-page-preview-new-tab.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/1004-confirmation-page-preview-new-tab.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/101-edit-page-check-answers.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/101-edit-page-check-answers.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/102-edit-page-check-answers-preview-pane.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/102-edit-page-check-answers-preview-pane.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/201-edit-page-confirmation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/201-edit-page-confirmation.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/202-edit-page-confirmation-preview-pane.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/202-edit-page-confirmation-preview-pane.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/301-set-completed-forms-email.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/301-set-completed-forms-email.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/302-confirmation-code-sent.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/302-confirmation-code-sent.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/401-add-confirmation-code.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/401-add-confirmation-code.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/402-confirmation-code-expired.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/402-confirmation-code-expired.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/403-email-confirmation.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/403-email-confirmation.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/501-provide-link-to-privacy-information.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/501-provide-link-to-privacy-information.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/601-provide-support-details.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/601-provide-support-details.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/701-make-your-form-live.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/701-make-your-form-live.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/702-form-is-live.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/702-form-is-live.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/703-create-form-live.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/703-create-form-live.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/801-are-you-sure-you-want-to-edit-live-questions.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/801-are-you-sure-you-want-to-edit-live-questions.png -------------------------------------------------------------------------------- /design/prototype-version-7/screenshots/802-form-index-live.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/design/prototype-version-7/screenshots/802-form-index-live.png -------------------------------------------------------------------------------- /diagrams/architecture.md: -------------------------------------------------------------------------------- 1 | # GOV.UK Forms Architecture 2 | 3 | ```mermaid 4 | --- 5 | title: Form submission 6 | --- 7 | 8 | graph TD 9 | 10 | classDef default fill:#fff,stroke:#333,stroke-width:2px; 11 | 12 | classDef govuk fill:#1d70b8,stroke:#333,stroke-width:0px,color:#fff,text-align:left,font:arial; 13 | classDef forms fill:#000,stroke:#333,stroke-width:5px,color:#fff,font-size:28px; 14 | classDef notify fill:#000,stroke:#000,stroke-width:1px,color:#fff; 15 | classDef pay fill:#000,stroke:#000,stroke-width:1px,color:#fff; 16 | 17 | classDef org fill:#fe6,stroke:#fc3,stroke-width:5px,color:#000; 18 | 19 | classDef user fill:#dfd,stroke:#333,stroke-width:3px,color:#000; 20 | 21 | classDef optional stroke-dasharray: 10 5; 22 | 23 | user((form
completer)) 24 | 25 | gov.uk[GOV.UK 26 | The best place to find 27 | government services 28 | and information] 29 | forms[GOV.UK Forms] 30 | notify[GOV.UK Notify] 31 | pay[GOV.UK Pay] 32 | 33 | class gov.uk govuk 34 | class forms forms 35 | class notify notify 36 | class pay pay 37 | class gds gds 38 | 39 | 40 | subgraph org [Organisation] 41 | 42 | inbox[shared inbox] 43 | case[Case
Management
System] 44 | integration([system integration]) 45 | 46 | creator((form
creator)) 47 | processor((form
processor)) 48 | 49 | integration -..-> case 50 | inbox --> processor -.-> case 51 | 52 | end 53 | 54 | confirmation[/confirmation
email/] 55 | email[/submitted form
as email/] 56 | data[/submitted form
as structured data/] 57 | 58 | forms ~~~ creator 59 | creator -- create form --> forms 60 | 61 | user ~~~ confirmation ~~~ notify ~~~ forms 62 | 63 | user -- browse --> gov.uk -- links to --> forms -. optional .-> notify -. optional .-> confirmation -.-> user 64 | 65 | forms --> email --> inbox 66 | 67 | forms -. under development .-> data -.-> integration 68 | 69 | forms -. optional link to .-> pay -. reconcile payment .-> processor 70 | 71 | class org org 72 | class user,processor,creator user 73 | class integration,data,confirmation optional 74 | 75 | ``` 76 | -------------------------------------------------------------------------------- /diagrams/class-diagrams/README.md: -------------------------------------------------------------------------------- 1 | # Class Diagrams for GOV.UK Forms apps 2 | 3 | The mermaid files in this directory are [Class Diagrams](https://mermaid.js.org/syntax/classDiagram.html) for each of the apps we run that make up the main GOV.UK Forms system. 4 | 5 | ## How to generate 6 | 7 | In each app, install the `rails-erd` gem: 8 | 9 | ```ruby 10 | group :development do 11 | gem "rails-erd", git: "https://github.com/voormedia/rails-erd.git" 12 | end 13 | ``` 14 | 15 | We need the latest version in the repo, as at the time of writing the most recent release does not include [Mermaid support](https://github.com/voormedia/rails-erd/commit/22cfc76098e222b7c211f0369e80580aeaa22c70). 16 | 17 | > ⚠️ Note: Do not commit the gem into the app repos. 18 | 19 | Run: 20 | 21 | ```shell 22 | generator="mermaid" rake erd 23 | ``` 24 | 25 | This will create a file called `erd.mmd` in the root of the application. 26 | 27 | ## Update the diagram 28 | 29 | 1. Open the file in an editor and copy the contents (all of the `classDiagram` block). 30 | 2. Paste the contents into the corresponding diagram file, replacing everything inside the "mermaid" block: 31 | ```` 32 | ```mermaid 33 | classDiagram 34 | ... 35 | ``` 36 | ```` 37 | 3. Update the date near the top of the file. 38 | -------------------------------------------------------------------------------- /diagrams/class-diagrams/runner.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: GOV.UK Forms Runner app class diagram 3 | --- 4 | 5 | # GOV.UK Forms Runner app class diagram 6 | ## 2025-05-29 7 | 8 | ```mermaid 9 | classDiagram 10 | direction RL 11 | class `Submission` 12 | `Submission` : +jsonb answers 13 | `Submission` : +jsonb form_document 14 | `Submission` : +integer form_id 15 | `Submission` : +string mail_message_id 16 | `Submission` : +string mail_status 17 | `Submission` : +string mode 18 | `Submission` : +string reference 19 | `Submission` : +datetime sent_at 20 | ``` 21 | -------------------------------------------------------------------------------- /diagrams/images/ADR037-architecture-diagram.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/alphagov/forms/eb465924e8f09d509d0c2923eed4b76acecd4e39/diagrams/images/ADR037-architecture-diagram.png -------------------------------------------------------------------------------- /diagrams/sequence-diagrams/README.md: -------------------------------------------------------------------------------- 1 | # GOV.UK Forms Sequence Diagrams 2 | 3 | ## Introduction 4 | 5 | The diagrams in this folder (created using [Mermaid](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-mermaid-diagrams)) show the interactions between users and GOV.UK Forms, including the 3 applications [forms-admin](https://github.com/alphagov/forms-admin), [forms-api](https://github.com/alphagov/forms-api), and [forms-runner](https://github.com/alphagov/forms-runner). 6 | 7 | The diagram below is to provide an overview of the different users and systems that interact with each other. For clarity, not all interactions are shown. Please refer to individual sequence diagrams for detailed interactions. 8 | 9 | ## High Level Architecture of GOV.UK Forms 10 | 11 | ```mermaid 12 | graph TD 13 | subgraph users 14 | super_admin((GOV.UK Forms
Team

Super Admin)) 15 | editor((form editor)) 16 | content((content designer)) 17 | filler((Person filling in a form)) 18 | processor((form processor)) 19 | end 20 | 21 | auth0(Auth0) 22 | sso(Google Workspace) 23 | govuk(GOV.UK website) 24 | 25 | super_admin --- sso --- auth0 26 | editor --- auth0 27 | content --- govuk 28 | 29 | subgraph sg1 [GOV.UK Forms] 30 | admin(forms-admin) 31 | api(forms-api) 32 | runner(forms-runner) 33 | end 34 | 35 | editor---runner 36 | 37 | auth0 --- admin --- api 38 | filler --- govuk 39 | filler --- runner --- api 40 | 41 | notify(GOV.UK Notify) 42 | 43 | pay(GOV.UK Pay) 44 | filler -.- pay -.- runner 45 | 46 | filler -.- notify 47 | notify --- runner 48 | processor --- notify 49 | 50 | 51 | ``` 52 | 53 | ## Links to Sequence Diagrams 54 | 55 | * [authentication](authentication.md) 56 | * [creating a form](creating-a-form.md) 57 | * [publishing a form](publishing-a-form.md) 58 | * [filling in a form](filling-in-a-form.md) 59 | * [changing a form](changing-a-form.md) 60 | 61 | -------------------------------------------------------------------------------- /diagrams/sequence-diagrams/publishing-a-form.md: -------------------------------------------------------------------------------- 1 | # Making a form live 2 | 3 | ```mermaid 4 | sequenceDiagram 5 | title Previewing a form 6 | actor user as form creator 7 | participant browser as Web Browser 8 | participant admin as forms-admin 9 | link admin: GitHub repo @ https://github.com/alphagov/forms-admin 10 | participant api as forms-api 11 | link api: GitHub repo @ https://github.com/alphagov/forms-api 12 | 13 | note right of user: All tasks except "Make your form live" have been completed 14 | 15 | admin-->>user: show "Create a form" page 16 | user->>browser: Click "Make your form live" link 17 | browser->>admin: GET /forms/{form id}/make-live 18 | admin->>api: GET /api/v1/forms/{form id} 19 | browser-->>user: show "Make your form live" page 20 | 21 | user->>browser: Confirm making form live
click "Save and continue" button 22 | browser->>admin: POST /forms/{form id}/make-live 23 | admin->>api: GET /api/v1/forms/{form id} 24 | admin->>api: GET /api/v1/forms/{form id}/pages 25 | admin->>api: POST /api/v1/forms/{form id}/make-live
payload: {includes all form attributes and values}
Controller Action doesn't use any 26 | browser-->>user: show "Your form is live" page 27 | user->>user: Copy URL for the form 28 | 29 | ``` 30 | 31 | # Publishing a form 32 | 33 | ```mermaid 34 | sequenceDiagram 35 | Title Publishing a form 36 | actor user as Form creator 37 | actor content as Content Designer 38 | participant publishing as GOV.UK Publishing tools 39 | participant govuk as GOV.UK website 40 | 41 | note right of user: Form has been made live 42 | 43 | user->>content: Provide form URL 44 | 45 | content->>publishing: Edit existing page or create new page
Link to form URL 46 | 47 | publishing->>govuk: Publish new content 48 | 49 | ``` 50 | -------------------------------------------------------------------------------- /diagrams/sequence-diagrams/review-apps-workflow.md: -------------------------------------------------------------------------------- 1 | ## Workflow for review apps on GOV.UK Forms 2 | 3 | ```mermaid 4 | %%{init: { "sequence": { "showSequenceNumbers": true }}}%% 5 | 6 | sequenceDiagram 7 | 8 | actor dev as Dev 9 | actor reviewer as Reviewer 10 | participant pr as PR 11 | participant app as Review App 12 | 13 | dev ->> pr: open 14 | activate pr 15 | 16 | pr ->> app: create 17 | activate app 18 | 19 | pr -->> dev: review app URL 20 | 21 | loop Iteration 22 | dev ->> pr: new commit 23 | pr ->> app: redeploy 24 | dev ->> app: visit 25 | end 26 | 27 | reviewer ->> pr: review 28 | pr -->> reviewer: review app URL 29 | reviewer ->> app: visit 30 | reviewer ->> pr: approve 31 | 32 | dev ->> pr: merge 33 | pr ->> app: destroy 34 | deactivate app 35 | 36 | pr -->> dev: merged 37 | deactivate pr 38 | ``` 39 | -------------------------------------------------------------------------------- /engagement/README.md: -------------------------------------------------------------------------------- 1 | # Coming soon 2 | -------------------------------------------------------------------------------- /product/readme.md: -------------------------------------------------------------------------------- 1 | Product information and files go here. 2 | -------------------------------------------------------------------------------- /research/2021-08-22-complex-logic.md: -------------------------------------------------------------------------------- 1 | # Findings 2 | - Most participants found it difficult to add in complex logic 3 | -------------------------------------------------------------------------------- /research/2022-03-15-EPIC-A-TESTING-SECURITY-FEATURES.md: -------------------------------------------------------------------------------- 1 | # EPIC A TESTING SECURITY FEATURES 2 | ## KEY HEADLINES 3 | 4 | - DPOs and cyber/security are supportive of GOV.UK Forms. They believe in the value of digitalising forms. They are seen as a quicker, safer and better solution. 5 | - Our proposition is fully endorsed by all and meets key needs around reducing risk and providing more control over data. All our security features are from tried and trusted methods of security. 6 | - Front-end features are a key selling point as they can help overcome problems around data minimalization, accuracy and storage. Desirable features include limits over free text boxes, mandatory privacy notices, built-in tips/ advice on good practice. 7 | - We can further meet their needs for control by providing a dashboard where all forms are stored. It would include a tagging system highlighting high risk forms and information on who created forms and when. 8 | - Our primary user group will not be aware of the practices involved in managing digital data. We can help with their transition by providing DPIA templates to help with good practice. 9 | 10 | ## SUPPORTING EVIDENCE 11 | [Epic A : testing security features](https://docs.google.com/presentation/d/1D3LJgQPtbDvczGvmbyWy-C9f4mBTlBhw/edit?usp=sharing&ouid=116661804351516042654&rtpof=true&sd=true) 12 | -------------------------------------------------------------------------------- /research/2022-05-03_Basic_Form_Building.md: -------------------------------------------------------------------------------- 1 | # Usability testing: Basic form building 2 | 3 | 2022-05-03 / Sprint 2 4 | 5 | ## Aims 6 | To test basic form builder journeys, including: 7 | - Adding a short answer question 8 | - Adding a date question 9 | - Adding a numerical question 10 | - Previewing a form 11 | - Reordering question logic 12 | 13 | ## Users 14 | - Civil Servants 15 | - 4 users 16 | 17 | ## Methodology 18 | - Usability Testing 19 | 20 | ## Key Headlines 21 | 22 | - The landing page 23 | - users were initially confused when arriving on the landing page and had a need to see a summary and preview of all the steps they needed to complete at this stage. This led to the idea of a ‘task list’ which outlines all the steps involved. 24 | - Users felt that a drop down with relevant forms would be useful as not everyone in the organisation would know what a form was called 25 | - Add a short answer question: there was some confusion as to what a ‘short’ and ‘long’ answer question was and this caused some hesitation - is a name a short question type or long? 26 | - Add a number question: fairly easy to complete but some users wanted a numerical field rather than an open text field so they cold control the information they were receiving 27 | - Previewing: some users were concerned that previewing a form would result them losing changes. This lea to the creation of the ‘save and preview’ button 28 | - The preview pane: many users were either a) unsure of what the preview pane was and as a result ignored it or b) expected it to auto populate with questions. In both scenarios users missed out on the ability to preview the question. 29 | - Adding a NI no: some users expected this to be formatted in two boxes to reflect how NI numbers appear 30 | - Change question order: generally this feature works well but there was some confusion around the language used on the page and some users point out that this could be hard to use for very long forms. Users prior experience of Whitehall Publisher informs their expectations. 31 | - Character limits in text boxes were seen as useful. 32 | - Overall, many had a positive experience and completed tasks with relative ease. There were questions around whether a declaration was necessary in all scenario and how people could review the form. There was an expectation that there would be a 2i process and a preview version people could share. There was also the expectation that there would be a publish confirmation page before a form goes live. 33 | 34 | ## Supporting Evidence 35 | - [Report](https://app.mural.co/t/gaap0347/m/gaap0347/1651569498203/782ddd2576b3b1812f6cb7f851a9d3143c301efb?sender=uac1457e37aa6525eed627424) 36 | -------------------------------------------------------------------------------- /research/2022-06-28_Basic_Form_Building.md: -------------------------------------------------------------------------------- 1 | # Usability testing: Basic Form Building 2 | 3 | 2022-06-28 / Sprint 6 4 | 5 | ## Aims 6 | To test usability of basic form builder journeys, including: 7 | - Basic building a form journeys: 8 | - Name the form 9 | - Add a long answer question and a date question (combination task) 10 | - Add a short answer question 11 | - Add a National Insurance number question 12 | - Add a phone number question 13 | - Preview a question 14 | 15 | Return to a form journeys: 16 | - Change the name of a form 17 | - Change the content of questions 18 | - Change preview formatting 19 | - Delete a question 20 | - Test a form 21 | - Re order questions 22 | 23 | ## Users 24 | - Civil Servants 25 | - 3 users 26 | 27 | ## Methodology 28 | - Usability Testing 29 | 30 | ## Key Headlines 31 | 32 | - There were consistently high scores across the tasks and some genuine moments of delight. Many elements of the prototype work well from a user perspective. However, there was also some familiar problems. 33 | - The preview pane appeared to work more effectively than previous rounds. 34 | - The addition of the ‘preview and save’ button was often used to discover the preview function. However, it suffers still from being visually recessive (especially adjacent to the vivid green 'save and continue button) and, for some, features too far down the page 35 | - Encouragingly, where users struggled or hesitated, they were able to resolve the problem themselves and there was a fairly quick learning curve. 36 | - Generally participants were able to add two questions with minimal difficulty. There were some minor problems 37 | - Throughout task users began to use the preview pane spontaneously (unprompted). 38 | - We also saw an emerging pattern with users wanting to add questions first and preview at the end or if they were unsure about something. 39 | 40 | ## Supporting Evidence 41 | - [Report](https://app.mural.co/t/gaap0347/m/gaap0347/1655912742334/57c265e721088247b57debffe73bd98ab89c0f09?fromVisitorModal=true&sender=f0e74d83-05ad-4604-975f-e97131fca4e9) 42 | - [Playback](https://drive.google.com/file/d/10dJUkO3j-nVJxozMm4Y1mkUbNJ5HZgue/view?usp=sharing) 43 | - [Supporting documents](https://drive.google.com/drive/folders/1VOMG9a0XyV371_1LxV9qUaddkyuY_xjE) 44 | -------------------------------------------------------------------------------- /research/2022-06-28_The_Review_Process.md: -------------------------------------------------------------------------------- 1 | # Understanding the review process 2 | 3 | 2022-06-28 / Sprint 6 4 | 5 | ## Aims 6 | - To understand how the review process works 7 | 8 | ## Users 9 | - Civil Servant 10 | - 1 user 11 | 12 | ## Methodology 13 | - Interview 14 | 15 | ## Key Headlines 16 | 17 | - The need to change a form comes from one of three teams: the policy team, the customer service team, or the processing team. 18 | - All teams have to request a change via the Content Change Request form as a first step. This is sent to the Content Team who review it, estimate the amount of work needed and triage it to the appropriate team. 19 | - A small change may be a content tweak based on customer feedback and this is dealt with quickly and informally. A large change, such as a format change, may take much longer and a full multidisciplinary project team may be assembled 20 | - For form creators, it can be difficult to make MS Word documents look correct as often adding multiple comments causes formatting issues. 21 | - Sometimes it can be difficult to review a document when there are too many changes making it ‘difficult to look at’ and hard to see where relevant changes are. 22 | - Form creators want control over the review process similar to a fact check, where policy people or legal can only comment on specific sections of the form. 23 | - The sign off process can be a long process as different changes are circulated through different teams. Version control becomes an issue. 24 | - Final sign off for RPS is done by the Service Manager but before that he will give an initial sign off where it will go through the Policy team, CST, business areas and then back to the manager to confirm. 25 | - The amend my personal details form is a basic form and it hasn’t needed many iterations to develop. When it comes to reviewing and changing it, it is updated quickly and informally. 26 | - Other form creators we’ve spoken to tell us that the track changes feature is important in order to collect feedback from relevant people. Some users like to create the form in MS Word first so it can be reviewed and then copied as a final version into a form builder e.g. Survey Monkey. 27 | 28 | ## Supporting Evidence 29 | - [Report](https://docs.google.com/presentation/d/1Kd21pObNi68KmPPwOC7wEGsLfhWJNdVV/edit) 30 | - [Playback](https://drive.google.com/file/d/1fadyJNaXB-PfeRNBCM-0cQBZqD_tBXkJ/view?usp=sharing) 31 | - [Supporting documents](https://drive.google.com/drive/folders/1VCr5DkqRLssCBF0_Ax6eCqN8DY8RSMNA) 32 | -------------------------------------------------------------------------------- /research/2022-08-29_Testing_form_processing_efficiency.md: -------------------------------------------------------------------------------- 1 | # Testing form processing efficiency (GOV.UK Forms vs document-based) 2 | 3 | 2022-08-29 / Sprint 10 4 | 5 | ## Aims 6 | - To capture estimated timings for current forms compared to GOV.UK Forms outputs 7 | - To understand challenges and needs for processing the output of forms created with GOV.UK Forms 8 | 9 | ## Users 10 | - Civil Servants 11 | - 1 user 12 | 13 | ## Methodology 14 | - Unmoderated interactive activity 15 | 16 | ## Key Headlines 17 | 18 | The average times spent processing a form for each pot were: 19 | - Existing forms: 3 minutes 20 | - Existing forms with errors: 8 minutes 11 seconds 21 | - GOV.UK Forms output: 2 minutes 58 seconds 22 | - Getting missing information and checking if information is valid are the areas with the longest times recorded. 23 | 24 | Qualitative feedback highlighted some common challenges and things that can slow the processing of forms down: 25 | - Completers who don’t put their LN claim number in the subject line of the email. 26 | - It takes longer to find a CN case number than an LN claim number on the system 27 | - Typos with claim or case numbers. 28 | - Emails being sent from an email address that is not the same as the one on their claim. 29 | 30 | ## Supporting Evidence 31 | - [Report](https://docs.google.com/document/d/1R5bleGlN0jt0BtuVdvUeRNs1mdKijkQZ003wfrWn9Fk/edit) 32 | - [Supporting documents](https://drive.google.com/drive/folders/1RFkIZA9txFo-NNl-LDIEl4kOSdHkLcd2) 33 | -------------------------------------------------------------------------------- /research/2022-09-12-MCA_Processing.md: -------------------------------------------------------------------------------- 1 | # Form Processing for 'Volunteer to be a Coastguard' form 2 | 3 | ## Key Headlines 4 | 5 | - When there is missing information, GOV.UK Forms can make a big difference to processing time for these forms. 6 | - Even compared to straightforward, complete forms, GOV.UK Forms still saves time 7 | - Existing forms completed correctly: 24 seconds saved per form (on average) - 36% faster 8 | - Forms with errors or missing information: 67 seconds saved per form (on average) - 55% faster 9 | - Potential time saved per year for this form: 51 hours (2,750 forms p.a. with a 67 second saving per form) 10 | - SCOOs claim that GOV.UK Forms output would be easier to read and process if there was clearer delineation between questions and responses 11 | - The addition of subject line would make the process more efficient for SCOOs. It would allow them to store forms and organise them with unique names/subjects. Ideally this would have: Name of form (Volunteer to be a Coastguard), Area team, Applicant name. 12 | - Having form completers answer to email questions formatted as mailto: links makes it convenient to use them to make contact. 13 | - There was a comment that the personal information in emails was very visible in inboxes, especially if using preview panes. 14 | 15 | ## Supporting Evidence 16 | - [Report](https://docs.google.com/presentation/d/1ZIliyiwD9qaqzRo2CLzt3lNbLlEYMgT-/edit?usp=sharing&ouid=104563467983597523310&rtpof=true&sd=true) 17 | - [Video playback](https://drive.google.com/file/d/1Oxh-fepfhfGUwQuhTclhuf97Ij57iX6G/view?usp=sharing) 18 | -------------------------------------------------------------------------------- /research/2022-10-24_Form_Builder_Usability_Testing.md: -------------------------------------------------------------------------------- 1 | # Usability testing: Form building 2 | 3 | 2022-10-24 / Sprint 14 4 | 5 | ## Aims 6 | To test form builder journeys required to digitise a specific partner department’s form. This included testing specific features for creating questions, as well as publishing a live version of the form: 7 | - Add a new name to the form 8 | - Add a name question 9 | - Add a address question 10 | - Add content before a question 11 | - Preview a form 12 | - Add ‘what happens next’ page 13 | - Set up email address for completed form 14 | - Add declaration 15 | - Add a privacy notice 16 | 17 | ## Users 18 | - Civil Servants 19 | - 6 users 20 | 21 | ## Methodology 22 | - Usability testing 23 | 24 | ## Key Headlines 25 | 26 | - Overall, a very positive experience for all users with many completing the tasks quickly and easily. 27 | - Adding a name question: some users were uncertain how to create a name question with multiple parts to it such as first name, last name, prefix. 28 | - Preview pane: users found and used preview pane more easily than in some preview sessions.Users were looking for an option to preview the entire form on the task list page. 29 | - Add content to a page: one user copied and pasted a very long question, which displayed poorly. This led them to simplify the question they were asking. 30 | - The form overview page: some users found numbering on the task list page felt inconsistent. 31 | - Users looked for ways to complete the 'in progress' tag next to the 'add and edit questions' link 32 | - There were problems with navigating between the 'form overview' page and the 'create a form' page. This often resulted in users becoming stuck and unsure how to progress. 33 | - There was some confusion from less digitally confident users about what 'preview in a new tab' meant or did. 34 | - Add a declaration: there was some confusion from less digitally confident users about whether the declaration page was for them or form completers. 35 | 36 | ## Supporting Evidence 37 | - [Report](https://drive.google.com/drive/folders/1sz7wfVsX8UWIJWd3htyCPBxpOqTPasBB) 38 | - [Supporting documents](https://drive.google.com/drive/folders/1sz7wfVsX8UWIJWd3htyCPBxpOqTPasBB) 39 | 40 | 41 | -------------------------------------------------------------------------------- /research/2022-11-23-Feedback_on_processing_of_the_first_form.md: -------------------------------------------------------------------------------- 1 | # Feedback on processing of the first form 2 | 3 | 2022-11-23 / Sprint 16 4 | 5 | ## Aims 6 | - Collect feedback from their processing team on what the experience with GOV.UK Forms has been like generally 7 | - Understand what has worked well and not so well 8 | - Identify ways we can improve going forward 9 | 10 | ## Users 11 | - Civil Servants 12 | 13 | ## Methodology 14 | - Focus Group / Interview 15 | 16 | ## Key Headlines 17 | 18 | - The form processors reported a positive overall experience, although there have been some teething issues along the way 19 | - Including a question with ‘LN numbers or case reference numbers’ led to an increase in processing time. 20 | - The processors reported an issue with receiving information that required a decimal point e.g. number of days taken. This has been resolved. 21 | - An inconsistent experience for claimants where some similar forms can be completed via a webform, and other forms need to be completed with document-based submissions. 22 | - Processors reported an improvement in processing time of between 1.5 – 2.5 minutes per form. Much of this was attributed to receiving information in more organised, well laid out fashion making it easier to find and transpose into the CMS 23 | 24 | ## Supporting Evidence 25 | - [Report](https://docs.google.com/presentation/d/1auIySXU8ENpf9w7pplidhnRSpNNWXu1j/edit) 26 | - [Other documents](https://drive.google.com/drive/folders/1tW3CMiESgubPZQBJfWecZ07IlPzwFQdL) 27 | -------------------------------------------------------------------------------- /research/2022-12-08_File_Upload_And_Optional_Questions_Processing.md: -------------------------------------------------------------------------------- 1 | # File upload and optional questions processing 2 | 3 | 2022-12-08 / Sprint 17 4 | 5 | ## Aims 6 | - How do form processors currently receive and work with forms that require additional evidence or documents to be sent? 7 | - Can we use Notify to send forms with additional evidence or documents? 8 | - Does the Notify approach work for processors? 9 | - How do processors feel about receiving files as attachments? 10 | - How do they feel about receiving links? 11 | 12 | ## Users 13 | - Civil Servants 14 | - 8 users 15 | 16 | ## Methodology 17 | - Interviews 18 | 19 | ## Key Headlines 20 | 21 | - Form processors preferred documents sent to them as attachments, not as individual links. This is largely because of the convenience of having files to preview in an inbox, and the time it takes to follow and download links. 22 | - Many form processors who receive documents require multiple documents. 80% need more than one document. 23 | - The majority of people receiving documents receive scans or photos, so capacity is needed for larger file sizes. 24 | - Most people keep documents in their own file systems or case management system. 25 | - Most people seem to prefer showing optional questions in the forms output, even if those questions have not been completed. 26 | 27 | 28 | ## Supporting Evidence 29 | - [Report](https://docs.google.com/presentation/d/1fFSjoXwM0rO0sJHDHRUak9a4aphiutl8u7HYlYdqX1c/edit#slide=id.g180154c838d_0_0) 30 | - [Playback](https://drive.google.com/drive/folders/1XdJCZYlsc9GedCEKWHhYvP8O0FdFf1-m) 31 | -------------------------------------------------------------------------------- /research/2022-9-12_Testing_form_processing_efficiency.md: -------------------------------------------------------------------------------- 1 | # Testing form processing efficiency (GOV.UK Forms vs document-based) 2 | 3 | ## Key Headlines 4 | 5 | - When there is missing information, GOV.UK Forms can make a big difference to processing time for these forms. 6 | - Even compared to straightforward, complete forms, GOV.UK Forms still saves time 7 | - Existing forms completed correctly: 24 seconds saved per form (on average) - 36% faster 8 | - Forms with errors or missing information: 67 seconds saved per form (on average) - 55% faster 9 | - Potential time saved per year for this form: 51 hours (2,750 forms p.a. with a 67 second saving per form) 10 | - SCOOs claim that GOV.UK Forms output would be easier to read and process if there was clearer delineation between questions and responses 11 | - The addition of subject line would make the process more efficient for SCOOs. It would allow them to store forms and organise them with unique names/subjects. Ideally this would have: Name of form (Volunteer to be a Coastguard), Area team, Applicant name. 12 | - Having form completers answer to email questions formatted as mailto: links makes it convenient to use them to make contact. 13 | - There was a comment that the personal information in emails was very visible in inboxes, especially if using preview panes. 14 | 15 | ## Supporting Evidence 16 | - [Report](https://drive.google.com/drive/folders/1VMn3RWPP-2TAgNbTxuOvpT4LCXvFAhEV) 17 | - [Playback](https://drive.google.com/file/d/1Oxh-fepfhfGUwQuhTclhuf97Ij57iX6G/view?usp=sharing) 18 | - [Supporting documents](https://drive.google.com/drive/folders/1VMn3RWPP-2TAgNbTxuOvpT4LCXvFAhEV) 19 | -------------------------------------------------------------------------------- /research/2023-01-31_Usability_testing_with_private_beta_partner_form_creator.md: -------------------------------------------------------------------------------- 1 | # Usability testing with private beta partner form creator 2 | 3 | 2023-01-31 / Sprint 21 4 | 5 | ## Aims 6 | Test the usability of the form builder for creating a draft version of a partner department’s form 7 | 8 | ## Users 9 | - Civil Servants 10 | - 1 user 11 | 12 | ## Methodology 13 | - Usability Testing 14 | 15 | ## Key Headlines 16 | 17 | - Form creator was able to create all questions without any major issues 18 | - Used statements from the original form (Name:) rather than conversational questions (What is your name?) 19 | - Expected questions to have validation, tested this with preview and was satisfied with this feature. 20 | - Some uncertainty about when to use single and multiple lines of text. This appeared to stem from not knowing what the questions would look like to the end user when creating them. 21 | - Expected the save question button to take them to a different page rather than save only. 22 | - Copied and pasted long hints that did not fit the hint text boxes. Commented that the boxes could be larger. 23 | 24 | ## Supporting Evidence 25 | - [Report](https://docs.google.com/document/d/1Y5CMinca1z2loH770cfSLy4UdkIBW-m4grKQ1GrndfY/edit#) 26 | - [Additional documents](https://drive.google.com/drive/folders/1IRHcNvn3xR2v0nS0wbbJFE0H9rweszxy) 27 | -------------------------------------------------------------------------------- /research/2023-03-03_Accessiblity_Testing.md: -------------------------------------------------------------------------------- 1 | # Accessibility testing: Form building 2 | 3 | 2023-03-03 / Sprint 22 4 | 5 | ## Aims 6 | To understand the user experience of our form builder product for people with access needs. Including: 7 | - Autocomplete questions 8 | - Select from list 9 | - Saving questions 10 | - Status labels on tasks 11 | 12 | ## Users 13 | - Members of the public with access needs 14 | - 6 users 15 | 16 | ## Methodology 17 | - Usability testing (Accessiblity focus) 18 | 19 | ## Key Headlines 20 | 21 | - User experience: Generally positive feedback, but lots of specific issues to further work on. 22 | - Autocomplete questions: Working well, and beneficial for accessibility. 23 | - Select from list: Options / question order can be confusing 24 | - Saving questions: Functioned well, but ‘Save question’ button isn’t clear to everyone. 25 | - Status labels on tasks: Worked well, users noticed and commented they were useful. 26 | - All users were relatively successful creating questions and building a form. 27 | - Some users found it hard to understand how questions would be presented when creating and writing them. 28 | - Some specific language and content was hard to understand. 29 | - We found several specific technical issues with how GOV.UK Forms interacts with screen readers. These have been detailed in the full report and cards created in the backlog to address each of them. 30 | 31 | ## Supporting Evidence 32 | - [Report](https://docs.google.com/presentation/d/1_1tZCUk019wTKWI9eF_DZdJ7DpOr93l6kX1lREDkls0/edit#slide=id.g1d1235c61d0_0_31) 33 | - [Further documents](https://drive.google.com/drive/folders/1SgylWBoM0SG2AGNdk5a-Moa-2T7G45Mx) -------------------------------------------------------------------------------- /research/2023-04-14_Usability_Testing_Draft_Live_Feature.md: -------------------------------------------------------------------------------- 1 | # Usability testing: Draft / Live feature 2 | 3 | 2023-04-14 / Sprint 26 4 | 5 | ## Aims 6 | To test the new designs for: 7 | - creating a new draft of a live form 8 | - preparing changes in a draft of a live form 9 | - making your changes live 10 | 11 | ## Users 12 | - Civil Servants 13 | - 5 users 14 | 15 | ## Methodology 16 | - Usability Testing 17 | 18 | ## Key Headlines 19 | 20 | - The concept of a live form you then make a draft of to edit was understood by users. 21 | - Users noticed the ‘Live’ and ‘Draft labels and made use of them. 22 | - All users managed to make the various changes to forms, with a few uncertain moments about general navigation. 23 | - All users wanted to understand the form before editing, and used the question view and preview functions to successfully do this. 24 | - Two users thought that the form would be put in a maintenance state and unavailable to completers while they were editing their draft. 25 | - Two users did not make their form live, partly due to not noticing the link to do so. 26 | 27 | ## Supporting Evidence 28 | - [Report](https://docs.google.com/presentation/d/1a-DTcB0dMOtEL3iV9L0lUajA_pgY3SI6Y7fBTkiNQpM/edit#slide=id.g2390911b466_0_31) 29 | - [Playback](https://drive.google.com/file/d/19vjt3hvZZw5XObtR93epa4mmDEZ-6qyh/view?usp=sharing) 30 | - [Further documents](https://drive.google.com/drive/folders/1q9WOLeIN6AjNkBGTycOqRZ2rJgOAWTeP) -------------------------------------------------------------------------------- /research/2023-06-07_Usability_testing_Simple_routing.md: -------------------------------------------------------------------------------- 1 | ## Usability testing: Simple Routing 2 | 3 | 2023-06-07 / Sprint 29-30 4 | 5 | ## Aims 6 | - To test current design for simple routing with users 7 | - To get feedback on how the language used to describe simple routing resonates with users and communicates the concepts 8 | - To test error messages relating to simple routing with users 9 | 10 | ## Users 11 | - Members of the public, one Civil Servant (who had immediate need for this feature) 12 | - 7 users 13 | 14 | ## Methodology 15 | - Usability Testing 16 | 17 | ## Key Headlines 18 | - Most people looked for routing in the ‘edit page’ of the question they wanted to skip. Most of them did not discover the ‘add question route’ button without prompting. 19 | - When people were prompted to use the button, most successfully set up routes for forms with existing questions. 20 | - Those users who understood routing largely understood error messages. It might be worth further testing on those involving question order changing. 21 | - The more experienced user applied their mental model of ‘branching’ at times, and this led them to experience some friction with simple routing. 22 | - Less digitally confident users found the tasks difficult. More confident people were able to complete them. 23 | 24 | ## Supporting Evidence 25 | - [Report](https://docs.google.com/presentation/d/1V81oe77gEkIgfedn5AXOYYTR3wWAiUOxYd-tmeiP4cs/edit?usp=drive_link) 26 | - [Playback](https://drive.google.com/file/d/17yYelusQOP-hhX8UIvbenlccK4kAViZk/view?usp=drive_link) 27 | - [Further documents](https://drive.google.com/drive/folders/1-_lcepxw4UEe_3nof3XW-GJKJWpX3rT8) -------------------------------------------------------------------------------- /research/2023-08-01_Usability_Testing_Form_Completers copy.md: -------------------------------------------------------------------------------- 1 | # Usability testing: Form Completers 2 | 3 | 2023-08-01 / Sprint 31-32 4 | 5 | ## Aims 6 | - Test usability of forms created using GOV.UK Forms, including all current answer types. 7 | - Compare usability and time taken for these with document based forms 8 | 9 | ## Users 10 | - Members of the public 11 | - 6 users 12 | 13 | ## Methodology 14 | - Usability Testing 15 | 16 | ## Key Headlines 17 | 18 | - GOV.UK Forms were preferred to document based forms. 19 | - There was lots of positive feedback about features that make GOV.UK Forms easy and clear to complete. 20 | - We observed people complete forms more fully and accurately when they were in GOV.UK Forms format. 21 | - When looking for help, several people said they would prefer information to help them to solve the problem. Contacting a civil servant for help was not what they were looking for. 22 | - Several situations showed that giving form completers enough context is very important. There may be some opportunities to further support form builders to do this. 23 | 24 | ## Supporting Evidence 25 | - [Report](https://docs.google.com/presentation/d/1JmUP4LkIqZskFdb7S0x8n4hNdYjs7xR0SIj92ZmM2Ro/edit) 26 | - [Folder - including playback video](https://drive.google.com/drive/folders/1WhjxKeRVmkgO7TRgvs9Qeb-2YawVFYFV) 27 | -------------------------------------------------------------------------------- /research/2023-08-09-Usability_Testing_Authentication.md: -------------------------------------------------------------------------------- 1 | # Usability testing: Authentication and trial accounts 2 | 3 | 2023-08-09 / Sprint 31-34 4 | 5 | ## Aims 6 | - To understand attitudes towards signing up for a new online tool 7 | - To test the usability of two authentication methods 8 | - To understand attitudes towards and needs for trial account 9 | 10 | ## Users 11 | - Civil Servants 12 | - 5 users 13 | 14 | ## Methodology 15 | - Usability Testing 16 | 17 | ## Key Headlines 18 | 19 | - Using an email code rather than a password felt different to participants, but they were all relatively comfortable with it. 20 | - Participants preferred the Auth0 journey due to the simple look and feel and the numeric codes. 21 | - Most participants would have got started with the tool rather than reading the landing page thoroughly. But they said it was clear and useful when they read the content. 22 | - The concept of a limited trial account was clearly understood. The main limitation was seen as not being able to share forms with the public. But participants weren’t yet clear on how they would move beyond the trial. 23 | 24 | ## Supporting Evidence 25 | - [Report](https://docs.google.com/presentation/d/1y7atILC8ZkkgytN901waVWI7jsVxq37cW8xL0fvVpI4/edit#slide=id.g25f7a5b3cb1_0_445) 26 | - [Playback Video](https://drive.google.com/file/d/1pI3b8luMB_aeCTHFn4VvUYFX-pCps_Ym/view?usp=drive_link) 27 | - [Folder](https://drive.google.com/drive/folders/1EHhqDp8JPgsuJU6aJE5triRhboTfbzLS) -------------------------------------------------------------------------------- /research/2023-08-30_Detailed_Guidance_Usability_Testing.md: -------------------------------------------------------------------------------- 1 | # Usability testing: ’Detailed Guidance‘ and ‘Check Your Questions’ 2 | 3 | 2023-08-30 / Sprint 35 4 | 5 | ## Aims 6 | - To test the usability of the new iteration on the design for the ‘add a question’ journey. 7 | - To test the usability of the ‘detailed guidance’ feature. 8 | - To understand how well people are able to add markdown formatting to ‘detailed guidance’ using the ‘detailed guidance’ feature and the associated content 9 | 10 | ## Users 11 | - Civil Servants 12 | - 5 users 13 | 14 | ## Methodology 15 | - Usability Testing 16 | 17 | ## Key Headlines 18 | 19 | - ‘Check your question’ was used well, and came across as a natural part of the process. Several users commented on how useful it was for them. 20 | - ‘Detailed guidance’ was used with some trial and error. Participants mostly differentiated it from hints and used appropriately. 21 | - Formatting using Markdown was very much trial and error. All participants completed some formatting and used the preview to verify this. 22 | - There are a number of specific ways participants used the markdown input, preview and guidance that we should look at addressing. Some of these are related to content, some to design. 23 | 24 | ## Supporting Evidence 25 | 26 | - [Report](https://docs.google.com/presentation/d/1cZKLrPDaXZlqHtg_y8rYE2eKA1B26Hc8YiUBJKGc-jg/edit?usp=drive_link) 27 | - [Playback](https://drive.google.com/file/d/1MKPiGkWCs9jKp86w7joRrsHZV-H20FRR/view?usp=drive_link) 28 | - [More documents](https://drive.google.com/drive/folders/1L52JCUb8hLea32lS5im6mM7Y4AKhZGWV) -------------------------------------------------------------------------------- /research/2023-09-26-Early_Access_Journey.md: -------------------------------------------------------------------------------- 1 | # Usability testing: Early Access Journey 2 | 3 | 2023-09-06 / Sprint 37 4 | 5 | ## Aims 6 | - Test acceptance of the ‘early access’ sign up journey 7 | - Understand how new users feel about the journey / process 8 | - Understand how dept admin users feel about the process 9 | - Identify any barriers to adoption of GOV.UK Forms through an ‘early access’ model 10 | 11 | ## Users 12 | - Civil Servants 13 | - 6 users 14 | 15 | ## Methodology 16 | - Usability Testing 17 | 18 | ## Key Headlines 19 | 20 | - Participants were clear about the journey from trial account to editors, and were keen to explore the tool for their uses. 21 | - Some were less clear on whether they met the requirements, particularly around the type of organisation and whether that organisation is a partner. 22 | - Each stage of the process was clear, but participants had a need to understand the whole process and how it would play out for them. 23 | - We identified a number of specific and detailed issues to consider in the content of the journey. 24 | 25 | ## Supporting Evidence 26 | - [Report](https://docs.google.com/presentation/d/1Sd4y8xXPDyxw_yThsA5qNmatAqjb-rpYvctYMflgCJQ/edit#slide=id.g283a4c56425_1_44) 27 | - [Playback](https://drive.google.com/file/d/1-bNkAAKJ3GMs1m7OM4ubdfbdalqKNf7l/view?usp=drive_link) 28 | - [Additional documents](https://drive.google.com/drive/folders/1uevHf30gL8TlbeeRK1O3RvOhMUQURHwQ) 29 | -------------------------------------------------------------------------------- /research/2023-09-26-Form_Completers_Accessibility.md: -------------------------------------------------------------------------------- 1 | # Accessibility testing: Form Completers 2 | 3 | 2023-09-26 / Sprint 35 4 | 5 | ## Aims 6 | - To observe and draw insights from the experiences of ‘Form Completers’ with access needs 7 | 8 | ## Users 9 | - Members of the public with access needs 10 | - 6 users 11 | 12 | ## Methodology 13 | - Usability Testing (Accessibility focus) 14 | 15 | ## Key Headlines 16 | 17 | - There was lots of positive feedback on how online forms help people with access needs complete forms. 18 | - We identified some specific areas to consider around the design of forms and the potential to get help on the ‘Check your answers’ page. 19 | - Whilst GOV.UK Forms does a lot to improve accessibility, this work highlighted that content in questions and guidance is also an important factor in how accessible a form is. 20 | 21 | ## Supporting Evidence 22 | - [Report](https://docs.google.com/presentation/d/1dNlpWRCAley_J9sPIsVY-6kYlozgUYe-Umn4Ecmoiz4/edit) 23 | - [Playback](https://drive.google.com/file/d/1TocDUiJ88K3NcgQQcaDGImtmOtSyOKVL/view) 24 | - [Additional documents](https://drive.google.com/drive/folders/1n9kfxDn5UWnG3xsObh997D1yoYEHM796) 25 | -------------------------------------------------------------------------------- /research/2023-10-11-Data_And_Analytics.md: -------------------------------------------------------------------------------- 1 | # Data and Analytics 2 | 3 | 2023-10-11 / Sprint 38 4 | 5 | ## Aims 6 | - Understand the needs and capabilities of our existing partners for using data and analytics 7 | - Understand how partners are using the analytics provided to them so far 8 | 9 | ## Users 10 | - Civil Servants 11 | - 6 users 12 | 13 | ## Methodology 14 | - Interviews 15 | 16 | ## Key Headlines 17 | 18 | - The data is being used at two different levels 19 | - First a very general check, which our planned MVP would support 20 | - Second as a guide to problems with specific questions, which it would not. 21 | - None of the participants were manipulating the data and few were using it to report to others. 22 | - Generally people were happy with the format of the data as a spreadsheet attached to an email. One person suggested the spreadsheet could contain data from multiple forms for comparison. 23 | - It seems most people using this data do not see themselves as particularly capable with using data. There is a need to make the data clear and help them confidently understand what implications to draw from it. 24 | 25 | ## Supporting Evidence 26 | - [Report](https://docs.google.com/presentation/d/1652cpRz963L3nWHxn1dhlV2WrPJM4g4VnBx4RQhjv_s/edit?usp=drive_link) 27 | - [Playback](https://drive.google.com/file/d/1cKwbV6u9iV3EecFvHIfjsbYcBgHdDC6x/view?usp=drive_link) 28 | - [Additional files](https://drive.google.com/drive/folders/1u3x3Sc7Gk6WSx3BbVxiu5TyUakuRwoKS) -------------------------------------------------------------------------------- /research/2023-11-10-Confirmation_Emails.md: -------------------------------------------------------------------------------- 1 | # Usability testing: Confirmation emails 2 | 3 | 2023-11-10 / Sprint 40 4 | 5 | ## Aims 6 | - Understand the needs of form creators to provide information to form fillers after submission. 7 | - Test the usability of content on confirmation emails as part of the form building journey. 8 | - Understand the needs of form processors for information provided to form completers after submitting a form. 9 | 10 | ## Users 11 | - Civil Servants 12 | - 8 users 13 | 14 | ## Methodology 15 | - Usability Testing and Interview 16 | 17 | ## Key Headlines 18 | 19 | - The current design for confirmation emails was welcomed by users. It might not fully meet all of their particular needs, but no issues were identified with implementing it. 20 | - However, the current design left everyone we tested with unaware that the feature existed. When their attention was drawn to the content they clearly understood the feature. So the issue was awareness so they can write ‘what happens next’ content knowing it will be in this email. 21 | - Being able to provide detailed information both in ‘what happens next’ and the emails was identified as a need. Currently users feel held back by not being able to add formatting or hyperlinks to their content. 22 | - Including submitted answers in the confirmation emails was largely seen as a ‘nice to have’. We know this is essential for one service we are working with. We should do more work to understand how common this is. 23 | - There were some related insights around agents submitting forms and other specific needs for confirmation emails. 24 | 25 | ## Supporting Evidence 26 | - [Report](https://docs.google.com/presentation/d/1652cpRz963L3nWHxn1dhlV2WrPJM4g4VnBx4RQhjv_s/edit?usp=drive_link) 27 | - [Playback](https://drive.google.com/file/d/1RqPKscFAwqJ8YzqoHMwSuUxPugyzBEbe/view?usp=drive_link) 28 | - [Folder](https://drive.google.com/drive/folders/1DiWgtUJ_4pnJDXCYXeZgSqWvMHJHOvbd) 29 | -------------------------------------------------------------------------------- /research/2023-11-17-Accessibility_Testing_Detailed_Guidance_and_Routing.md: -------------------------------------------------------------------------------- 1 | # Accessibility testing: ‘Detailed Guidance’ and ‘Simple Routing’ 2 | 3 | 2023-11-17 / Sprint 41 4 | 5 | ## Aims 6 | Test the usability of the form builder for people with access needs, with a particular focus on: 7 | - Creating ‘detailed guidance’ 8 | - Adding a question route 9 | 10 | ## Users 11 | - Members of the public with access needs 12 | - 6 users 13 | 14 | ## Methodology 15 | - Usability Testing (Accessibility) 16 | 17 | ## Key Headlines 18 | 19 | - The ‘add a question route’ journey was accessible and straightforward for users. 20 | - Most users successfully added detailed guidance, using a combination of the buttons, typing input based on ‘formatting help’, and checking using the preview. 21 | - The ‘detailed guidance’ formatting buttons did not work well for screen reader users. But the guidance and typed markdown did. 22 | - Previewing formatted guidance poses some challenges for screen reader users. 23 | - There were a range of quite specific issues identified for us to look into further. These were mostly issues for screen reader users. 24 | - Most of our users successfully created a form with guidance and routing. This included people using significant assistive technology, including one person using an iPhone entirely interacting with VoiceOver. 25 | 26 | ## Supporting Evidence 27 | - [Report](https://docs.google.com/presentation/d/1D94iHQboSsif6MzR5zA8TB4sqNqlBHMa1bzvm_930xU/edit#slide=id.g298f9251a71_0_48) 28 | - [Playback](https://drive.google.com/file/d/1XMfALQCKw2HtZV6U2W51dot_u6926w_f/view) 29 | - [Additional files](https://drive.google.com/drive/folders/1dRu8nKqP13gDyFSfwZ_yi_oYHORMs6h3) 30 | -------------------------------------------------------------------------------- /research/2023-11-20-Barriers_to_adoption_research.md: -------------------------------------------------------------------------------- 1 | # Barriers to adoption 2 | 3 | ## Key Headlines 4 | 5 | - User research is a priority for several teams. In some cases there may be obstacles that delay the form creation process. 6 | - We uncovered recurring concerns and needs from DDaT users in content teams: 7 | - Content teams are worried that non DDaT users will create forms that are poorly designed or have not undergone GDPR checks. 8 | - Content teams would like visibility over who has an account within their department. 9 | - Content teams would like to manage accounts within their department. 10 | - Content teams would like to be involved from the beginning of the form creation process. 11 | 12 | ## Supporting Evidence 13 | - [Report](https://docs.google.com/presentation/d/1PH6eGfiu83nJvuzgpBmZHBNhQ4OfCqQcJKVASSYxLFQ/edit#slide=id.g29d073d7671_0_72) 14 | - [Playback](https://drive.google.com/file/d/1N1rZdC1WO9HOaYA52p0r4epW0HZHePeF/view?usp=sharing) 15 | - [Additional Files](https://drive.google.com/drive/folders/1g6KGqkffUg1iHyyndgaySdTlm__wtTgm?usp=drive_link) 16 | -------------------------------------------------------------------------------- /research/2024-04-15_Usability_Testing_User_Management: -------------------------------------------------------------------------------- 1 | # Usability testing: User management 2 | 3 | ## 2024-04-16 / Sprints 49 to 50 4 | 5 | ## Aims 6 | Test user management designs with various users: 7 | - Do users understand the model for managing users, groups and forms? 8 | - Does the interface clearly communicate this model to them? 9 | - Does the model meet their needs for managing users and forms? 10 | 11 | ## Users 12 | - Civil servants 13 | - 6 organisation admins, 2 group admins 14 | 15 | ## Methodology 16 | - Usability testing 17 | 18 | ## Key findings 19 | - The model came across clearly to participants from using and exploring the tool. 20 | - Most of their assumptions were correct, and the only areas of ambiguity were about very specific details. 21 | - Few participants saw people outside user-centred design (UCD) roles creating forms. Central UCD teams want to have control of form creation from the start - this is to ensure that only forms that are fit for purpose and high quality are created and made live. 22 | - People saw groups as mainly a way of organising forms in similar topic areas or categories. Permissions at group level were seen as secondary. 23 | - As people see groups as being useful mainly for organising forms, being able to reorganise them is important. That requires the ability to move items around the system. A desire to move forms between groups came up regularly. 24 | - Participants wanted control of publishing forms at form level, and the ability to run a 2i-style process around publishing a form. 25 | - There are differences in the mental models people had for how they want to organise and work with forms and how the features are implemented. 26 | - Participants were confident that the features could support them to work in the way they wanted to. However, in some cases this would require some thinking through in order to map their needs to the feature. 27 | 28 | ## Supporting evidence 29 | - [Report](https://docs.google.com/presentation/d/1_zEEa2xm1VU2ekWNPktspRpvi9rOEgYQSkzbOJ8hibs/) 30 | - [Playback](https://drive.google.com/file/d/1Iazd_x0sdwYnFRtR9FGd4mrVbNeJBFge/view?usp=drive_link) 31 | - [Further documentation](https://drive.google.com/drive/folders/16430JQKnHiLmRSx_uI-_a6RpKDkVqDNk) 32 | -------------------------------------------------------------------------------- /research/2024-06-18-concept_testing_add_another_answer.md: -------------------------------------------------------------------------------- 1 | # Concept testing: Add another answer 2 | 3 | ## 2024-06-18 / Sprint 55 to 56 4 | 5 | ## Aims 6 | - Test 2 concepts for helping people build a question that allows form fillers to add more answers. 7 | 8 | - Do these early concepts make sense to users? 9 | - Which concept seems to fit better with the users’ mental models? 10 | - What language do users use in relation to this type of feature/question? 11 | 12 | ## Users 13 | - GOV.UK Forms users (civil servants) 14 | - 5 participants 15 | 16 | ## Methodology 17 | - Concept testing 18 | 19 | ## Key Headlines 20 | ### Concept 1: 21 | - users broadly understood the new page of options. 22 | - one wrong choice but the correct result 23 | - overall more positive feedback for this design 24 | - not strong evidence that the extra page was a burden - however this wasn't a normal workflow. 25 | 26 | ### Concept 2: 27 | - there was a fair amount of confusion and error 28 | - some wrong choices with the correct result 29 | 30 | HOWEVER, 3 out of 5 users were primed by v2 before they saw v1, which could have influenced v1's success by priming. Still, the evidence clearly showed v2 was not easy to use anyway. 31 | 32 | There's a strong mental model that after creating set, you will edit all the questions 'together'. 33 | 34 | Preview was very important to participants - especially at individual question level, rather than whole form level. 35 | 36 | ‘Check your question’ and ‘edit your set’ pages were valuable validation points for people. 37 | 38 | Some confusion, error and overlooking of links and buttons on these pages when saving and adding questions, and when wanting to navigate elsewhere. 39 | 40 | People understood the use of minimum and maximum number of answers. They even used both min and max when they had chosen the ‘wrong’ thing (set etc), to force it to work how they needed. 41 | 42 | We heard more than once that it would be easier for form fillers to have the questions relating to one item (data row) on one page. 43 | 44 | All the participants showed familiarity with the concept of this type of question, all used the phrase ‘add another’ in relation to this question model. 45 | 46 | ## Supporting Evidence 47 | - [Report](https://docs.google.com/presentation/d/13LAMIzFq6-cn6AKDLYgoyGYy_N8BW036eoTHLo8McUg/edit#slide=id.g10d42026b8_2_0) 48 | - [Playback](https://drive.google.com/file/d/1iHooUhvaFx5z0pJUU1AjbSFMDJ07ZHvE/view?usp=drive_link) 49 | - [Further documentation](https://drive.google.com/drive/folders/1zMaTy5GgWhsDdZ8-uUciCkSUdCddEyAf) -------------------------------------------------------------------------------- /research/2024-08-28-Add-another-answer-round-2.md: -------------------------------------------------------------------------------- 1 | # Add another answer round 2 - usability testing 2 | 3 | ## 2024-08-28 / Sprint 2 4 | 5 | ## Aims 6 | - Usability test the MVP for single repeated questions. 7 | 8 | - Learn more about what works for people when building multiple repeated questions. 9 | 10 | - We tried out 3 different entry points for building multiple repeated questions as well as 2 different ways of actually building them. 11 | 12 | 13 | ## Users 14 | - GOV.UK Forms users (civil servants) 15 | - 5 16 | 17 | ## Methodology 18 | - interview 19 | - usability testing of prototype 20 | - usability/cognitive walkthrough of Mural designs 21 | 22 | ## Key Headlines 23 | - The MVP tested quite well but users need help understanding how to write the repeated questions to make it clear that users can add another answer. 24 | - People didn't notice the maximum number of repeated answers. 25 | - People questioned the need for a maximum and stated that any maximum would need to be much higher. 26 | - The format of the MVP email seemed unproblematic - but these are not the real users, so recommend checking with actual data processors. 27 | - The routing 'model' for building multiple repeated questions did not test well. Only one user (n=5) worked out how to do it and they said it was only due to test expectations. They also didn't find the process or the language logical. 28 | - The 'add a question set' button was only discussed - it seemed reasonably clear to users, but with no confident consensus as to its purpose. Users would need to try it out. 29 | - The radio option on the 'answer type' page worked well and users were confident that it would be what they needed to do. It helped to steer them through the journey. 30 | - The iterated journey for building multiple repeated questions worked better than the previous concept, but some users still found it confusing - although all users managed to get it right in the end. 31 | - In particular, they didn't understand what 'set name' to give their set, and how the structure of set name and questions worked. 32 | - Three of the five were clear on how to finish building a set by editing their questions, however two found it confusing. 33 | - One didn't notice the 'Edit' links at all, and several were confused by the wording of the links. 34 | 35 | ## Supporting Evidence 36 | - [Report](https://docs.google.com/presentation/d/14z8RLSljza-V5-gYJvDMgc6SxWI7j25Vi6RBvejADEg/edit#slide=id.g10d42026b8_2_0) 37 | - [Playback](https://drive.google.com/file/d/1pENCW6Gb_8o7eBKMuu_HRO5SH7utVoNx/view?usp=drive_link) 38 | - [Further documentation](https://drive.google.com/drive/folders/1XjD2G3mJXBe2S0e0SUK0X2M2BTk7_n_Q) -------------------------------------------------------------------------------- /research/2024-12-23-Support_Model.md: -------------------------------------------------------------------------------- 1 | # Support Model User Research 2 | 3 | ## 2024-12-23 / Sprint 43 4 | 5 | ## Aims 6 | - Understand needs for support of existing and potential future forms 7 | - Understand user expectations in terms of service level and support 8 | - Identify any areas where service level or support may present barriers to adoption 9 | 10 | ## Users 11 | - Civil Servants 12 | - 4 users 13 | 14 | ## Methodology 15 | - Interviews / Review of support tickets 16 | 17 | ## Key Headlines 18 | 19 | - Only 4% of support tickets were related to user issues. 20 | - Interviews confirm that people see Forms as reliable and low risk. 21 | - 25% of tickets were requests for information on the product, often information that is already available somewhere. 22 | - Users have expectations of support related to their experience of other GDS products and GOV.UK. They expect quick initial responses, but understand fixes to issues may take several days. 23 | - They want clear information so they can take action their side, such as updating landing pages or putting in place mitigations. 24 | - Directing form completers to the appropriate action or alternative contacts is the action participants saw as most pressing. We could consider how we make sure contact details are available in case of any downtime or errors. 25 | - Issues with the runner are likely higher priority than the admin, but there are some situations where urgent admin access would be needed to correct errors or launch new time sensitive forms. 26 | 27 | ## Supporting Evidence 28 | - [Report](https://docs.google.com/presentation/d/1ZH3PALkYQ0CR2VODJziOAAjSf3tBjcwYVwE2Am7QUNk/edit) 29 | - [Playback](https://drive.google.com/drive/folders/12vJsl6M5gaMg6-IJRqw7EU01igJhE2-C) 30 | - [Other files](https://drive.google.com/drive/folders/1lN87Pm5HI0y0J2YulG63tMfRjkyBkJog) 31 | -------------------------------------------------------------------------------- /research/2024-2-21-Add_a_Payment_Link.md: -------------------------------------------------------------------------------- 1 | # Usability testing: Add a payment link 2 | 3 | 2024-02-21 / Sprint 47 4 | 5 | ## Aims 6 | - Explore participants’ understanding of the payment link process acquired from three options for content on the payment link page. 7 | - Understand the amount of content and context that users need to have a good understanding of the payment link feature 8 | 9 | ## Users 10 | - Civil Servants 11 | - 4 users 12 | 13 | ## Methodology 14 | - Usability testing 15 | 16 | ## Key Headlines 17 | 18 | - The initial version of the feature was comprehensible to users and they appeared able to set up payment links in the Forms interface. 19 | - Users anticipate a time consuming process to get set up to use GOV.UK Pay involving others in their organisation such as finance colleagues. 20 | - The long version of the content gave users the clearest understanding of the feature. 21 | - We identified a number of areas to iterate the content to improve the understanding of the feature. 22 | - Participants were happy to use the feature, with the caveat that they would need to get sign off and processes in place to use GOV.UK Pay. 23 | - There is a need for more guidance on how to set up GOV.UK Pay to accept a GOV.UK Forms generated reference number 24 | 25 | ## Supporting Evidence 26 | - [Report](https://docs.google.com/presentation/d/1oTOkZVe8XtLRk7jOQczT0yg1uLXr0-phWsTHKh248pE/edit?usp=sharing) 27 | - [Playback](https://drive.google.com/file/d/16n1gwHR0Y3eBX8Us2exhM2nIOuEX6vEk/view?usp=drive_link) 28 | - [Other files](https://drive.google.com/drive/folders/1RG7680AO1FZActFefA5uryzWJZyEZbz2) -------------------------------------------------------------------------------- /research/2025-02-03-Branching_feedback_round_1.md: -------------------------------------------------------------------------------- 1 | # Branching feedback round 1 2 | 3 | ## 2025-02-03 / Sprint 13 4 | 5 | ## Aims 6 | - The feedback rounds were planned as intermediary research where we could understand from a small group of users whether our design changes were heading in the right direction before carrying out more time-consuming, rigorous research. Recruitment and methodolgy did not follow the usual rigorous processes and were intended more as light touch checkins. 7 | 8 | **They were not designed or planned as rigorous investigations, and therefore the findings and data should be treated with caution.** 9 | 10 | The aim was to understand whether the first part of of our recent iterations in response to the latest usability testing of branching were heading in the right direction: 11 | * Is it easier for users to find where to do branching? 12 | * Is it easier for users to understand how routing works? 13 | * Is it easier for user to understand how to build 2 routes? 14 | 15 | ## Participants 16 | - Civil servants - existing users (mostly beginners) 17 | - 4 participants 18 | 19 | ## Methodology 20 | - Informal observations of 2 users (like UR but not formalised) 21 | - Access given to 7 users, of whom 2 who gave feedback at the end of a week. 22 | 23 | ## Key Headlines 24 | - ‘Changes to ”Add a route to a question”’ have made it easier for users to select the question to set the 2nd route. 25 | 26 | - Users find it hard to select questions to understand and set the 2nd route, however for the feedback sessions, we hadn't implemented all the improvements around this. 27 | 28 | - Team decisions: 29 | 1) Change wording from take to to skip (before next round of testing) 30 | 2) Think how to help creators choose the questions in the ""Route 2: set questions to skip page"" (if possible, have something to show for next round of testing)" 31 | 32 | ## Supporting Evidence 33 | - [Mural with all notes](https://app.mural.co/t/gaap0347/m/gaap0347/1738940940485/034a18851b5c49ab12351bfbde86ab1538d5f380?wid=0-1737728768635) 34 | - [Playback](https://drive.google.com/file/d/19AhkZNGs0KCGpM4gbodjmv7uflydeUk_/view?usp=drive_link) 35 | - [Summary of two calls where users were observed](https://docs.google.com/document/d/1XCyCtRAzAwhKfpYFPdq6f-2f6fSRMWwltwXzVDVeKTc/edit?usp=drive_link) 36 | -------------------------------------------------------------------------------- /research/EPIC B MANAGING TWO VERSIONS OF THE SAME FORM.md: -------------------------------------------------------------------------------- 1 | # Epic B: Managing two versions of the same form 2 | 3 | - Managing two versions of the same form is not a widespread issue. Larger (high volume) teams are generally well-oiled machines with systems and processes in place that allow this to be managed seamlessly. 4 | - In smaller teams, where there are less processes and resources, it can be more challenging, and the burden can fall on one person. However, in these situations many prioritise online forms and only make changes to paper forms on a case-by-case basis 5 | - The biggest potential challenge our primary intended users would likely face would be the transition from a paper to digital mindset when it comes to creating and editing HTML forms. To help users with this we should provide GDS style guides and help sections/ videos to encourage positive form design. 6 | - There are some positive examples where HTML forms have been readily adopted. However, in these examples HTML has overtaken paper almost entirely and they are not managed side by side. 7 | - Version control is an issue in some departments and users may benefit from a way of managing this in a an easier way, enabling them to feel more in control and organised. Likewise, a print feature was highlighted as a useful feature and would enable the creation of two versions of the same form 8 | 9 | https://docs.google.com/presentation/d/1_b7p6RfnEy10sa2NYD9-QYaicZaZmuGW/edit?usp=sharing&ouid=116661804351516042654&rtpof=true&sd=true 10 | -------------------------------------------------------------------------------- /research/EPIC-6-HOW TO HELP USERS WHEN THEY CREATE BAD FORMS.md.md: -------------------------------------------------------------------------------- 1 | # Epic 6: Who will help users when they create bad forms? 2 | 3 | - Publishers are the most appropriate group to help assure forms. They are more engaged than Digital Assurance Managers and have the required skillset 4 | - Digital Assurance Manages are not the right audience to bring into the process for several reasons but predominately because they do not have the remit or capability set to assure forms. Their role is confined to Service Assessments only and often struggle to think outside this framework 5 | - Publishers claim they would benefit greatly from an email notification with form performance analytics, and this would prompt positive action 6 | - However, there are question marks over who will help the very small departments who have no resources or ‘parent’ organisation to call upon. Could other department Service Teams help? 7 | - Participants identified 4 solutions to the problem: a self assessment Q&A form which would help users identify and solve problems, a check point template for pre/ post feedback, guidance on good form design (which could be assessed), and a slimmed down, one-hour Service Assessment (for forms only) 8 | 9 | https://docs.google.com/presentation/d/1PLdboUsHKD41uJ36ZKRdOQ6RhAOJcI29/edit?usp=sharing&ouid=116661804351516042654&rtpof=true&sd=true 10 | -------------------------------------------------------------------------------- /research/YYYY-MM-DD-template.md: -------------------------------------------------------------------------------- 1 | # Title 2 | 3 | ## YYYY-MM-DD / Sprint N 4 | 5 | ## Aims 6 | - Aims here 7 | 8 | ## Participants 9 | - Type of participants 10 | - Number of participants 11 | 12 | ## Methodology 13 | - Research methods used 14 | 15 | ## Key Headlines 16 | - Key 17 | - Takaways 18 | - Here 19 | 20 | ## Supporting Evidence 21 | - [Report](URL) 22 | - [Playback](URL) 23 | - [Further documentation](URL) 24 | --------------------------------------------------------------------------------