diff --git a/pages/suzyqboard/accessing-ccd.mdx b/pages/suzyqboard/accessing-ccd.mdx
new file mode 100644
index 0000000..d8a35b5
--- /dev/null
+++ b/pages/suzyqboard/accessing-ccd.mdx
@@ -0,0 +1,7 @@
+---
+title: Accessing Closed Case Debugging
+description: Access Closed Case Debugging (CCD) using the SuzyQ Board
+---
+
+When Accessing Closed Case Debugging, the SuzyQ Board is no different then using any other SuzyQable. Just follow [MrChromebox's WP disabling page](https://docs.mrchromebox.tech/docs/firmware/wp/disabling.html).
+If you want to dive deeper, [Google's CCD documentation](https://chromium.googlesource.com/chromiumos/platform/ec/+/cr50_stab/docs/case_closed_debugging_gsc.md) is a great resource.
diff --git a/pages/suzyqboard/flash-firmware.mdx b/pages/suzyqboard/flash-firmware.mdx
new file mode 100644
index 0000000..0a4f738
--- /dev/null
+++ b/pages/suzyqboard/flash-firmware.mdx
@@ -0,0 +1,10 @@
+---
+title: Flashing Firmware
+description: Flash Firmware using the SuzyQ Board
+---
+
+When Flashing Firmware, the SuzyQ Board is no different then using a SuzyQable. Check out [MrChromebox's page on flashing firmware](https://docs.mrchromebox.tech/docs/firmware/manual-flashing.html).
+
+Note that this WILL work on Ultramarine and Fedora. Grab the `flashrom` package from Fedora repositories, and `cbfstool` from [Terra](https://terra.fyralabs.com/).
+
+For other distros/package manaagers, check out [flashrom packaging on Repology](https://repology.org/project/flashrom/versions), and [cbfstool packaging on Repology](https://repology.org/project/coreboot/versions) (note that the package must include `cbfstool`).
diff --git a/pages/suzyqboard/index.mdx b/pages/suzyqboard/index.mdx
index c1faec9..ae3cdb2 100644
--- a/pages/suzyqboard/index.mdx
+++ b/pages/suzyqboard/index.mdx
@@ -4,3 +4,49 @@ description: Learn about using the Fyra SuzyQ Board to hack your Chromebook
 ---
 
 # Introduction
+
+The SuzyQ Board is an open-source Chromebook debug board. It's a versatile tool for Chromebook hacking and debugging. This board works exactly like a [Google SuzyQable](https://chromium.googlesource.com/chromiumos/third_party/hdctools/+/master/docs/ccd.md#suzyq-suzyqable). Any guides or documentation you find elsewhere on using 'SuzyQables' will work with the Fyra Labs SuzyQ Board.
+
+Huge shoutout to the [Chrultrabook Project](https://docs.chrultrabook.com/) for their help in building this product.
+
+## FAQ
+
+### Does My Chromebook Support Using a SuzyQ Board?
+
+Please refer to [this list](https://www.chromium.org/chromium-os/developer-library/reference/development/developer-information-for-chrome-os-devices/), if your device supports Closed Case Debugging (CCD), it will support our SuzyQ Board.
+
+### Where Can I Purchase a SuzyQ Board?
+
+You can buy a SuzyQ Board [from the Fyra Shop](https://fyralabs.com/FDS010) - COMING VERY SOON.
+
+### How Do I Connect This Up?
+
+The SuzyQ USB-C connector goes into the CCD port of your Chromebook.
+You must provide a USB cable that can carry data to attach to the USB-C port of the SuzyQ Board.
+This can be either a USB-C to USB-A or USB-C to USB-C cable.
+The side of the cable not plugged into the SuzyQ Board will attach to your Linux device.
+
+### Where Are the Schematics?
+
+* [Online schematics view on PCBhub](https://pcbhub.org/projects/53)
+* [GitHub repo](https://github.com/FyraLabs/suzyqboard)
+
+### Where Can I Get Help?
+
+If you need support with anything that may be an issue with the Fyra SuzyQ board, please join our [Discord server](https://fyralabs.com/discord) and hop into our support forum channel.
+If you have purchasing trouble, please email `contact@fyralabs.com`.
+If you need support with what you're actually doing with the SuzyQ Board, and you're SURE it is not an issue with the board, your question will probably be best answered in the [Chrultrabook Forum](https://forum.chrultrabook.com/).
+
+### What’s With the Case?
+
+The case is to ensure the USB-C connector does not snap off if too much force is applied.
+The case is 3D printed, and snaps onto the board with its top and bottom piece.
+
+We HIGHLY RECOMMEND leaving the case on!
+However, you can remove it pretty easily by wedging something thin between the top and bottom piece, but again, you SHOULD leave it on!
+
+### What Does FDS010 Mean?
+
+| Fyra | Category | Product | Version | Revision |
+|------|----------|---------|---------------|---------------|
+| Fyra | Developer Tools | SuzyQ |  01 | 0 |
diff --git a/pages/suzyqboard/unbricking.mdx b/pages/suzyqboard/unbricking.mdx
new file mode 100644
index 0000000..8ca9f17
--- /dev/null
+++ b/pages/suzyqboard/unbricking.mdx
@@ -0,0 +1,10 @@
+---
+title: Unbricking
+description: Unbrick your ChromeOS Device using the SuzyQ Board
+---
+
+When Unbricking, the SuzyQ Board is no different then using a SuzyQable. Follow [MrChromebox's Unbricking page](https://docs.mrchromebox.tech/docs/support/unbricking/unbrick-suzyq.html).
+
+Note that this WILL work on Ultramarine and Fedora. Grab the `flashrom` package from Fedora repositories, and `cbfstool` from [Terra](https://terra.fyralabs.com/).
+
+For other distros/package manaagers, check out [flashrom packaging on Repology](https://repology.org/project/flashrom/versions), and [cbfstool packaging on Repology](https://repology.org/project/coreboot/versions) (note that the package must include `cbfstool`).