Vercel Logo

Deploy Your Docs

The Vercel project from lesson 1.1 still contains the starter stubs. Push the API and documentation changes to update the deployment.

This lesson publishes and verifies those changes.

Outcome

Push your changes to redeploy the feedback API so your llms.txt, docs, and feedback endpoints are live at your public URL.

Fast Track

  1. Commit your changes and push to your repo
  2. Vercel redeploys automatically
  3. Curl your live /llms.txt, /api/docs.md, and /api/feedback endpoints to confirm they work

Push and redeploy

Since your project is already connected to Vercel from the deploy button in lesson 1.1, every push to main triggers a new deployment automatically. Commit your latest changes and push:

git add -A
git commit -m "feat: add feedback API, docs, and llms.txt endpoints"
git push

Open the Vercel dashboard to follow the build. When it finishes, the live URL will serve the new routes.

Try It

Replace the URL below with your deployment URL and verify each endpoint.

Fetch the llms.txt file:

curl https://your-project-name.vercel.app/llms.txt

You should see the plain-text markdown with the project name, summary blockquote, and links to your endpoints.

Fetch the API docs via the markdown endpoint:

curl https://your-project-name.vercel.app/api/docs.md

The full markdown documentation should come back with all the endpoint signatures, parameter tables, and examples.

Fetch some feedback:

curl https://your-project-name.vercel.app/api/feedback

You should see the JSON array of seed feedback entries.

Troubleshooting:

  • If you get a 404 on /llms.txt, check that the folder is named exactly llms.txt inside app/. The deployment mirrors your local file structure.
  • If the deploy fails with a build error, check the Vercel build logs for TypeScript errors. The production build runs next build, which is stricter than the dev server about type checking.
Data doesn't persist in production

The feedback data lives in a JSON file that gets read at runtime. Since Vercel Functions are serverless, any POST requests that write to that file won't persist across invocations. The function's filesystem resets on each cold start. This is fine for the course because the seed data is what matters for testing. In a real app, you'd use a database.

Commit

You already committed and pushed in the exercise above. If you made any additional fixes during troubleshooting, commit those too:

git add -A
git commit -m "fix: resolve build issues for production deploy"
git push

Done-When

  • Your latest code is pushed and Vercel has redeployed
  • Curling <your-url>/llms.txt returns the plain-text llms.txt content
  • Curling <your-url>/api/docs.md returns the full markdown API documentation
  • Curling <your-url>/api/feedback returns the seed feedback data as JSON

Solution

No new code is required for this lesson. Push triggers a redeploy:

git push

Vercel detects the Next.js App Router project without an additional configuration file. Confirm the deployment by testing the live routes rather than relying only on the local build.

Was this helpful?

supported.