Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design a first version default template for our new App receipt #769

Open
12 tasks
Febakke opened this issue Dec 21, 2022 · 0 comments
Open
12 tasks

Design a first version default template for our new App receipt #769

Febakke opened this issue Dec 21, 2022 · 0 comments
Assignees
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

Comments

@Febakke
Copy link
Member

Febakke commented Dec 21, 2022

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"
Skjermbilde 2022-12-21 kl  12 54 08

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

  • What elements should be / or must be a part of our new template
    • "Kvittering" Header
    • <h2> header
    • Metadata table
    • Link to archive
    • Standard description text
    • "The following is sent in" and pdf
    • Attachments
  • Create a new design based on our app components
  • Define what components that should be available for the app developer
  • Create standard text for the template
  • Create Guidelines/tips on how to build their receipt page

Acceptance Criterias

@Febakke Febakke added 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 area/receipt labels Dec 21, 2022
@Febakke Febakke self-assigned this Jan 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
Status: Todo 📈
Status: No status
Development

No branches or pull requests

1 participant