+
diff --git a/docs/content/1.guide/0.getting-started.md b/docs/content/1.guide/0.getting-started.md
new file mode 100644
index 00000000..573c6d07
--- /dev/null
+++ b/docs/content/1.guide/0.getting-started.md
@@ -0,0 +1,11 @@
+---
+title: 'Getting Started'
+description: 'Answer a few questions about the devtool you want to build and get a reading list tailored to it.'
+---
+
+Devframe provides a lot of features to build DevTools with various needs. It could be overwhelming to start with. Here we have the wizard to help you get started. Answer a few questions about the devtool you want to build and get a reading list tailored to it.
+
+::getting-started-wizard
+::
+
+None of this is a required reading order. [`defineDevframe()`](/guide/devframe-definition) and [the tutorial](/guide/tutorial-server-data-inspector) are worth reading regardless of your answers above — everything else is additive.
diff --git a/docs/content/1.guide/index.md b/docs/content/1.guide/index.md
index 28065319..afd39123 100644
--- a/docs/content/1.guide/index.md
+++ b/docs/content/1.guide/index.md
@@ -19,6 +19,8 @@ Devframe moves that boundary. A capability is defined once against a stable inte
With a coding agent to scaffold the boilerplate, Devframe is also a fast foundation for standing up a bespoke, specific-need, or even one-off devtool.
+New here? [Answer a few questions about your devtool](/guide/getting-started) and get a reading list tailored to it.
+
## One definition, one standard handler
Every devframe starts with [`defineDevframe()`](/guide/devframe-definition), pairing a tool's identity with its capabilities.