Develop Guardian UI components library

[anvabr]

Problem description

Currently Guaridan UI is built using a mixture of 'vanilla' 3rd party components such as PrimeNG and Material. #3141 addresses some of the issues affecting Guardian core team connected to this, namely complex maintenance and challenging extendability of the UI, by standardising the entire UI on a single platform.

However to enable more developers, especially those outside of the core team, to directly contribute features and enhancements, as well as to enabled 3rd party teams to easily switch look&feel of Guardian and to increase the speed of internal development it would be useful to have an 'official' Guardian component library.

Requirements

Design and develop Guardian component library which would be:

• tailored to specific use-case of Guardian, i.e. environmental sustainability and impact accountability
• optimised for the specific tasks users perform in Guardian User Interface (UI) such as data submission (forms), document management - approvals, etc
• providing a good User Experience (UX) for dealing with the fundamental concepts of Guardian operation such as:
  • Decentralised Identity Documents (DIDs)
  • Verifiable Credentials (VCs) and related concepts
  • Hedera transactions, tokens, topics, messages, memo fields - their content, IDs and data formats
  • Interplanetary File System (IPFS) storage

The components library needs to be whitelabel-able with limited required effort.

Definition of done

• Code and a corresponding Figma component library is available for Guardian community
• Documentation with examples is published

Acceptance criteria

3rd party and core developers have the means to construct new UI pages using Guardian component libraries.