diff --git a/.github/workflows/assets/root-dir.png b/.github/workflows/assets/root-dir.png
new file mode 100644
index 0000000000..081aaa7e08
Binary files /dev/null and b/.github/workflows/assets/root-dir.png differ
diff --git a/.github/workflows/solidity.md b/.github/workflows/solidity.md
new file mode 100644
index 0000000000..6bdb3341db
--- /dev/null
+++ b/.github/workflows/solidity.md
@@ -0,0 +1,17 @@
+# Configuring a New Vercel Project for Solidity Documentation
+
+Since we're using Vercel via github actions rather than the UI, configuring a new project requires a little extra work.
+
+1. Click "Add New" on the home screen.
+2. The project creation page will force you to import a project from github. Select any non-private repo, as this will be disconnected later.
+![create project](./assets/vercel-create-project.png)me
+3. Go to the settings->git and disconnect the repo.
+![disconnect repo](./assets/vercel-git-page.png)
+4. Get the project id from vercel.
+![project id](./assets/vercel-project-id.png)
+5. Set the root directory to the path in the repo where your package is located + docs
+![root directory](./assets/root-dir.png)
+6. [Add this variable as a secret to github actions](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository). As a convention this should be called `VERCEL_[PACKAGE_NAME]_DOCS_PROJECT_ID` (e.g. `VERCEL_CONTRACT_DOCS_PROJECT_ID` for contracts-core).
+7. Add the project id to the PROJECT_IDS mapping in [solidity.yml](./solidity.yml) under the "Get Project ID" step.
+
+Now you're done. Any time you push to the main branch, the Solidity documentation will be deployed to vercel.