Merge branch 'main' into chore/add-identity-1.4

iotaledger · Sep 24, 2024 · 16dcd39 · 16dcd39
2 parents 306d92b + 9bfccbe
commit 16dcd39
Show file tree

Hide file tree

Showing 22 changed files with 46 additions and 7,710 deletions.
diff --git a/config/articleRedirects.js b/config/articleRedirects.js
@@ -588,7 +588,7 @@ exports.articleRedirects = [
   },
   {
     from: '/identity.rs/libraries/wasm/api_reference/',
-    to: '/identity.rs/references/api/wasm/',
+    to: '/identity.rs/references/wasm/api_ref',
   },
   {
     from: '/identity.rs/libraries/wasm/getting_started/',

diff --git a/docs/build/identity.rs/1.3/docs/explanations/verifiable-presentations.mdx b/docs/build/identity.rs/1.3/docs/explanations/verifiable-presentations.mdx
@@ -1,7 +1,7 @@
 # Verifiable Presentations
 
 A verifiable presentation is the recommended data format for sharing one or more [verifiable credentials](./verifiable-credentials.mdx).
-It is constructed and signed by a holder to prove control over their credentials and can be presented to a verifier for [validation](#validation).
+It is constructed and signed by a holder to prove control over their credentials and can be presented to a verifier for validation.
 
 For instance, after an issuer [creates and issues](./../how-tos/verifiable-credentials/create.mdx) a [verifiable credential](./verifiable-credentials.mdx) to a holder, such as a university issuing a degree to a graduate,
 the holder stores it securely until asked to present it.

diff --git a/docs/build/identity.rs/1.3/docs/getting-started/wasm.mdx b/docs/build/identity.rs/1.3/docs/getting-started/wasm.mdx
@@ -334,6 +334,6 @@ You may find it useful to see how the WASM bindings are being used in existing a
 
 - [Zebra IOTA Edge SDK](https://github.com/ZebraDevs/Zebra-Iota-Edge-SDK) (mobile apps using Capacitor.js + Svelte)
 
-## [API Reference](../references/api/wasm.mdx)
+## [API Reference](../references/wasm/api_ref.md)
 
 ## [Examples](https://github.com/iotaledger/identity.rs/blob/v1.3.0/bindings/wasm/examples/README.md)
diff --git a/docs/build/identity.rs/1.3/docs/how-tos/decentralized-identifiers/resolve.mdx b/docs/build/identity.rs/1.3/docs/how-tos/decentralized-identifiers/resolve.mdx
@@ -187,7 +187,7 @@ resolve the DID Documents of the [verifiable credential](./../../explanations/ve
 and presentation holder to verify their signatures.
 
 Resolving the necessary DID Documents is
-[performed automatically when verifying presentations via the `Resolver`](../verifiable-presentations/create-and-validate.mdx#example)
+[performed automatically when verifying presentations via the `Resolver`](../verifiable-presentations/create-and-validate.mdx#example-code)
 
 When direct access to these DID Documents is desired, the `Resolver` also provides standalone methods to:
 

diff --git a/docs/build/identity.rs/1.3/docs/how-tos/decentralized-identifiers/update.mdx b/docs/build/identity.rs/1.3/docs/how-tos/decentralized-identifiers/update.mdx
@@ -21,7 +21,7 @@ while a service can provide metadata around the identity via URIs.
 
 ## Verification Methods
 
-As demonstrated by the [example](#example) below, the IOTA Identity framework offers easy-to-use methods for adding
+As demonstrated by the [example](#full-example-code) below, the IOTA Identity framework offers easy-to-use methods for adding
 [verification methods](https://www.w3.org/TR/did-core/#verification-methods).
 
 ### Properties

diff --git a/docs/build/identity.rs/1.3/docs/how-tos/verifiable-credentials/create.mdx b/docs/build/identity.rs/1.3/docs/how-tos/verifiable-credentials/create.mdx
@@ -39,7 +39,7 @@ In the IOTA Identity Framework, you can create a Verifiable Credential with the
 
 
 
-## Signing {#signing}
+## Signing
 
 After preparing the verifiable credential, the issuer creates a signed JWT containing VC in the claims using one of their private keys. This is what allows verifiers to validate the credential independently using the corresponding public key from the issuer's DID Document.
 
@@ -71,7 +71,7 @@ and for enforcing [subject-holder relationships](https://www.w3.org/TR/vc-data-m
 
 ## Example
 
-The following code showcases how an issuer can [create, sign](#create-and-sign-vc),
+The following code showcases how an issuer can [create, sign](#create-and-sign-a-vc),
 and [validate](#validate-a-vc) a verifiable credential.
 In this example, the issuer signs a `UniversityDegreeCredential` with Alice's name and DID.
 

diff --git a/docs/build/identity.rs/1.3/docs/how-tos/verifiable-credentials/revocation.mdx b/docs/build/identity.rs/1.3/docs/how-tos/verifiable-credentials/revocation.mdx
@@ -14,7 +14,7 @@ import TabItem from '@theme/TabItem';
 
 # Revoke a Verifiable Credential
 
-The [example](#example) below demonstrates two methods that an issuer can use to revoke a verifiable credential
+The [example](#full-example-code) below demonstrates two methods that an issuer can use to revoke a verifiable credential
 using the IOTA Identity Framework:
 
 1. By using the [`credentialStatus`](https://www.w3.org/TR/vc-data-model/#status) field in a credential and linking

diff --git a/docs/build/identity.rs/1.3/docs/references/.gitignore b/docs/build/identity.rs/1.3/docs/references/.gitignore
@@ -0,0 +1 @@
+wasm