Update and Enhance "Prototyping with Figma" Guide on Altinn Studio Documentation

[olavflar]

Description

Last update Altinn Studio Komponenter V 2.1 - Release 21.05.24

The "Prototyping with Figma" guide on the Altinn Studio documentation site (https://docs.altinn.studio/altinn-studio/guides/design/prototype/) serves as an essential resource for developers and designers who utilize Altinn Studio for creating prototypes. To ensure this guide remains up-to-date and maximally beneficial, we are proposing enhancements that reflect recent updates to our Figma components.

The Figma file for Altinn Studio components has been updated. This update includes new components and patterns that can significantly aid our users in creating more accurate and effective prototypes. The updated Figma file is available here: Altinn Studio Components in Figma

*Update Guide Content:** Revise the guide to include references and examples using the latest components from the updated Figma file. This ensures that users have the most current information and can leverage the full capabilities of our design system.

Add New Sections: Introduce new sections or subsections that specifically address how to use the newly added components within the Figma file. Each section should include practical examples and best practices for integration into prototypes.

Improve Navigation and Usability: Enhance Altinn.docs Delete duplicates of components on the documentation.

Conclusion

By updating the "Prototyping with Figma" guide to reflect the latest changes and enhancements in our Figma components, we can provide a more valuable resource to our community. These improvements aim to foster a more intuitive and efficient design process, enabling creators to build more effective and user-friendly prototypes. We invite the community's feedback on these proposals to ensure the guide meets our users' evolving needs.

---

This issue draft is structured to clearly identify the need for updates based on the Figma file changes, outline specific improvements, and invite community engagement for further enhancement.

### My tasks
- [x] Update examples and prototypekit and guide
- [x] Delete duplicates of components and clean up the docs
- [x] Update mobile components

### Update new components
- [ ] Datepicker
- [ ] Sub-form
- [ ] Summary 2.0
- [ ] Navigation
- [ ] Sign - delegate task
- [ ] PDF
- [ ] Tabs
- [ ] Card

[nkylstad]

@olavflar This issue is marked as "Done" in your project, can it be closed? If not, it should be moved to the docs repo.

[olavflar]

@olavflar This issue is marked as "Done" in your project, can it be closed? If not, it should be moved to the docs repo.

This issue is a work in progress, so we should move it to the docs repo, and update every time we publish a new component

[olavflar]

@olavflar This issue is marked as "Done" in your project, can it be closed? If not, it should be moved to the docs repo.

Do you have a link to the docs repo board?

[nkylstad]

@olavflar There is no board for docs as far as I know, we add issues relevant to us to our team boards.