diff --git a/docs/docs-next/docs/partials/_InspirationList.md b/docs/docs-next/docs/partials/_InspirationList.md
new file mode 100644
index 0000000000000..ba76d609c3c9a
--- /dev/null
+++ b/docs/docs-next/docs/partials/_InspirationList.md
@@ -0,0 +1,7 @@
+## Want more inspiration?
+
+If you're looking for additional inspiration, we recommend:
+
+- [**Dagster Open Platform**](https://github.com/dagster-io/dagster-open-platform), which is Dagster Lab's open-source data platform. This full-sized project contains real assets and other Dagster features used by the Dagster Labs team.
+- [**GitHub Discussions**](https://github.com/dagster-io/dagster/discussions), where you can ask questions and get inspired by the Dagster community
+- [**The Awesome Dagster repository**](https://github.com/dagster-io/awesome-dagster), which is a collection of all awesome things related to Dagster, including other users' projects, talks, articles, and more
\ No newline at end of file
diff --git a/docs/docs-next/src/templates/concept.md b/docs/docs-next/src/templates/concept.md
new file mode 100644
index 0000000000000..79f5b515a53a5
--- /dev/null
+++ b/docs/docs-next/src/templates/concept.md
@@ -0,0 +1,96 @@
+---
+title: ""
+description: ""
+---
+
+# [TOPIC]
+
+<!-- This section is an intro that includes:
+
+- A brief description of what the topic is,
+- An example of how it could be used in the real-world
+- What it can do in the UI
+ -->
+
+---
+
+## Benefits
+
+<!-- This section lists the benefits of using the topic, whatever it is. The items listed here should be solutions to real-world problems that the user cares about, ex:
+
+Using schedules helps you:
+
+- Predictably process and deliver data to stakeholders and business-critical applications
+- Consistently run data pipelines without the need for manual intervention
+- Optimize resource usage by scheduling pipelines to run during off-peak hours
+-->
+
+Using [TOPIC] helps you:
+
+<!-- - A benefit of the thing
+- Another benefit
+- And one more -->
+
+---
+
+## Prerequisites
+
+<!-- This section lists the prerequisites users must complete before they should/can proceed. For concepts, we should list the other concepts they should be familiar with first. -->
+
+Before continuing, you should be familiar with:
+
+<!-- - Ex: To use asset checks, users should understand Asset definitions first
+- Another one
+- One more -->
+
+---
+
+## How it works
+
+<!-- This section provides a high-level overview of how the concept works without getting too into the technical details. Code can be shown here, but this section shouldn't focus on it. The goal is to help the user generally understand how the thing works and what they need to do to get it working without overwhelming them with details.
+
+For example, this is the How it works for Schedules:
+
+Schedules run jobs at fixed time intervals and have two main components:
+
+- A job, which targets a selection of assets or ops
+
+- A cron expression, which defines when the schedule runs. Simple and complex schedules are supported, allowing you to have fine-grained control over when runs are executed. With cron syntax, you can:
+
+   - Create custom schedules like Every hour from 9:00AM - 5:00PM with cron expressions (0 9-17 * * *)
+   - Quickly create basic schedules like Every day at midnight with predefined cron definitions (@daily, @midnight)
+
+   To make creating cron expressions easier, you can use an online tool like Crontab Guru. This tool allows you to create and describe cron expressions in a human-readable format and test the execution dates produced by the expression. Note: While this tool is useful for general cron expression testing, always remember to test your schedules in Dagster to ensure the results are as expected.
+
+For a schedule to run, it must be turned on and an active dagster-daemon process must be running. If you used dagster dev to start the Dagster UI/webserver, the daemon process will be automatically launched alongside the webserver.
+
+After these criteria are met, the schedule will run at the interval specified in the cron expression. Schedules will execute in UTC by default, but you can specify a custom timezone.
+
+-->
+
+---
+
+## Getting started
+
+<!-- This section is a list of guides / links to pages to help the user get started using the topic. -->
+
+Check out these guides to get started with [CONCEPT]:
+
+From here, you can:
+
+<!-- A list of things the user can do once they've got the basics down. These could be links to additional guides, ex:
+
+- Construct schedules to run partitioned jobs
+- Execute jobs in specific timezones
+- Learn to test your schedules
+- Identify and resolve common issues with our troubleshooting guide -->
+
+### Limitations [and notes]
+
+<!-- This section should describe any known limitations that could impact the user, ex: "Schedules will execute in UTC unless a timezone is specified" -->
+
+---
+
+## Related
+
+<!-- A list of related links and resources -->
\ No newline at end of file
diff --git a/docs/docs-next/src/templates/example-reference.md b/docs/docs-next/src/templates/example-reference.md
new file mode 100644
index 0000000000000..09f4df9301e20
--- /dev/null
+++ b/docs/docs-next/src/templates/example-reference.md
@@ -0,0 +1,44 @@
+---
+title: "[TOPIC] example reference"
+description: ""
+---
+
+# [TOPIC] examples
+
+This reference contains a variety of examples using Dagster [TOPIC]. Each example contains:
+
+- A summary
+- Additional notes
+- Links to relevant documentation
+- A list of the APIs used in the example
+
+---
+
+## [Title of example]
+
+[This example demonstrates [description of what the example accomplishes]
+
+<!-- Example: This example demonstrates how to use resources in schedules. To specify a resource dependency, annotate the resource as a parameter to the schedule's function. -->
+
+```python title="my_schedule.py"
+@schedule(job=my_job, cron_schedule="* * * * *")
+def logs_then_skips(context):
+    context.log.info("Logging from a schedule!")
+    return SkipReason("Nothing to do")
+```
+
+<!-- We need to fix the base table implemenatation before launch. This is a must. -->
+
+| | |
+|-|-|
+| Notes | |
+| Related docs | |
+| APIs in this example | |
+
+---
+
+<!-- This section lists a few additional sources of inspiration, such as DOP and GitHub discussions. You shouldn't need to change anything here. -->
+
+import InspirationList from '../partials/_InspirationList.md';
+
+<InspirationList />
\ No newline at end of file
diff --git a/docs/docs-next/src/templates/guide.md b/docs/docs-next/src/templates/guide.md
new file mode 100644
index 0000000000000..ced99f32d16ff
--- /dev/null
+++ b/docs/docs-next/src/templates/guide.md
@@ -0,0 +1,49 @@
+---
+title: ""
+description: ""
+---
+
+# [Title that briefly describes what the guide is for]
+
+<!-- This section is a brief introduction into the guide's topic. -->
+
+By the end of this guide, you will [a sentence or list about what will be achieved by the end of the guide].
+
+---
+
+## Prerequisites
+
+<!-- This section lists the prerequisites users must complete before they should/can proceed with the guide. -->
+
+To follow the steps in this guide, you'll need:
+
+- A prerequisite, ex: "Familiarity with Asset definitions"
+- Another prerequisite, ex: "To install <this> library"
+- One more
+
+---
+
+## Step 1: Title that describes what this step will do {#step-1}
+
+<!-- 
+For section / step heaings:
+
+- Titles should describe an action, ex: "Generate a token"
+- Don't use gerunds (-ing) in titles, as it can cause issues with translation + SEO 
+- Each section heading should have an ID that includes the word 'step' and the number of the step, ex: {#step-1}
+-->
+
+### Step 1.1: Title that describes a substep {#step-1-1}
+
+<!-- - If a step would benefit by being broken into smaller steps, follow this section's formatting
+- Each substep should get an H3 and start with Step N., followed by the number of the substep -->
+
+---
+
+## Step 2: Another step {#step-2}
+
+---
+
+## Related
+
+[List of links to related content]
\ No newline at end of file