Consider feedback from Nexera developer

[erasmus]

From Slack.

• it took me some time to realize there is a difference between identites and verifialbe-credentials, but it makes total sense once i realized that

• I really like the glossary https://developer.concordium.software/en/mainnet/net/resources/glossary.html#term-Account-credential but sometimes I thought I’d click on a link with more examples / elaboration but was just pointed to the glossary screen

• https://developer.concordium.software/en/mainnet/net/web3-id/issuer.html#concordium-issuer-tool you mention issuer tool, but there is no direct link to it to the github

• https://developer.concordium.software/en/mainnet/net/guides/create-proofs.html#:~:text=You%20can%20find%20more%20information%20about%20building%20proof%20statements%20in%20the%20Concordium%20node%20SDK%20js%20repository. leads to a 404

• no code examples for how the data reveal in case of compliance request would work

• here is a flow mentioned https://developer.concordium.software/en/mainnet/net/concepts/id-accounts.html#disclosing-an-identity

• https://developer.concordium.software/en/mainnet/net/web3-id/index.html might make sense to split ID layer into 2 sections?

• identity-providers

• verifiable-credential-issuers

• After our calls and some research i realised these are 2 different entities… which can be issued by same company (or not)… but they work a bit differently and probably have different tech assumptions under the hood

• currently ID layer is more refering to the VCs than Identity themselves… so maybe a section for IDPs specifically would be nice to have