Skip to content

revamp: migrate Node.js (Express) backend API quickstart to new content model#996

Open
arpit-jn wants to merge 1 commit intomainfrom
refactor/backend-nodejs-quickstart
Open

revamp: migrate Node.js (Express) backend API quickstart to new content model#996
arpit-jn wants to merge 1 commit intomainfrom
refactor/backend-nodejs-quickstart

Conversation

@arpit-jn
Copy link
Copy Markdown
Contributor

Description

Migrates the Node.js (Express) backend API quickstart from the old Recipe/Section multi-file format to the new single index.mdx content model, matching the pattern established by backend/fastify.

What changed:

  • Replaced 5 files (_index.mdx, index.mdx, interactive.mdx, 02-using.mdx, 03-troubleshooting.mdx) with a single consolidated index.mdx
  • New format includes: mode: wide, AI accordion (defaultOpen), <Steps> component, <Check> checkpoint, <AccordionGroup> troubleshooting, and <Accordion> advanced usage sections
  • Updated docs.json navigation from nodejs/interactive to nodejs/index
  • Added redirect from /docs/quickstart/backend/nodejs/interactive/docs/quickstart/backend/nodejs
  • Localized versions (fr-ca, ja-jp) left untouched

References

Testing

  • Built sample Express API from the documented code — public endpoint returns 200, private endpoint returns 401 without token
  • Verified page renders on mint dev at /docs/quickstart/backend/nodejs (HTTP 200)
  • Verified old /interactive URL redirects correctly (HTTP 307)

Checklist

  • I've read and followed CONTRIBUTING.md.
  • I've tested the site build for this change locally.
  • I've made appropriate docs updates for any code or config changes.
  • I've coordinated with the Product Docs and/or Docs Management team about non-trivial changes.

@arpit-jn arpit-jn requested review from a team as code owners April 21, 2026 11:28
@mintlify
Copy link
Copy Markdown
Contributor

mintlify Bot commented Apr 21, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
auth0 🟢 Ready View Preview Apr 21, 2026, 11:35 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@github-actions
Copy link
Copy Markdown

Summary

Status Count
🔍 Total 14
✅ Successful 10
⏳ Timeouts 0
🔀 Redirected 2
👻 Excluded 2
❓ Unknown 0
🚫 Errors 0
⛔ Unsupported 0

Redirects per input

Redirects in main/docs/quickstart/backend/nodejs/index.mdx

@arpit-jn arpit-jn changed the title revamp: migrate Node.js (Express) backend API quickstart to new conte… revamp: migrate Node.js (Express) backend API quickstart to new content model Apr 24, 2026
AUTH0_AUDIENCE=YOUR_API_IDENTIFIER
```

<Warning>
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CLI tab uses to explain what the command does, while the Dashboard tab uses to remind users to replace placeholder values

A few things to fix here -

  1. should be on dashboard tab
  2. The placeholder reminder is missing from the CLI tab, even though both tabs show the same .env with YOUR_AUTH0_DOMAIN and YOUR_API_IDENTIFIER, so basically the warning tag should be there for both CLI and dashboard tab, with Warning change to Note
  3. The CLI (what the command does) sits after the .env block but describes the command, it should be move to right after

"dependencies": {
"dotenv": "^16.3.1",
"express": "^4.21.0",
"express-oauth2-jwt-bearer": "^1.6.0"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a small suggestion, instead of showing the full package.json, we could show only the scripts block that needs to be added, since npm install already handles writing the dependencies. Also, if we do want to keep the full file, could we update express-oauth2-jwt-bearer to ^1.8.0 (current version)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants