diff --git a/internal/website/docs/getting-started.mdx b/internal/website/docs/getting-started/setting-up-wordpress.mdx
similarity index 61%
rename from internal/website/docs/getting-started.mdx
rename to internal/website/docs/getting-started/setting-up-wordpress.mdx
index d25b788ee..20d0cb632 100644
--- a/internal/website/docs/getting-started.mdx
+++ b/internal/website/docs/getting-started/setting-up-wordpress.mdx
@@ -1,9 +1,11 @@
-# Getting Started
+# Setting Up WordPress
 
-## Prerequisites
+## WordPress
 
 To create a headless WordPress site, you'll first need a WordPress instance! If you don't already have one, we recommend [Local](https://localwp.com/) to try things out locally, or you can use a live WordPress site.
 
+## Plugins
+
 You'll also need to download/activate two plugins for your WordPress site:
 
 1. Download, upload, and activate the `wpe-headless` plugin. [(Download)](https://wp-product-info.wpesvc.net/v1/plugins/wpe-headless?download)
@@ -19,8 +21,14 @@ The plugin ensures that your WordPress site runs smoothly as a headless CMS. Fro
 
 [WP GraphQL](https://wordpress.org/plugins/wp-graphql/) turns your WordPress site into a fully queryable GraphQL API. We use this API to communicate with the frontend.
 
+### Set your headless frontend URL
+
+Now that you have the plugins installed, navigate to Settings -> Headless and set your Front-end site URL. This is the URL where your frontend will live. For local development this will usually be something like `http://localhost:3000` or `http://localhost:8000`.
+
+<img src="/docs/img/frontend-site-url-settings.png" alt="The Headless WordPress admin interface with a red rectangle around the front-end site URL field" />
+
 ## Usage
 
-We've made examples for you to easily get started with the frontend framework of your choice:
+Now that you have WordPress setup to support headless, you can now use the framework! We've made guides to easily get you started with the frontend framework of your choice:
 
 - [Usage with Next.js](/next/getting-started)
\ No newline at end of file
diff --git a/internal/website/docs/guides/custom-post-types.mdx b/internal/website/docs/guides/custom-post-types.mdx
new file mode 100644
index 000000000..aec43e163
--- /dev/null
+++ b/internal/website/docs/guides/custom-post-types.mdx
@@ -0,0 +1,258 @@
+# Interacting with custom post types
+
+Querying data in custom post types is just as easy as querying for posts or pages in the framework.
+
+Before we start, if you haven't already, [setup your WordPress site for headless](/getting-started/setting-up-wordpress).
+
+## Create a custom post type
+
+We'll be using the [Atlas Content Modeler](https://github.com/wpengine/atlas-content-modeler) plugin to create custom post types for this guide, but you can choose to create your custom post types in any way you'd like.
+
+Atlas Content Modeler is a WordPress plugin to create custom post types and fields for headless WordPress sites. Start by downloading the plugin and activating it on your WordPress site [(Download)](https://wp-product-info.wpesvc.net/v1/plugins/atlas-content-modeler?download)
+
+Now, navigate to WP Admin -> Content Modeler.
+
+<img src="/docs/img/empty-content-modeler.png" alt="The Atlas Content Modeler admin interface" />
+
+Let's create a custom post type for our team members. Click the "Get Started" button, and fill out the fields to create a new Content Model. Be sure to mark "API Visibility" to "Public" so we can query the data.
+
+<img src="/docs/img/team-members-content-modeler.png" alt="The Atlas Content Modeler admin interface with fields for a team member content type" />
+
+## Create fields for your custom post type
+
+Now, that we've created our custom post type, let's add some fields to it. From WP Admin -> Content Modeler, select the Team Members custom post type.
+
+We'll add three fields:
+
+1. A Media field type. The name will be "Profile Pic" and the API identifier "profilePic"
+2. A Text field type. The name will be "Full Name" and the API identifier "fullName". We'll also select "Use this field as the entry title"
+3. A Rich Text field type. The name will be "Bio" and the API identifier "bio".
+
+<img src="/docs/img/team-members-content-modeler-fields.png" alt="The Atlas Content Modeler admin interface with filled custom fields" />
+
+## Create some team members
+
+Now that you have created a custom post type and fields, you can start entering data. Navigate to WP Admin -> Team Members to start creating!
+
+For this example, I've created two team members, Jane and Jonh Doe, with bios and profile pics:
+
+<img src="/docs/img/content-modeler-add-team-member.png" alt="Atlas Content Modeler Custom Post Type interface for adding a new item" />
+
+## Create your starter headless project
+
+From here, you have your WordPress site setup with the necessary headless plugins, and data. Now, we need to create a frontend app to consume this data.
+
+We are going to use a starter project in Next.js, but the same concepts apply in other frontend frameworks.
+
+[Follow the steps in our Getting started with Next.js usage guide to create a frontend app.](/next/getting-started)
+
+Once your frontend app is created, the structure should look something like this:
+
+```
+my-app/
+  src/
+    client/
+      ..
+    pages/
+      ..
+    components/
+      ..
+    scss/
+      ..
+  public/
+  .env.local
+  .env.local.sample
+  .env.test.sample
+  .eslintrc
+  .gitignore
+  gqless.config.js
+  next-env.d.ts
+  package.json
+  README.md
+  tsconfig.json
+```
+
+### Regenerate your schema
+
+Your schema is a TypeScript representation of your WordPress site. Since we have added some custom post types and fields, we'll want to regenerate this schema to ensure it's up to date. To regenerate your schema from the Next.js starter, simply run:
+
+```bash
+npm run generate
+```
+
+[Learn more about generating your client/schema](next/generating-client)
+
+### Run the dev server
+
+Run the following command to start the dev server:
+
+```bash
+npm run dev
+```
+
+You should now be able to access the starter project at [http://localhost:3000](http://localhost:3000)
+
+### Create a team page
+
+We'll create a team page in `src/pages/team.tsx` to display our team members:
+
+```tsx title="src/pages/team.tsx"
+import Head from 'next/head';
+import { Header, Footer } from '../components';
+import { client } from '../client';
+
+export default function Team() {
+  const { useGeneralSettings } = client;
+  const generalSettings = useGeneralSettings();
+
+  return (
+    <>
+      <Header
+        title={generalSettings.title}
+        description={generalSettings.description}
+      />
+
+      <Head>
+        <title>Custom Page - {generalSettings.title}</title>
+      </Head>
+
+      <main className="content content-single">
+        <div className="wrap">
+          <h2>Team Members</h2>
+        </div>
+      </main>
+
+      <Footer copyrightHolder={generalSettings.title} />
+    </>
+  );
+}
+```
+
+This will look something like:
+
+<img src="/docs/img/nextjs-empty-team-members-page.png" alt="An empty web page with a large title for team members" />
+
+### Query for team members
+
+When querying for custom post types, you can leverage the `useQuery` hook that is exported from the client. This allows you to access all of WordPress' data. You'll also notice it's typed from your schema, making things super easy to find.
+
+<img src="/docs/img/useQuery-typed.png" alt="A screenshot of the useQuery hook and its typings" />
+
+Let's get our team members using the `useQuery` hook:
+
+```tsx title="src/pages/team.tsx" {6,8}
+import Head from 'next/head';
+import { Header, Footer } from '../components';
+import { client } from '../client';
+
+export default function Team() {
+  const { useGeneralSettings, useQuery } = client;
+  const generalSettings = useGeneralSettings();
+  const teamMembers = useQuery().teamMembers()?.nodes;
+
+  return (
+    <>
+      <Header
+        title={generalSettings.title}
+        description={generalSettings.description}
+      />
+
+      <Head>
+        <title>Custom Page - {generalSettings.title}</title>
+      </Head>
+
+      <main className="content content-single">
+        <div className="wrap">
+          <h2>Team Members</h2>
+        </div>
+      </main>
+
+      <Footer copyrightHolder={generalSettings.title} />
+    </>
+  );
+}
+```
+
+Finally, we'll create a `teamMember.tsx` component to display each team member:
+
+```tsx title="/src/components/teamMember.tsx"
+import { TeamMember as TeamMemberType } from 'client';
+
+interface TeamMemberProps {
+  teamMember: TeamMemberType;
+}
+
+export default function TeamMember({ teamMember }: TeamMemberProps) {
+  return (
+    <div>
+      <img
+        src={teamMember?.profilePic.mediaItemUrl}
+        alt={teamMember?.profilePic?.altText}
+      />
+      <h2>{teamMember?.fullName}</h2>
+      <div
+        className="bio"
+        dangerouslySetInnerHTML={{ __html: teamMember?.bio }}
+      />
+    </div>
+  );
+}
+```
+
+Notice how we are getting the `TeamMember` type from the client and generated schema.
+
+### Put it all together
+
+Finally, let's hook up our `TeamMember` component to the Team page.
+
+```tsx title="src/pages/team.tsx" {4,27-29}
+import Head from 'next/head';
+import { Header, Footer } from '../components';
+import { client } from '../client';
+import TeamMember from '../components/teamMember';
+
+export default function Team() {
+  const { useGeneralSettings, useQuery } = client;
+  const generalSettings = useGeneralSettings();
+
+  const teamMembers = useQuery().teamMembers()?.nodes;
+
+  return (
+    <>
+      <Header
+        title={generalSettings.title}
+        description={generalSettings.description}
+      />
+
+      <Head>
+        <title>Meet the Team - {generalSettings.title}</title>
+      </Head>
+
+      <main className="content content-single">
+        <div className="wrap">
+          <h2>Team Members</h2>
+
+          {teamMembers.map((teamMember) => (
+            <TeamMember key={teamMember.id} teamMember={teamMember} />
+          ))}
+        </div>
+      </main>
+
+      <Footer copyrightHolder={generalSettings.title} />
+    </>
+  );
+}
+```
+
+Now, head back over to [http://localhost:3000/team](http://localhost:3000/team) to see your WordPress data come to life!
+
+<img src="/docs/img/nextjs-team-page.png" alt="A web page with a list of team members" />
+
+## Learnings
+
+In this guide, we demonstrated:
+
+* How to create custom post types/fields using Atlas Content Modeler
+* Creating data for your custom post types
+* Creating a starter frontend project to consume your WordPress data
+* Using the `useQuery` custom React hook in the framework to query your custom post type data in GraphQL
diff --git a/internal/website/sidebars.js b/internal/website/sidebars.js
index 32f95933b..8421ad47f 100644
--- a/internal/website/sidebars.js
+++ b/internal/website/sidebars.js
@@ -13,11 +13,17 @@ module.exports = {
   docsSidebar: [
     {
       type: 'doc',
-      id: 'introduction'
+      id: 'introduction',
     },
     {
-      type: 'doc',
-      id: 'getting-started'
+      type: 'category',
+      label: 'Getting Started',
+      items: [
+        {
+          type: 'autogenerated',
+          dirName: 'getting-started',
+        },
+      ],
     },
     {
       type: 'category',
@@ -25,9 +31,19 @@ module.exports = {
       items: [
         {
           type: 'autogenerated',
-          dirName: 'next'
-        }
-      ]
-    }
-  ]
+          dirName: 'next',
+        },
+      ],
+    },
+    {
+      type: 'category',
+      label: 'Guides',
+      items: [
+        {
+          type: 'autogenerated',
+          dirName: 'guides',
+        },
+      ],
+    },
+  ],
 };
diff --git a/internal/website/static/docs/img/content-modeler-add-team-member.png b/internal/website/static/docs/img/content-modeler-add-team-member.png
new file mode 100644
index 000000000..da27ced46
Binary files /dev/null and b/internal/website/static/docs/img/content-modeler-add-team-member.png differ
diff --git a/internal/website/static/docs/img/empty-content-modeler.png b/internal/website/static/docs/img/empty-content-modeler.png
new file mode 100644
index 000000000..f0df90be4
Binary files /dev/null and b/internal/website/static/docs/img/empty-content-modeler.png differ
diff --git a/internal/website/static/docs/img/frontend-site-url-settings.png b/internal/website/static/docs/img/frontend-site-url-settings.png
new file mode 100644
index 000000000..d9502d1e0
Binary files /dev/null and b/internal/website/static/docs/img/frontend-site-url-settings.png differ
diff --git a/internal/website/static/docs/img/nextjs-empty-team-members-page.png b/internal/website/static/docs/img/nextjs-empty-team-members-page.png
new file mode 100644
index 000000000..f150fb9fc
Binary files /dev/null and b/internal/website/static/docs/img/nextjs-empty-team-members-page.png differ
diff --git a/internal/website/static/docs/img/nextjs-team-page.png b/internal/website/static/docs/img/nextjs-team-page.png
new file mode 100644
index 000000000..e1df9d638
Binary files /dev/null and b/internal/website/static/docs/img/nextjs-team-page.png differ
diff --git a/internal/website/static/docs/img/team-members-content-modeler-fields.png b/internal/website/static/docs/img/team-members-content-modeler-fields.png
new file mode 100644
index 000000000..05a1820b9
Binary files /dev/null and b/internal/website/static/docs/img/team-members-content-modeler-fields.png differ
diff --git a/internal/website/static/docs/img/team-members-content-modeler.png b/internal/website/static/docs/img/team-members-content-modeler.png
new file mode 100644
index 000000000..925aa2a5a
Binary files /dev/null and b/internal/website/static/docs/img/team-members-content-modeler.png differ
diff --git a/internal/website/static/docs/img/useQuery-typed.png b/internal/website/static/docs/img/useQuery-typed.png
new file mode 100644
index 000000000..c327ee634
Binary files /dev/null and b/internal/website/static/docs/img/useQuery-typed.png differ