diff --git a/src/app/v5/core/events/page.mdx b/src/app/v5/core/events/page.mdx
new file mode 100644
index 0000000..d0f535e
--- /dev/null
+++ b/src/app/v5/core/events/page.mdx
@@ -0,0 +1,148 @@
+# Events
+
+Events in Firebot are automatic triggers that run a list of effects in response to specific activities on your stream, such as new followers, subscribers, cheers, or chat messages. This allows you to create dynamic and interactive alerts and responses without any manual input. They will often have specific variables associated with the event, so if you're trying to recreate an effect from a command and it isn't working it is worth checking to make sure that you are using the correct variables. For example, sub events do *not* have an associated `$chatMessage` variable, as there is no chat message associated with the event. If you want to capture the message associated with a sub then you would instead use the `$subMessage` variable. You can check available variables anywhere you can see the blue `$vars` button.
+
+You can manage all your events from the **Events** tab, located in the main navigation sidebar under the "Triggers" category. 
+
+Events are a good way to acknowledge and reward your community's engagement, making your stream more interactive and professional. 
+
+## General Events vs. Event Sets
+
+Firebot organizes events into two main categories:
+
+*   **General Events:** This is where you can create and set effects for general events that you want to react to. They are perfect for alerts that you want to be available at all times, like standard follow or subscription notifications.
+*   **Event Sets:** These are groups of events that you can activate or deactivate as a whole. This is useful for creating different themes of alerts for specific games, holidays, or special stream occasions. For example, you could have a "Horror Game" event set with spooky alerts that you only activate when playing horror games.
+
+## Creating a New Event
+In the top left of the screen is a blue button with `+ New Event` as the label. To create a new event simply click on this button.
+
+## Configuring an Event
+
+Whether you're creating a new event or editing an existing one, the configuration process is the same.
+
+### **Trigger On**
+This is the core of your event. Here you select the specific activity that will trigger the effects. Firebot provides a wide range of triggers from various sources:
+
+*   **Twitch:** Includes follows, subs, raids, cheers, channel point redemptions, and more.
+*   **Integrations:** If you have linked services like Streamlabs, StreamElements, or others, their specific events (like donations) will appear here.
+*   **Firebot:** Internal events such as chat connections or when a custom variable expires.
+
+*   **Others:** Custom scripts can sometimes add custom events. 
+*   A complete list of triggers will be added to the bottom of the document. 
+
+### **Name**
+Give your event a descriptive name (e.g., "New Follower Alert," "Tier 2 Sub Thank You"). This helps you stay organized, especially as you create more events.
+
+### **Filters**
+Filters allow you to add specific conditions that must be met for the event to trigger. This lets you create targeted responses.
+
+**Example**: You could create a "Sub" event but add a filter for "Sub Tier" -> "is" -> "Tier 3". This event would then *only* trigger for Tier 3 subscriptions, allowing you to have a special alert just for them.
+
+You can add multiple filters and choose whether **all** of them must be met or if **any** of them can be met for the event to trigger.
+
+### **Settings**
+
+*   **Is Enabled:** A simple toggle to turn the event on or off without deleting it.
+*   **Custom Cooldown:** This prevents the event from triggering too frequently. You can set a cooldown in seconds and specify if it applies globally (to all viewers) or per user. This is useful for events like "First Time Chat" to prevent it from firing multiple times if a new chatter sends several messages in quick succession.
+
+### **Effects**
+This is where you define what happens when the event is triggered. You can add one or more effects that will run in sequence.
+
+*   Click the **"Add New Effect"** button to open the effect selector.
+*   Choose any effect, such as **Play Sound**, **Show Image/GIF**, or **Chat**.
+*   Configure each effect as needed. You can use event-specific variables (like `$user` for the person who triggered the event) to personalize the response.
+*   Find out more about effects here: [Effects](../effects/page.mdx)
+
+## Event Sets
+
+Event Sets are useful for managing different themes of alerts.
+
+*   **Creating a Set:** In the Events tab, click the plus icon next to the "Event Sets" header. Give your set a name, and it will appear in the list.
+*   **Activating/Deactivating:** Each Event Set has a status dot next to its name. A green dot indicates it's active; a gray dot means it's inactive. Click the three-dot menu next to the set's name to activate or deactivate it. You can also use the **Toggle Event Set** effect to control this automatically.
+*   **Managing Events:** Click on an Event Set to view and manage the events within it, just as you would with General Events.
+
+## Simulating Events
+
+To test your events without waiting for a real stream activity, you can use the "Simulate Event" button located in the toolbar. This opens a modal where you can select any event type and fill in placeholder data (like a username or sub tier) to see how your effects will behave. This is an excellent way to fine-tune your alerts.
+
+---
+
+## **Example: Creating a Custom Raid Alert**
+
+**Premise:** You want to create a special alert that plays a sound and shows a GIF when your channel gets raided.
+
+1.  **Create a New Event:** In the **Events** tab, click the **"New Event"** button.
+
+2.  **Configure the Trigger:**
+    *   For **Trigger On**, select `Twitch` as the source and `Raid` as the event.
+    *   Give it a **Name**, like "Raid Alert".
+
+3.  **Add Effects:**
+    *   **Play Sound:** Add a "Play Sound" effect and choose a sound file from your computer that you want to play when you get raided.
+    *   **Show Image/GIF:** Add a "Show Image/GIF" effect and select a GIF to display on your overlay. Configure its position and duration.
+    *   **Chat Message:** Add a "Chat" effect to thank the raider and welcome their viewers.
+        *   **Message:** `Welcome raiders from $user's channel! Thanks so much for the raid, hope you enjoy your stay!`
+
+4.  **Save the Event:** Click "Save" and your new raid alert is ready to go!
+
+---
+
+## Events List
+
+### **Firebot Events** 
+
+*   **Chat Connected:** Triggers when Firebot successfully connects to Twitch chat. 
+*   **Overlay Connected:** Activates when a Firebot overlay is connected. 
+*   **View Time Update:** Runs when a viewer's watch time is updated. 
+*   **Currency Update:** Triggers when a viewer's currency amount changes. 
+*   **Viewer Created:** Activates when a new viewer is added to the database, typically after their first chat message.
+*   **Firebot Started:** Triggers when Firebot is launched and running. 
+*   **Custom Variable Expired:** Activates when a custom variable's set duration expires. 
+*   **Custom Variable Created:** Triggers when a new custom variable is created. 
+*   **Chat Message Spotlight:** Activates when a chat message is spotlighted, for example, to be displayed on an overlay. 
+*   **Category Changed:** Triggers when the stream category is changed in the Firebot dashboard. 
+*   **Effect Queue Cleared:** Activates when an effect queue has finished and is cleared. 
+*   **Before Firebot Closed:** Triggers just before Firebot shuts down. 
+*   **Viewer Rank Updated:** Activates when a viewer's rank changes. 
+*   **Viewer Metadata Updated:** Triggers when a viewer's metadata is updated. 
+
+### **Twitch Events** 
+
+*   **Raid:** Triggers when another channel raids yours.
+*   **Follow:** Activates when someone follows your channel.
+*   **Sub:** Triggers for new subscriptions and re-subscriptions.
+*   **Prime Sub Upgraded:** Activates when a viewer upgrades their Prime Gaming subscription to a paid one. 
+*   **Sub Gifted:** Triggers when a viewer gifts a subscription to another user.
+*   **Community Subs Gifted:** Activates when a viewer gifts multiple subscriptions to the community.
+*   **Gift Sub Upgraded:** Triggers when a viewer upgrades their gifted subscription to a paid one. 
+*   **Cheer:** Activates when a viewer sends Bits.
+*   **Bits Badge Unlocked:** Triggers when a viewer unlocks a new Bits badge tier. 
+*   **Viewer Arrived:** Activates when a viewer sends their first message in a stream.
+*   **Chat Cleared:** Triggers when the chat is cleared. 
+*   **Chat Message:** Activates for every new chat message.
+*   **Chat Message Deleted:** Triggers when a chat message is deleted. 
+*   **First Time Chat:** Activates when a viewer chats for the first time ever in your channel.
+*   **Announcement:** Triggers when a moderator sends an announcement. 
+*   **Viewer Banned:** Activates when a viewer is banned from the channel. 
+*   **Viewer Unbanned:** Triggers when a viewer is unbanned. 
+*   **Viewer Timeout:** Activates when a viewer is timed out. 
+*   **Channel Reward Redemption:** Triggers when a viewer redeems a channel point reward. 
+*   **Channel Reward Redemption Approved:** Activates when a channel point redemption is approved.
+*   **Channel Reward Redemption Rejected:** Triggers when a channel point redemption is rejected. 
+*   **Whisper:** Activates when you or your bot account receives a whisper. 
+*   **Chat Mode Changed:** Triggers when a moderator changes chat modes (e.g., emote-only, sub-only). 
+*   **Channel Poll Started/Progress/Ended:** Activates at the start, during, and at the end of a Twitch poll. 
+*   **Channel Goal Started/Progress/Ended:** Activates at the start, during, and at the end of a channel goal. 
+*   **Channel Prediction Started/Progress/Locked/Ended:** Triggers at the start, during, when locked, and at the end of a channel prediction. 
+*   **Hype Train Started/Progress/Ended:** Activates at the start, during, and at the end of a Hype Train. 
+*   **Stream Started/Ended:** Triggers when your stream goes live or ends. 
+*   **Charity Campaign Started/Donation/Progress/Ended:** Triggers for events related to a charity campaign on your channel. 
+*   **Shoutout Sent/Received:** Activates when you send or receive a shoutout. 
+*   **Category Changed:** Triggers when your stream category changes on Twitch. 
+*   **Title Changed:** Activates when your stream title changes on Twitch. 
+*   **Scheduled Ad Break Starting Soon:** Triggers when a scheduled ad break is about to start. 
+*   **Ad Break Started/Ended:** Activates at the start and end of an ad break.
+
+### **Integration Events** 
+
+*   **Streamlabs, StreamElements, TipeeeStream, Extra Life:** These integrations have their own set of events, primarily for donations and follows, which will appear as "Trigger On" options when the respective service is linked to Firebot.
\ No newline at end of file
diff --git a/src/app/v5/core/timers/page.mdx b/src/app/v5/core/timers/page.mdx
new file mode 100644
index 0000000..53cf77f
--- /dev/null
+++ b/src/app/v5/core/timers/page.mdx
@@ -0,0 +1,118 @@
+# Timers and scheduled effects
+
+## **Timers**
+
+Timers in Firebot are a crucial feature for automating various actions on your stream at set intervals. They allow you to schedule regular messages in chat, trigger effects, or perform other tasks, ensuring consistent engagement even when you're focused on gameplay or conversation.
+
+You can access and manage all your timers from the **TIME-BASED** tab, located in the main navigation sidebar under "Triggers". This tab is dedicated to "Time-Based" events, allowing you to schedule actions to occur automatically.
+
+Timers are an good way to remind your viewers about important information, promote your social media, or even run mini-games without constant manual intervention.
+
+## **Creating a Timer**
+To create a new time click on the blue button in the top right labeled `+ New Timer` of the Time-Based tab. This will bring up four options, name, interval, required chat lines and "Only Run When Live", as well as an effects list when you can add the effects to be run on the timer. 
+
+*   **Name**
+    This is where you can name your timer. It is generally a good idea to give it a descriptive name so you don't forget what it's for. 
+*   **interval**
+    This is where you decide how long an interval Firebot waits before triggering the effects list. This is measured in seconds, so if you wanted to wait 30 minutes you would use 1800 seconds. 
+*   **Required Chat Lines**
+    This is the minimum number of lines in chat since the last time this interval timer ran. So if nobody has said anything in chat this timer will not trigger until the some people have commented in chat enough to reach this minimum. 
+
+**Example**: If you set `Interval` to `900` seconds (15 minutes) and `Required Chat Lines` to `25`, the timer will only send a message if 25 or more lines of chat have occurred in the last 15 minutes. This prevents messages from repeating in an empty channel.
+
+* **Only Run When Live**
+This checkbox determines whether the timer should operate only when your stream is actively live.
+    *   **Enabled (checked):** The timer will only run its effects when your stream is online. This is generally recommended for most chat-based timers.
+    *   **Disabled (unchecked):** The timer will run its effects even when your stream is offline. This might be useful for very specific, non-stream-dependent automation.
+
+### **Effects**
+This is where you define the actions that the timer will perform when it triggers. You can add one or more effects that will run in the order they appear.
+
+*   **Add effects:** Click the blue **"Add New Effect"** button to open the effect selector.
+*   **Select effects:** Choose any effect, such as **Chat**, **Play Sound**, or **Run Random Effect**.
+*   **Configure effects:** Each added effect has its own settings that you can customize.
+*   **Order of execution:** Multiple effects will run sequentially.
+*   **Random or Sequential Effects:** For timers that display chat messages, it's often useful to use the **Run Random Effect** or **Run Sequential Effect** within your effects list. This allows you to set up multiple chat messages, and the timer will rotate through them or pick one at random each time it fires, preventing repetitive messages.
+---
+
+
+## Timer Example: Promoting Social Media
+
+You want to periodically remind your viewers about your social media channels in chat, but only when chat is active.
+
+1.  **Create a New Timer:**
+    *   Navigate to the **Timers** tab.
+    *   Click the blue **"+ New Timer"** button.
+    *   **Name**: `"Social Media Plug"`
+    *   **Interval (secs)**: `"600"` (This means the timer will try to run every 10 minutes).
+    *   **Required Chat Lines**: `"5"` (The timer will only run if there have been at least 5 lines of chat in the last 10 minutes).
+    *   **Only Run When Live**: Ensure this is **checked**.
+
+2.  **Add Effects:**
+    *   Add a **Run Sequential Effect**.
+        *   Inside this sequential effect, add multiple **Chat** effects.
+            *   **Chat Effect 1 Message**: `"Don't forget to follow me on Twitter! $twitter[handle]"`
+            *   **Chat Effect 2 Message**: `"Join our Discord server for more fun! $discord[invite]"`
+            *   **Chat Effect 3 Message**: `"Check out my latest YouTube video! $youtube[latestvideo]"`
+
+3.  **Save the Timer**: Click **"Save"**.
+
+Now, every 10 minutes (provided there's been at least 5 lines of chat), Firebot will post one of your social media messages in chat, rotating through them sequentially.
+
+---
+## **Scheduled Effect List**
+
+Scheduled Effect Lists in Firebot allow you to automate actions at specific times or recurring schedules, independent of chat activity or stream status. This is ideal for daily greetings, weekly reminders, or seasonal events.
+
+You can create and manage all your Scheduled Effect Lists from the **TIME-BASED** tab, located in the main navigation sidebar under "Triggers", by selecting the **"SCHEDULED EFFECT LISTS"** sub-tab.
+
+Scheduled Effect Lists are perfect for automating consistent stream elements, such as reminding viewers about an upcoming weekly show, a daily poll, or even a monthly giveaway announcement.
+
+## **Creating a Scheduled Effect List**
+To create a new Scheduled Effect List, click on the blue button labeled `+ New Scheduled Effect List` in the top right of the "SCHEDULED EFFECT LISTS" sub-tab. This will open a new window with several options, including name, schedule, and an effects list.
+
+*   **Name**
+    This is where you name your Scheduled Effect List. A descriptive name helps you quickly identify its purpose, especially if you have multiple schedules.
+*   **Schedule**
+    This is the core of a Scheduled Effect List, defining exactly when your effects will run. You have two options:
+    *   **Simple Schedule**: Choose from predefined options like "Every Minute," "Every Hour," "Every Day," "Every Month," or "Every Weekday." This is straightforward for common recurring tasks.
+    *   **Advanced Schedule**: For more complex timing, you can use a [crontab expression](https://crontab.guru/). This allows for highly specific schedules (e.g., "every Monday at 8 AM" or "the last day of every month").
+        *   When you add a crontab expression to the input field, a "friendly name" will appear, translating your cron expression into a human-readable format to help you verify your schedule.
+*   **Only Run When Live**
+    This checkbox determines whether the Scheduled Effect List should operate only when your stream is actively live.
+    *   **Enabled (checked):** The effects will only run when your stream is online. This is generally recommended for most alerts or chat messages.
+    *   **Disabled (unchecked):** The effects will run even when your stream is offline. This might be useful for behind-the-scenes tasks or messages intended for your community outside of live hours.
+
+### **Effects**
+This is where you define the actions that the Scheduled Effect List will perform when it triggers. You can add one or more effects that will run in the order they appear.
+
+*   **Add effects:** Click the blue **"Add New Effect"** button to open the effect selector.
+*   **Select effects:** Choose any effect, such as **Chat**, **Play Sound**, or **Run Command**.
+*   **Configure effects:** Each added effect has its own settings that you can customize.
+*   **Order of execution:** Multiple effects will run sequentially.
+*   **Random or Sequential Effects:** For chat messages, using **Run Random Effect** or **Run Sequential Effect** can prevent repetitive messages by rotating through a list of predefined messages or selecting one randomly.
+
+---
+
+## Scheduled Effect List Example: Weekly Stream Reminder
+
+You want to automatically post a reminder in chat every Sunday at 3 PM (your local time) about your upcoming stream, but only if you are live.
+
+1.  **Create a New Scheduled Effect List:**
+    *   Navigate to the **TIME-BASED** tab and select the **"SCHEDULED EFFECT LISTS"** sub-tab.
+    *   Click the blue **"+ New Scheduled Effect List"** button.
+    *   **Name**: `"Weekly Stream Reminder"`
+    *   **Schedule**:
+        *   Select **"Advanced Schedule"**.
+        *   Enter the cron expression: `"0 15 * * SUN"` (This translates to "At 3:00 PM, only on Sunday").
+        *   Verify the "friendly name" matches your intention.
+    *   **Only Run When Live**: Ensure this is **checked**.
+    *   **Enabled**: Ensure this is **checked**.
+
+2.  **Add Effects:**
+    *   Add a **Chat** effect.
+        *   **Message**: `"Don't forget, my stream is coming up this week! Get ready for some fun at [Your Stream Link]"`
+
+3.  **Save the Scheduled Effect List**: Click **"Save"**.
+
+Now, every Sunday at 3 PM, if your stream is live, Firebot will automatically post your stream reminder message in chat.
\ No newline at end of file
diff --git a/src/app/v5/guides/effect-queues/page.mdx b/src/app/v5/guides/effect-queues/page.mdx
new file mode 100644
index 0000000..2685b80
--- /dev/null
+++ b/src/app/v5/guides/effect-queues/page.mdx
@@ -0,0 +1,46 @@
+# **Effect Queues**
+
+The Effect Queues in Firebot are a feature that helps manage and display alerts on your stream in an organized manner. It allows you to add separate effects lists to a queue, meaning that you can play lists of effects one after another, preventing overlap and ensuring that each effect list gets its moment in the spotlight.
+
+You can find queues in two locations. First in the **Effect Queues** tab, located in the main navigation sidebar under the "Management" category. You can also find them by looking at the top right of any effects list just underneath **QUEUE**. If you haven't set a queue yet, click on the `V` symbol next to "Not set" to add your effects to a queue, or create a new queue. If you already added the effects to a queue then "Not set" will become the name of the queue, you can still click on the `V` to change the queue.
+
+## **Creating an Effect Queue**
+If you are in the Effect Queues management tab then click on the blue button labeled `+ New Effect Queue`. If you want to create a queue from the drop down menu for an effects list then select "Create new queue".
+
+## **Configuring an Effect Queue**
+When creating a new queue you will be given two options, name and mode. 
+
+### **Name**
+This is where you create the name for your queue, it is generally good practice to use a descriptive name that will make it obvious what the queue is for when you come to look at it later. 
+
+### **Mode**
+
+Here you have three options:
+
+* **Custom**
+    This will wait a custome amount of time between effects, meaning you can set a specific time before it moves onto the next effect. When you select a custom effect queue from the effect list drop down menu two options will appear next to it, "EFFECTS DURATION", which is the total duration (in seconds) the queue should wait after triggering the effect list before triggering the next one. And "QUEUE PRIORITY", if an effect list has priority it will get added in front of other lists in that queue that do not have priority. 
+* **Sequential**
+    This will run effects lists in the queue sequentially, priority items will be addded before non-priority. There is an optional additional delay that you can add between effects lists, that will default to 0 seconds. When you select this option while creating the queue it will give you a new third option "INTERVAL/DELAY (SECS)", where you can optionally add the delay time between effect lists. When you add a list to this queue the option to give the effect list priority will appear to the left of the queue drop down menu. 
+* **Interval**
+    This runs effects lists after a set interval. When you select this option this will give you the third "INTERVAL/DELAY (SECS)" option. When you add an effects list it will also give you the option to make the effects list a priority for that queue. 
+---
+## **Example: Managing Multiple Donations with a Queue**
+
+You want to ensure that every donation, regardless of how quickly they come in, gets a distinct on-stream alert without overlapping.
+
+1.  **Create a New Effect Queue:**
+    *   Navigate to the **Effect Queues** tab in Firebot.
+    *   Click the blue **"+ New Effect Queue"** button.
+    *   Name your queue: `"Donation Alerts"`
+    *   Select **Mode**: `"Sequential"` (This ensures alerts play one after another).
+    *   Click **"Save"**.
+
+2.  **Configure a Donation Event to use the Queue:**
+    *   Go to the **Events** tab.
+    *   Find or create an event that triggers on `"Twitch"` -> `"Cheer"` (for Bits) and another for `"Streamlabs"` -> `"Donation"`.
+    *   For each of these events, in the event's "Effects" section:
+        *   Add your desired effects (e.g., **Play Sound**, **Show Image/GIF**, **Chat Message**).
+        *   In the top right corner of the effects list, next to **"QUEUE"**, click the `V` symbol.
+        *   Select your newly created `"Donation Alerts"` queue from the dropdown.
+
+Now, whenever you receive multiple donations close together, Firebot will add each associated effects list to the "Donation Alerts" queue. Each alert will play fully, ensuring no alerts overlap and every donor is properly acknowledged.
\ No newline at end of file
diff --git a/src/app/v5/guides/metadata/page.mdx b/src/app/v5/guides/metadata/page.mdx
new file mode 100644
index 0000000..301f2d4
--- /dev/null
+++ b/src/app/v5/guides/metadata/page.mdx
@@ -0,0 +1,77 @@
+# **Metadata Effects**
+
+Metadata allows you to store viewer specific data for use in Firebot. 
+
+You can use metadata by using the  **Set User Metadata** and **Remove User Metadata** effects, found in the “Select New Effect” box when adding a new effect. They’re listed under the “ALL” and “Scripting” tabs.  Metadata works by storing data (basically text) associated with a specific viewer's username.
+
+Using Metadata you can tailor interactive experiences to individual viewers like tracking stats, preferences, or progress within a game or loyalty system. It works similarly to [Custom Variables](/v5\guides\custom-variables\page.mdx), but custom variables are not associated with a single viewer, and unless you have changed the settings do not persist when you close Firebot, meaning that when you close Firebot all data is deleted. Metadata on the other hand is stored for each user persistently and can be used across Firebot sessions. 
+
+## **Configuring Metadata Effects**
+
+### **Username**
+
+Specify the username for whom you want to configure or modify the metadata.  This should generally be the `$user` variable to affect the user triggering the event.
+
+### **Metadata Key**
+
+This is where you define the name of the specific piece of information you want to store. Choose a descriptive key without spaces (e.g., `favoriteColor`, `level`, `totalPoints`). A common practice is using camelCase.
+
+### **Data**
+
+This is the actual value you want to store under the specified Metadata Key. This can be static text, numbers, or any other data, or you can reference Firebot's built-in variables using the `$vars` button to create dynamic values.
+
+### **Advanced (Optional)**
+
+You can click on the blue "Advanced" text to open up this section, which enables you to directly access or modify specific parts of complex data structures, such as arrays or objects, associated with the Metadata key. This is designed for advanced users already familiar with property paths.
+Most users can skip this section.
+
+This is used for accessing or modifying specific parts of complex data structures like arrays or objects. Most users can skip this section, but here’s a quick overview:
+
+- **Array Example:** `["apple", "banana", "cherry"]`  
+  Access "banana" with `$$myArray[1]`.
+
+- **Object Example:** `{"fruit":"apple", "color":"red"}`  
+  Access "apple" with `$$myObject[fruit]`.
+
+- **Array of Objects Example:**  
+  `[{"fruit":"apple"}, {"fruit":"banana"}]`  
+  Access "apple" with `$$myArray[0, fruit]`.
+
+You can use the Property Path field to update a specific part of the variable without overwriting the entire structure.
+
+<Note type="info">
+    **Example**: To change the color of a fruit from red to yellow in `{"fruit":"apple", "color":"red"}`, set `Variable Name` to your object’s name, `Variable Data` to `yellow`, and `Property Path` to `color`.
+</Note>
+
+## **Accessing and Using Metadata**
+
+Metadata is accessed using the `$userMetadata` replace variable.
+
+*   `$userMetadata[key]`
+*   `$userMetadata[key, propertyPath]`
+
+<Note type="info">
+  **Example:** Once you have used a `Set User Metadata` effect to set the user data for one of your viewers you can use `$userMetadata[key]` to display a viewer's favorite color, if for example you saved the metadata as "favouriteColor" you would set  `Key` to `favoriteColor`, and use `$userMetadata[favoriteColor]` in a chat message or overlay effect.
+</Note>
+
+## Example: Tracking Viewer Stats
+
+**Premise:** Suppose you want to keep track of how many times a viewer has checked into your stream.
+
+1.  **Add Set User Metadata Effect to Check In:** Set up your check in, either with a new command or a channel reward, and add a "Set User metadata" effect. 
+2.  **Set Up The Metadata Effect:**
+
+    *   `Username`: `$user` (This ensures the metadata is stored for the user who triggered the command/reward)
+    *   `Metadata Key`: `checkInCount`
+    *   `Data`: `$numberMath[$userMetadata[checkInCount] + 1]`
+
+    Every time this event is triggered, the user's `checkInCount` will increase by one.
+3.  **Display the Stat:** In a chat message or overlay effect, use the following:
+
+    *   `$userMetadata[$username, checkInCount]`
+
+    This will display the number of times the user has triggered the command or reward.
+
+    ## Viewing and Managing Metadata
+
+    You can view and manage metadata stored for a user by going to the "VIEWERS" tab in Firebot, selecting a viewer and looking at the "METADATA" table available there. You can see what metadata has been stored on the viewer, what the keys are to that data, and the data itself. You can also edit or delete metadata directly from this table. 
\ No newline at end of file
diff --git a/src/navigation.ts b/src/navigation.ts
index bf614ee..ef7cf2f 100644
--- a/src/navigation.ts
+++ b/src/navigation.ts
@@ -13,8 +13,8 @@ export const nav: Array<NavGroup> = [
         links: [
             { title: 'Effects', href: '/v5/core/effects' },
             { title: 'Commands', href: '/v5/core/commands' },
-            { title: 'Events', href: '/events' },
-            { title: 'Timers', href: '/timers' },
+            { title: 'Events', href: '/v5/core/events' },
+            { title: 'Timers And Scheduled Effects', href: '/v5/core/timers' },
             { title: 'Channel Rewards', href: '/channel-rewards' },
             { title: 'Preset Effect Lists', href: '/preset-effect-lists' },
             { title: 'Hotkeys', href: '/hotkeys' },
@@ -27,12 +27,13 @@ export const nav: Array<NavGroup> = [
     {
         title: 'Guides',
         links: [
-            { title: 'Alert Queues', href: '/guides/alert-queues' },
+            { title: 'Effect Queues', href: '/v5/guides/effect-queues' },
             { title: 'Conditional Effects', href: '/v5/guides/conditional-effects' },
             { title: 'Time Variables', href: '/v5/guides/time-variable' },
             { title: 'Custom Variables', href: '/v5/guides/custom-variables' },
             { title: 'Evaluate JavaScript', href: '/v5/guides/evaluate-javascript' },
             { title: 'Manual Restore', href: '/v5/guides/manual-restore' },
+            { title: 'Metadata', href: '/v5/guides/metadata' },
         ],
     },
     {