add info about getting basehub set up in the intstallation doc (#361)

haydenbleasel · Dec 17, 2024 · 082922c · 082922c
1 parent 9887e25
commit 082922c
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 2 deletions.
diff --git a/docs/features/cms.mdx b/docs/features/cms.mdx
@@ -38,11 +38,11 @@ By default, next-forge uses [BaseHub](https://basehub.com) as the CMS. However,
 
 Here's how to quickly get started with your new CMS.
 
-### 1. Fork the [`basehub/next-forge`](https://basehub.com/basehub/next-forge) template
+### 1. Fork the [`basehub/next-forge`](https://basehub.com/basehub/next-forge?fork=1) template
 
 You'll be forking a BaseHub repository which contains the next-forge compatible content schema.
 
-Once you fork the repository, you'll need to get your Read Token from the Connect page:
+Once you fork the repository, you'll need to get your Read Token from the "Connect to your App" page:
 
 ```
 https://basehub.com/<team-slug>/<repo-slug>/dev/main/dev:connect

diff --git a/docs/setup/installation.mdx b/docs/setup/installation.mdx
@@ -45,6 +45,14 @@ You will need to scaffold the database using the schema defined in `packages/dat
 pnpm migrate
 ```
 
+## CMS
+
+You will need to setup the CMS. Follow the instructions [here](/features/cms), but the summary is:
+
+1. Fork the [`basehub/next-forge`](https://basehub.com/basehub/next-forge?fork=1) template
+2. Get your Read Token from the "Connect to Your App" page
+3. Add the `BASEHUB_TOKEN` to your [Environment Variables](/features/env)
+
 ## Development
 
 Run the development server with: