Add category files

docs/static/abi.mdx

@@ -0,0 +1,4 @@
+---
+title: Application Binary Interface
+description: 'Implement smart contracts through their Application Binary Interface (ABI).'
+---

docs/static/address.mdx

@@ -0,0 +1,13 @@
+---
+title: Addresses
+description: ''
+---
+
+Addresses are a fundamental part of interacting with Quai Network. They represent the gloabal identity of Externally Owned Accounts (accounts backed by a private key), contracts, and UTXO wallets.
+
+These functions help convert between various formats, validate addresses across the Quai and Qi address spaces, and other utilities for working with addresses.
+
+The Quais SDK supports the following address formats:
+
+-   `quai` addresses
+-   `qi` addresses

docs/static/constants.mdx

@@ -0,0 +1,4 @@
+---
+title: Constants
+description: 'A collection of useful constants when interacting with Quai Network.'
+---

docs/static/crypto.mdx

@@ -0,0 +1,6 @@
+---
+title: Cryptographic Functions
+description: 'A set of common cryptographic functions used in Quai Network.'
+---
+
+A fundamental building block of Quai Network is the underlying cryptographic primitives.

docs/static/encoding.mdx

@@ -0,0 +1,4 @@
+---
+title: Encoding Utilities
+description: 'Utilities for common tasks involving data encoding.'
+---

docs/static/hash.mdx

@@ -0,0 +1,4 @@
+---
+title: Hashing Utilities
+description: 'Utilities for common tasks involving hashing.'
+---

docs/static/provider.mdx

@@ -0,0 +1,8 @@
+---
+title: Providers
+description: 'Configure and utilize a Provider to interact with Quai Network.'
+---
+
+A Provider provides a connection to the blockchain, whch can be used to query its current state, simulate execution and send transactions to update the state.
+
+It is one of the most fundamental components of interacting with a blockchain application, and there are many ways to connect, such as over HTTP, WebSockets or injected providers such as Pelagus.

docs/static/signer.mdx

@@ -0,0 +1,6 @@
+---
+title: Signers
+description: 'Configure and manage signers for Quai and Qi.'
+---
+
+A Signer can represent an account on the either the Quai or Qi ledger, and is most often backed by a private key represented by a mnemonic or residing on a Hardware Wallet.

docs/static/transactions.mdx

@@ -0,0 +1,6 @@
+---
+title: Transactions
+description: 'Build and sign transactions on Quai Network.'
+---
+
+Transactions are a fundamental piece of Quai Network. Every state-changing operation within the network requires a signed transaction.

docs/static/utils.mdx

@@ -0,0 +1,6 @@
+---
+title: Utilities
+description: 'Utility functions for common tasks.'
+---
+
+A collection of useful utilities for manipulating data, mathematical operations, and more.

docs/static/wallet.mdx

@@ -0,0 +1,10 @@
+---
+title: Wallets
+description: 'A combination of generalized and low-level wallet tools.'
+---
+
+When interacting with either Qi or Quai, it is necessary to use a private key authenticate actions by signing a payload.
+
+Wallets are the simplest way to expose the concept of an Externally Owner Account (EOA) or UTXO account as it wraps a private key and supports high-level methods to sign common types of interaction and send transactions.
+
+The class most developers will want to use is Wallet, which can load a private key directly or from any common wallet format.

docs/static/wordlists.mdx

@@ -0,0 +1,12 @@
+---
+title: Wordlists
+description: 'A collection of wordlists for use in various applications.'
+---
+
+A Wordlist is a set of 2048 words used to encode private keys (or other binary data) that is easier for humans to write down, transcribe and dictate.
+
+The BIP-39 standard includes several checksum bits, depending on the size of the mnemonic phrase.
+
+A mnemonic phrase may be 12, 15, 18, 21 or 24 words long. For most purposes 12 word mnemonics should be used, as including additional words increases the difficulty and potential for mistakes and does not offer any effective improvement on security.
+
+There are a variety of BIP-39 Wordlists for different languages, b