Skip to content

Commit d19330f

Browse files
Force Vercel static framework preset for MkDocs
Co-authored-by: RQM Technologies <RQM-Technologies-dev@users.noreply.github.com>
1 parent 1ee6640 commit d19330f

2 files changed

Lines changed: 5 additions & 1 deletion

File tree

README.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,11 +45,14 @@ Build output is written to `site/`.
4545

4646
This repository is configured for static publishing on Vercel.
4747

48+
- **Framework preset:** `Other` (explicitly disable framework auto-detection)
4849
- **Install command:** `pip install -r requirements.txt`
4950
- **Build command:** `mkdocs build --strict`
5051
- **Output directory:** `site`
5152

52-
Connect this repository in Vercel and use standard static project settings. The `vercel.json` file in this repository encodes the expected build posture.
53+
The repository `vercel.json` pins this behavior with `"framework": null`, which maps to Vercel's **Other** framework preset and prevents Python backend entrypoint checks.
54+
55+
If the project was previously configured as Python in the Vercel dashboard, update it to **Framework Preset = Other** and trigger a redeploy.
5356

5457
---
5558

vercel.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
{
22
"$schema": "https://openapi.vercel.sh/vercel.json",
3+
"framework": null,
34
"installCommand": "pip install -r requirements.txt",
45
"buildCommand": "mkdocs build --strict",
56
"outputDirectory": "site"

0 commit comments

Comments
 (0)