Skip to content

docs: improve configuration page structure and terminology#3039

Open
bartlomieju wants to merge 1 commit intomainfrom
docs/config-page-improvements-2673
Open

docs: improve configuration page structure and terminology#3039
bartlomieju wants to merge 1 commit intomainfrom
docs/config-page-improvements-2673

Conversation

@bartlomieju
Copy link
Copy Markdown
Member

Summary

  • Reframes package.json support as a :::note callout instead of a top-level section — positions it as "Node.js projects work out-of-the-box" rather than equal to deno.json
  • Uses code tags in section titles to match deno.json field keys (e.g., "imports", "tasks", "fmt", "lock", "compilerOptions", etc.)
  • Simplifies the proxies section into a brief note linking to the environment variables reference

Based on feedback from @nayeemrmn.

Closes #2673

Test plan

  • Verify section headings render correctly with code tags
  • Verify the :::note callout renders properly
  • Check that anchor links still work (or update any internal references)

🤖 Generated with Claude Code

- Reframe package.json support as a note rather than a top-level section,
  emphasizing that Node.js projects work out-of-the-box
- Use code tags in section titles to match deno.json field keys
  (e.g., `"imports"`, `"tasks"`, `"fmt"`)
- Simplify proxies section to a brief note linking to env variables

Closes #2673

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.

Feedback: /runtime/fundamentals/configuration/ - Positive

1 participant