diff --git a/.vitepress/config.mts b/.vitepress/config.mts
index 5dfd880..eb7d8c4 100644
--- a/.vitepress/config.mts
+++ b/.vitepress/config.mts
@@ -82,6 +82,7 @@ export default defineConfig({
           { text: "Server Endorsements", link: "/extensions/server-endorsement" },
           { text: "Events", link: "/extensions/events" },
           { text: "Reports", link: "/extensions/reports" },
+          { text: "Vanity", link: "/extensions/vanity" },
         ]
       }
     ],
@@ -99,7 +100,7 @@ export default defineConfig({
   },
   lastUpdated: true,
   cleanUrls: true,
-  titleTemplate: ":title · Lysand Documentation",
+  titleTemplate: ":title · Lysand 2.0 Docs",
   head: [
     ['link', { rel: 'icon', href: '/favicon.png', type: 'image/png' }]
   ],
diff --git a/docs/index.md b/docs/index.md
index 84c6cfb..9b0b7b1 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -14,18 +14,31 @@ hero:
       text: Protocol Docs
       link: /spec
     - theme: alt
-      text: Types
-      link: /types
+      text: Lysand Server
+      link: https://github.com/lysand-org/lysand
 
 features:
   - title: JSON-based APIs
-    details: Simple JSON objects are used to represent all data
+    details: Simple JSON objects are used to represent all data 
   - title: Built-in namespaced extensions
     details: Extensions for common use cases are built-in, such as custom emojis and reactions
   - title: Easy to implement
     details: The protocol is simple to implement, and can be used with any language
+  - title: Secure by default
+    details: All requests are signed with the latest cryptography algorithms
+  - title: No vendor-specific implementations
+    details: Everything is heavily standardized to ensure compatibility
+  - title: TypeScript types
+    details: TypeScript types are provided for every object in the protocol
 ---
 
+---
+
+> [!INFO]
+> The latest version of Lysand is **2.0**, released on **March 19th 2024** by [**CPlusPatch**](https://cpluspatch.dev).
+>
+> Lysand 2.0 features **more standardization**, **simpler object structures**, and **documentation rewrite**.
+
 <style>
 :root {
   --vp-home-hero-image-background-image: linear-gradient(to top right, rgb(249, 168, 212), rgb(216, 180, 254), rgb(129, 140, 248));
diff --git a/docs/objects/server-metadata.md b/docs/objects/server-metadata.md
index 543887b..235a3f1 100644
--- a/docs/objects/server-metadata.md
+++ b/docs/objects/server-metadata.md
@@ -94,7 +94,7 @@ Represents the website of the server. This may be used to link to the server's w
 
 | Name       | Type            | Required |
 | :--------- | :-------------- | :------- |
-| moderators | Array of string | No       |
+| moderators | Array of String | No       |
 
 Rrray of URIs to the server moderators.
 
@@ -104,7 +104,7 @@ If it is not provided, it is assumed that the server does not have any moderator
 
 | Name   | Type            | Required |
 | :----- | :-------------- | :------- |
-| admins | Array of string | No       |
+| admins | Array of String | No       |
 
 The `admins` field on a Server Metadata object is an array of URIs that represent the admins of the server.
 
@@ -149,6 +149,6 @@ Clients should display the most modern format that they support, such as WebP, A
 
 | Name                 | Type            | Required                       |
 | :------------------- | :-------------- | :----------------------------- |
-| supported_extensions | Array of string | Yes, can be empty array (`[]`) |
+| supported_extensions | Array of String | Yes, can be empty array (`[]`) |
 
 List of extension names that the server supports, in namespaced format (`"org.lysand:reactions"`).
\ No newline at end of file
diff --git a/docs/structures/content-format.md b/docs/structures/content-format.md
index a375e48..12a5398 100644
--- a/docs/structures/content-format.md
+++ b/docs/structures/content-format.md
@@ -1,4 +1,4 @@
-# ContentFormat Protocol
+# ContentFormat
 
 The `ContentFormat` structure, as represented below in TypeScript, is a flexible and robust way to handle various types of content. It is designed to accommodate a wide range of content types and provide additional metadata about the content.