• Add the openURL in the code snippet in the "how to use the SSO SDK" page
• Add a note about the limitation of opening a new tab
• Add a note about the recommendation to use hasSession and a conditional connect() for a smoother authentication

• Update the tutorial with the the code from https://developers.verida.io/docs/concepts/verifiable-credentials
• Update https://developers.verida.io/docs/concepts/verifiable-credentials with new screenshots

Implement the landing page (I think pages/index.js) using the design https://www.figma.com/file/vhxDoIDoel8GtruvUnerYK/Developers---landing-page?node-id=194%3A6201

The following pages need updating for the new account API:

• https://developers.verida.io/docs/single-sign-on-sdk/how-to-use-the-sso-sdk (DONE)
• https://developers.verida.io/docs/tutorial/SSO (DONE)
• https://developers.verida.io/docs/client-sdk/getting-started (FIXED)
• https://github.com/verida/verida-js/blob/main/packages/client-ts/README.md (make this point at developer docs). Will be fixed by the relevant issue in verida-js. (DONE)

Components:

• https://github.com/verida/verida-vue-components (DONE)

Platforms:

• https://github.com/verida/Credentials-Management-Platform

Demos:

• https://github.com/verida/web-sandbox (DONE)
• https://github.com/verida/demo-credential-issuer (DONE)
• https://github.com/verida/account-explorer (DONE)
• https://github.com/verida/markdown-notes-demo
• https://github.com/verida/practitioner-emr-web
• https://github.com/verida/vault-showcase (DONE)

Seems to work in Chrome and Safari.

See verida/verida-js#182

The following changes are needed

• Update the footer to be the same as at https://verida.io
• Fix the "Terms & Conditions" link to go to https://www.verida.io/terms-and-conditions
• In the top (header) menu to be:
  • (Left aligned): Verida Logo Documentation API Tutorial Demos
  • (Right aligned): Verida Homepage Github Search
• Fix the copyright link and text in the footer (to be the same as https://verida.io)

The API Docs are currently pretty messy. Move them to Docusaurus to make it easier to refer to them.

We should have an example DID document that helps explain how the DID registry ties everything together.

This should be somewhere in concepts.

Add this and make sure it gets loaded on every page

<script defer data-domain="developers.verida.io" src="https://plausible.io/js/plausible.js"></script>

Link for "Documentation" in the footer menu should be updated.
It's currently pointing to an old link: https://docs.datastore.verida.io/#/
It should point to: https://developers.verida.io/

Docusaurus has support for this, see: https://docusaurus.io/docs/markdown-features/code-blocks#npm2yarn-remark-plugin

Need to update:

• https://developers.verida.io/docs/client-sdk/getting-started
• https://developers.verida.io/docs/single-sign-on-sdk/how-to-use-the-sso-sdk

Check other markdown pages for any mention of yarn

We need a "quick start" page to explain to developers how to get started with Verida

• Disable dark mode (remove the whole switch)
• Remove the whole newsletter section from the front page footer

Update

• @verida/client-ts to 1.1.15
• @verida/verifiable-credentials to 1.1.6
• @verida/account-web-vault to 1.1.7

Task

update the code in the send message tutorial to match the documentation for send message in the Client SDK section.

• Change "Welcome to your Web3 toolkit!" to: “Welcome to the Verida Developer Portal’
• Add: “Verida is a multi-chain protocol for interoperable database storage and messaging built on decentralized identity.”

For each of the 4 boxes, have explainer text. 1-2 sentences. E.g.

• Read the documentation
  • Add Subtext “Learn about the core concepts of the Verida protocol, the network and more ”
• Explore API Documentation
  • Add Subtext “Detailed documentation of the Verida JS library”
• Interactive Tutorial
  • Add Subtext: “Try the interactive tutorial to get you coding with Verida as quickly as possible.”
• Demos
  • Add Subtext: “Test our demo applications to interact with the Verida protocol ”
    Reduce icon size

Replace the "Download the Verida Vault (Developer Preview)" section with another "box" section (similar to the 4 box section above). The title for this part should be "Getting Started"

This section should have 3 boxes, from left to right:

• Download the Verida Vault (Developer Preview) with links & icons to the AppStore and PlayStore
• Implement the Single Sign On and Client SDK Javascript SDKs in your application.
• For Vue developers, try the Vue Starter Kit.

Update the linked GitHub repos to these:

• Verida-JS
• Account Explorer
• Markdown Notes
• Storage Node
• Vault Examples
• Vue starter kit

Add the subheading under "Github Repositories" that says: "The Verida protocol is comprised of an ecosystem of open source components"

Update technical capabilities page to include reference implementations.

Update the verifiable credentials documentation to explain the latest technical capabilities provided by verida/verida-js#157

Many pages in the documentation have h1 headers (ie: https://developers.verida.io/docs/concepts/data-storage).

These appear very large, aren't linkable and don't appear in the sub-menu navigation. This makes me think we should only use h2 and smaller within the content of our documentation.

@nick-verida ?

Add HTML metadata to landing page. Use https://www.heymeta.com/url/developers.verida.io to generate correct tags.

Add an example in the https://developers.verida.io/docs/client-sdk/data#opening-databases section on how to use the Client class to open an external context and database.

see @tahpot example code from this comment verida/verida-js#170 (comment)

  const context = await client.openExternalContext()
  const db = await context.openExternalDatabase() 

Using the VC Example feature branch at https://feature-vc-example.d3e62gra73ggnc.amplifyapp.com/docs/tutorial/verifiable_credentials

Send yourself a VC. It appears as a message correctly and can be accepted, but never appears in the Data section in the Vault

New verida-js library release needs API docs synced

We should discuss how data is signed and how it can then be used on chain in the future.

Now the VC implementation is for demonstration purposes only the docs should make that clear.

Currently https://developers.verida.io/docs/client-sdk/data both explains the difference between datastores and databases AND explains CRUD operations. Split this up better.

see screenshot

Here's a list of things that need fixing before we can close this project out:

• The HTML title tag is wrong. It should be getting set from config.title in docusaurus.config.js but is instead is Hello from ${siteConfig.title}
• The HTML description meta tags are wrong. Currently are <meta name="description" content="Description will go into a meta tag in <head />" data-react-helmet="true"> and <meta property="og:description" content="Description will go into a meta tag in <head />" data-react-helmet="true">. Chris asked for the SEO tags to be done and this is one of the main ones.
• Search doesn't seem to be working. Note that we are going to need to change the URL this is hosted at so we will need to config for this.
• Please update the link title in the header that goes to https://verida.io. Currently it is titled "Main" and please change that to "Verida Homepage".
• There are some Markdown-style links that are not being rendered properly. An example is https://main.d3e62gra73ggnc.amplifyapp.com/docs/client-sdk/data#user-owned-datastore where it looks like this:
  
  Is there a config setting to change this? Or is there a way to find all the cases where this is happening?

As per https://github.com/verida/vault-mobile/issues/394#issuecomment-1080334156 the Account API should be reverted to this:

const account = new VaultAccount({
  request: {
    logoUrl: "https://assets.verida.io/verida_login_request_logo_170x170.png",
  }
});

I have the same Twitter account connected to two Verida accounts:

• did:vda:0x77fA3AD11A82965aB59e643Ac59448c262bD905D (which I connected it to first)
• did:vda:0xC3527839Cd28212D1b56C29Dc294Ed7966feA828

In the Vault the data shows for both.

When I request did:vda:0xC3527839Cd28212D1b56C29Dc294Ed7966feA828 I get the request in the Vault, consent, but no data shows up.

When I request did:vda:0x77fA3AD11A82965aB59e643Ac59448c262bD905D it works as expected.

It is possible to syncronize data between two databases in different application contexts.

This was previously implemented in the https://github.com/verida/practitioner-emr-web project allowing a user to sync their health records between the Vault and the EMR application.

Here is the code in the EMR web application that generates the Vault message requesting data to be syncronized.

The tutorial needs to add the ability for to generate this type of data sync request, to create a local encrypted database in the tutorial context and sync it with data from the Vault (perhaps the contexts or credentials?).

Update the demos page to look something like below

It works well on mobile, so keep that. But below 1000px we get scroll bars.

Make the linked GitHub repos these:

https://github.com/verida/verida-js
https://github.com/verida/account-explorer
https://github.com/verida/markdown-notes-demo
https://github.com/verida/generic-demo
https://github.com/verida/documentation
https://github.com/verida/storage-node

Add data storage architecture to concepts page.

While there, fix the headers.

Add a tutorial based on the web sandbox

Underneath the Join our Discord Community box have another similar box. This one should:

• Say "Verida Early Adopter Program"
• Have a subtitle "Join the growing ecosystem of partners building the future of web3"
• Link to https://www.verida.io/ecosystem#partner

Tasks

Add documentation under "extensions" sections on step-by-step instructions for how to get it, create a project using it, and how best to use it.