Unify tabs configuration

iotaledger · Jul 11, 2023 · 8b0f0a3 · 8b0f0a3
1 parent 24c7877
commit 8b0f0a3
Show file tree

Hide file tree

Showing 213 changed files with 909 additions and 1,448 deletions.
diff --git a/common/community/contribute-to-wiki/reference/structure/how_tos.md b/common/community/contribute-to-wiki/reference/structure/how_tos.md
@@ -34,11 +34,11 @@ snippets), while keeping the language agnostic instructions outside the tabs.
 
 #### Tabs Example
 
-<Tabs groupId="language">
+<Tabs groupId="language" queryString>
   <TabItem value="java" label="Java">
     Java specific code and text goes here.
   </TabItem>
-  <TabItem value="nodejs" label="Nodejs">
+  <TabItem value="node" label="Node.js">
     Nodejs specific code and text goes here.
   </TabItem>
 </Tabs>

diff --git a/iota/docs/identity.rs/v0.5.0/docs/concepts/advanced/storage_interface.mdx b/iota/docs/identity.rs/v0.5.0/docs/concepts/advanced/storage_interface.mdx
@@ -122,22 +122,15 @@ This test suite is available in newer versions of the framework, but not yet in
 
 This section shows the Rust and TypeScript `MemStore` implementations, which are thoroughly commented.
 
-<Tabs
-    groupId="programming-languages"
-    defaultValue="nodejs"
-    values={[
-        { label: "Node.js", value: "nodejs" },
-        { label: "Rust", value: "rust" }
-    ]}
->
-<TabItem value="nodejs">
+<Tabs groupId="language" queryString>
+<TabItem value="node" label="Node.js">
 
 ```ts reference
 https://github.com/iotaledger/identity.rs/tree/support/v0.5/bindings/wasm/examples-account/src/memory_storage.ts
 ```
 
 </TabItem>
-<TabItem value="rust">
+<TabItem value="rust" label="Rust">
 
 ```rust reference
 https://github.com/iotaledger/identity.rs/tree/support/v0.5/identity-account-storage/src/storage/memstore.rs

diff --git a/iota/docs/identity.rs/v0.5.0/docs/concepts/decentralized_identifiers/create.mdx b/iota/docs/identity.rs/v0.5.0/docs/concepts/decentralized_identifiers/create.mdx
@@ -30,22 +30,15 @@ Select your programming language of choice and press the green play button to ex
 
 :::
 
-<Tabs
-  groupId="programming-languages"
-  defaultValue="nodejs"
-  values={[
-    { label: "Node.js", value: "nodejs" },
-    { label: "Rust", value: "rust" }
-  ]}
->
-<TabItem value="nodejs">
+<Tabs groupId="language" queryString>
+<TabItem value="node" label="Node.js">
 
 ```ts reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/bindings/wasm/examples-account/src/create_did.ts
 ```
 
 </TabItem>
-<TabItem value="rust">
+<TabItem value="rust" label="Rust">
 
 ```rust reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/examples/account/create_did.rs

diff --git a/...s/identity.rs/v0.5.0/docs/concepts/decentralized_identifiers/private_tangle.mdx b/...s/identity.rs/v0.5.0/docs/concepts/decentralized_identifiers/private_tangle.mdx
@@ -27,22 +27,15 @@ https://github.com/iotaledger/identity.rs/tree/support/v0.5/examples/account/con
 
 ### Low-level API
 
-<Tabs
-    groupId="programming-languages"
-    defaultValue="nodejs"
-    values={[
-        { label: "Node.js", value: "nodejs" },
-        { label: "Rust", value: "rust" }
-    ]}
->
-<TabItem value="nodejs">
+<Tabs groupId="language" queryString>
+<TabItem value="node" label="Node.js">
 
 ```ts reference
 https://github.com/iotaledger/identity.rs/tree/support/v0.5/bindings/wasm/examples/src/private_tangle.js
 ```
 
 </TabItem>
-<TabItem value="rust">
+<TabItem value="rust" label="Rust">
 
 ```rust reference
 https://github.com/iotaledger/identity.rs/tree/support/v0.5/examples/low-level-api/private_tangle.rs

diff --git a/iota/docs/identity.rs/v0.5.0/docs/concepts/decentralized_identifiers/resolve.mdx b/iota/docs/identity.rs/v0.5.0/docs/concepts/decentralized_identifiers/resolve.mdx
@@ -24,8 +24,8 @@ the W3C specification.
 
 The following example demonstrates how to resolve the DID: "did:iota:H3C2AVvLMv6gmMNam3uVAjZpfkcJCwDwnZn6z3wXmqPV" from the `main` network.
 
-<Tabs>
-<TabItem value="Rust" label="Rust">
+<Tabs groupId="language" queryString>
+<TabItem value="rust" label="Rust">
 
 ```rust
 use identity::iota::Resolver;
@@ -62,8 +62,8 @@ the resolver needs to be configured to have a client capable of operating on sai
 
 The following example demonstrates how one can setup a `Resolver` with a given `client` and then attempt resolving a specified `did` which may be on any Tangle (public or private).
 
-<Tabs>
-<TabItem value="Rust" label="Rust">
+<Tabs groupId="language" queryString>
+<TabItem value="rust" label="Rust">
 
 ```rust
 use identity::iota::Resolver;
@@ -122,8 +122,8 @@ advanced use cases where more control is desired. To accommodate for such situat
 The fact that a DID Document [can be updated](./update.mdx) implies that the state of the DID Document can change over time, or in other words the result of resolving a DID
 also depends on when this operation was carried out. The `Resolver` provides a way to view the entire history of a DID Document (up to the time when the method is called).
 
-<Tabs>
-<TabItem value="Rust" label="Rust">
+<Tabs groupId="language" queryString>
+<TabItem value="rust" label="Rust">
 
 ```rust
 use identity::iota::Resolver;
@@ -158,22 +158,15 @@ async function callResolveHistory(did) {
 
 This section shows complete examples from the Iota Identity Framework code base. The first example creates a DID Document, publishes it to the Tangle and then resolves it.
 
-<Tabs
-  groupId="programming-languages"
-  defaultValue="nodejs"
-  values={[
-    { label: "Node.js", value: "nodejs" },
-    { label: "Rust", value: "rust" }
-  ]}
->
-<TabItem value="nodejs">
+<Tabs groupId="language" queryString>
+<TabItem value="node" label="Node.js">
 
 ```ts reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/bindings/wasm/examples/src/resolve_did.js
 ```
 
 </TabItem>
-<TabItem value="rust">
+<TabItem value="rust" label="Rust">
 
 ```rust reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/examples/low-level-api/resolve_did.rs
@@ -184,22 +177,15 @@ https://github.com/iotaledger/identity.rs/blob/support/v0.5/examples/low-level-a
 
 This second example demonstrates creating, publishing changes and then resolving the history of a DID Document.
 
-<Tabs
-  groupId="programming-languages"
-  defaultValue="nodejs"
-  values={[
-    { label: "Node.js", value: "nodejs" },
-    { label: "Rust", value: "rust" }
-  ]}
->
-<TabItem value="nodejs">
+<Tabs groupId="language" queryString>
+<TabItem value="node" label="Node.js">
 
 ```ts reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/bindings/wasm/examples/src/resolve_history.js
 ```
 
 </TabItem>
-<TabItem value="rust">
+<TabItem value="rust" label="Rust">
 
 ```rushttps://github.com/iotaledger/identity.rs/blob/support/v0.5/examples/low-level-api/resolve_history.rs
     t reference

diff --git a/iota/docs/identity.rs/v0.5.0/docs/concepts/decentralized_identifiers/update.mdx b/iota/docs/identity.rs/v0.5.0/docs/concepts/decentralized_identifiers/update.mdx
@@ -72,22 +72,15 @@ The following properties can be specified for a service:
 
 The following example demonstrates adding verification methods and services to a DID Document.
 
-<Tabs
-  groupId="programming-languages"
-  defaultValue="nodejs"
-  values={[
-    { label: "Node.js", value: "nodejs" },
-    { label: "Rust", value: "rust" }
-  ]}
->
-<TabItem value="nodejs">
+<Tabs groupId="language" queryString>
+<TabItem value="node" label="Node.js">
 
 ```ts reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/bindings/wasm/examples-account/src/manipulate_did.ts
 ```
 
 </TabItem>
-<TabItem value="rust">
+<TabItem value="rust" label="Rust">
 
 ```rust reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/examples/account/manipulate_did.rs
@@ -100,8 +93,8 @@ https://github.com/iotaledger/identity.rs/blob/support/v0.5/examples/account/man
 
 The Example above starts by [creating an identity using the account](./create.mdx).
 
-<Tabs groupId="code-examples">
-<TabItem value="Rust" label="Rust">
+<Tabs groupId="language" queryString>
+<TabItem value="rust" label="Rust">
 
 ```rust
 let mut account: Account = Account::builder()
@@ -162,8 +155,8 @@ Note that the Account does not allow removing all capability invocation keys.
 
 Another verification method can be added to the DID document using the Account:
 
-<Tabs groupId="code-examples">
-<TabItem value="Rust" label="Rust">
+<Tabs groupId="language" queryString>
+<TabItem value="rust" label="Rust">
 
 ```rust
 account
@@ -226,8 +219,8 @@ Since the `MethodScope` is not specified, the verification method will be create
 
 Verification relationship can be attached to a verification method by referencing its fragment.
 
-<Tabs groupId="code-examples">
-<TabItem value="Rust" label="Rust">
+<Tabs groupId="language" queryString>
+<TabItem value="rust" label="Rust">
 
 ```rust
 account
@@ -297,8 +290,8 @@ property now has both an embedded and a referenced verification method.
 
 Similar to verification methods, services can be added to a DID Document.
 
-<Tabs groupId="code-examples">
-<TabItem value="Rust" label="Rust">
+<Tabs groupId="language" queryString>
+<TabItem value="rust" label="Rust">
 
 ```rust
 account
@@ -373,8 +366,8 @@ The updated Document with the newly created service looks as follows.
 
 Verification methods and/or their relationships can be removed from the DID Document. The following code removes the verification method that we created previously.
 
-<Tabs groupId="code-examples">
-<TabItem value="Rust" label="Rust">
+<Tabs groupId="language" queryString>
+<TabItem value="rust" label="Rust">
 
 ```rust
 account

diff --git a/iota/docs/identity.rs/v0.5.0/docs/concepts/verifiable_credentials/create.mdx b/iota/docs/identity.rs/v0.5.0/docs/concepts/verifiable_credentials/create.mdx
@@ -83,22 +83,15 @@ A [verifiable presentation](./verifiable_presentations.mdx) is the recommended d
 The following code exemplifies how an issuer can create, sign, and validate a verifiable credential. In this example, the issuer signs a UniversityDegreeCredential with Alice's name and DID.
 This Verifiable Credential can be [verified by anyone](./verifiable_presentations.mdx), allowing Alice to take control of it and share it with anyone.
 
-<Tabs
-  groupId="programming-languages"
-  defaultValue="nodejs"
-  values={[
-    { label: "Node.js", value: "nodejs" },
-    { label: "Rust", value: "rust" }
-  ]}
->
-<TabItem value="nodejs">
+<Tabs groupId="language" queryString>
+<TabItem value="node" label="Node.js">
 
 ```ts reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/bindings/wasm/examples-account/src/create_vc.ts
 ```
 
 </TabItem>
-<TabItem value="rust">
+<TabItem value="rust" label="Rust">
 
 ```rust reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/examples/account/create_vc.rs

diff --git a/iota/docs/identity.rs/v0.5.0/docs/concepts/verifiable_credentials/revoke.mdx b/iota/docs/identity.rs/v0.5.0/docs/concepts/verifiable_credentials/revoke.mdx
@@ -45,22 +45,15 @@ Revocation List 2020 is not yet supported in the IOTA Identity Framework
 
 The following code exemplifies how you can revoke a [Verifiable Credential(VC)](overview.mdx) by removing a verification method (public key) from the DID Document of the Issuer. This means the VC can no longer be validated. This would invalidate every VC signed with the same public key, meaning the Issuer would have to sign every VC with a different key.
 
-<Tabs
-  groupId="programming-languages"
-  defaultValue="nodejs"
-  values={[
-    { label: "Node.js", value: "nodejs" },
-    { label: "Rust", value: "rust" }
-  ]}
->
-<TabItem value="nodejs">
+<Tabs groupId="language" queryString>
+<TabItem value="node" label="Node.js">
 
 ```ts reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/bindings/wasm/examples-account/src/revoke_vc.ts
 ```
 
 </TabItem>
-<TabItem value="rust">
+<TabItem value="rust" label="Rust">
 
 ```rust reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/examples/account/revoke_vc.rs

diff --git a/...ity.rs/v0.5.0/docs/concepts/verifiable_credentials/verifiable_presentations.mdx b/...ity.rs/v0.5.0/docs/concepts/verifiable_credentials/verifiable_presentations.mdx
@@ -170,22 +170,15 @@ so setting a signature expiration alone should not be relied upon.
 The following code demonstrates how to use the IOTA Identity Framework end-to-end to create and sign a verifiable presentation as a holder,
 serialize it to JSON for transmission, deserialize it on the receiving side as a verifier, and finally validate it with various options.
 
-<Tabs
-  groupId="programming-languages"
-  defaultValue="nodejs"
-  values={[
-    { label: "Node.js", value: "nodejs" },
-    { label: "Rust", value: "rust" }
-  ]}
->
-<TabItem value="nodejs">
+<Tabs groupId="language" queryString>
+<TabItem value="node" label="Node.js">
 
 ```ts reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/bindings/wasm/examples-account/src/create_vp.ts
 ```
 
 </TabItem>
-<TabItem value="rust">
+<TabItem value="rust" label="Rust">
 
 ```rust reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/examples/account/create_vp.rs

diff --git a/iota/docs/identity.rs/v0.5.0/docs/getting_started/create_and_publish.mdx b/iota/docs/identity.rs/v0.5.0/docs/getting_started/create_and_publish.mdx
@@ -34,22 +34,15 @@ Select your programming language of choice and press the green play button to ex
 
 :::
 
-<Tabs
-  groupId="programming-languages"
-  defaultValue="nodejs"
-  values={[
-    { label: "Node.js", value: "nodejs" },
-    { label: "Rust", value: "rust" }
-  ]}
->
-<TabItem value="nodejs">
+<Tabs groupId="language" queryString>
+<TabItem value="node" label="Node.js">
 
 ```ts reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/bindings/wasm/examples-account/src/create_did.ts
 ```
 
 </TabItem>
-<TabItem value="rust">
+<TabItem value="rust" label="Rust">
 
 ```rust reference
 https://github.com/iotaledger/identity.rs/blob/support/v0.5/examples/account/create_did.rs

diff --git a/iota/docs/identity.rs/v0.6.0/docs/concepts/advanced/storage_interface.mdx b/iota/docs/identity.rs/v0.6.0/docs/concepts/advanced/storage_interface.mdx
@@ -116,22 +116,15 @@ The `StorageTestSuite` can be used to test the basic functionality of storage im
 
 This section shows the Rust and TypeScript `MemStore` implementations, which are thoroughly commented.
 
-<Tabs
-  groupId="programming-languages"
-  defaultValue="nodejs"
-  values={[
-    { label: "Node.js", value: "nodejs" },
-    { label: "Rust", value: "rust" }
-  ]}
->
-<TabItem value="nodejs">
+<Tabs groupId="language" queryString>
+<TabItem value="node" label="Node.js">
 
 ```ts reference
 https://github.com/iotaledger/identity.rs/tree/support/v0.6/bindings/wasm/examples-account/src/custom_storage.ts
 ```
 
 </TabItem>
-<TabItem value="rust">
+<TabItem value="rust" label="Rust">
 
 ```rust reference
 https://github.com/iotaledger/identity.rs/tree/support/v0.6/identity_account_storage/src/storage/memstore.rs