Design a first version default template for our new App receipt #769
Labels
area/receipt
kind/user-story
Used for issues that describes functionality for our users.
status/draft
Status: When you create an issue before you have enough info to properly describe the issue.
ux
Needs some love from a UX resource
Description
As our receipt will use the same front-end components as the rest of our apps we need a design that will support this. This means that we must be able to build the template with the same components that we use to build any other page in our apps. This will make it much easier for our app-developers to edit this page.
This is the app receipt. The green page that the user sees after they press "send in"
Related to #739
NB: The changes to this solution will not change the platform receipt. This is the receipt that is available for the user in their Altinn Archive after an instance is finished.
Additional Information
KS Plain language guide on Receipt
Gov.uk Confirmation page
Tasks
<h2>
headerAcceptance Criterias
The text was updated successfully, but these errors were encountered: