Skip to content

Docs: Add Next.js Glossary#88811

Merged
delbaoliveira merged 9 commits into
canaryfrom
docs-glossary
Jan 23, 2026
Merged

Docs: Add Next.js Glossary#88811
delbaoliveira merged 9 commits into
canaryfrom
docs-glossary

Conversation

@delbaoliveira
Copy link
Copy Markdown
Contributor

@delbaoliveira delbaoliveira commented Jan 20, 2026

Add next.js glossary so we can reference concepts in guides without having to re-explain them. Guides should be succint, like a skill :)

Closes: https://linear.app/vercel/issue/DOC-5574/nextjs-glossary

@nextjs-bot nextjs-bot added created-by: Next.js DevEx team PRs by the DX team. Documentation Related to Next.js' official documentation. labels Jan 20, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 20, 2026

All broken links are now fixed, thank you!

Comment thread docs/01-app/glossary.mdx Outdated
Comment thread docs/01-app/glossary.mdx Outdated
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
Comment thread docs/01-app/glossary.mdx Outdated
Comment thread docs/01-app/glossary.mdx Outdated
Copy link
Copy Markdown
Member

@icyJoseph icyJoseph left a comment

Choose a reason for hiding this comment

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

I had a bunch of terms on my version, pasting here for completeness. We do mention these in the docs 10+ times:

"use client" directive: A special statement that marks the boundary between server and client code. It must be placed at the top of a file, before any imports or other code. It indicates that React Components, helper functions, variable declarations, and all imported dependencies should be included in the client bundle. Learn more about this directive.

Module Graphs: A graph of file dependencies in your app. Each file (module) is a node, and import/export relationships form the edges. Next.js analyzes this graph to determine optimal bundling and code-splitting strategies.

Client Bundles: JavaScript bundles sent to the browser. Next.js splits these automatically based on the module graph to reduce initial payload size and load only the necessary code for each page.

Catch-all segments: Dynamic route segments that can match multiple URL parts using the [...folder]/page.js syntax. These segments capture all remaining URL segments and are useful for implementing features like documentation sites or file browsers.

Private folders: Folders prefixed with an underscore (e.g., _components) that are excluded from the routing system. These folders are used for code organization and shared utilities without creating accessible routes.

Static assets: Files such as images, fonts, videos, and other media that are served directly without processing. Static assets are typically stored in the public directory and referenced by their relative paths.

Import aliases: Custom path mappings that provide shorthand references for frequently used directories. Import aliases reduce the complexity of relative imports and make code more readable and maintainable.

Comment thread docs/01-app/glossary.mdx Outdated
@delbaoliveira delbaoliveira merged commit 599fc3f into canary Jan 23, 2026
72 checks passed
@delbaoliveira delbaoliveira deleted the docs-glossary branch January 23, 2026 12:04
icyJoseph pushed a commit that referenced this pull request Jan 26, 2026
Add next.js glossary so we can reference concepts in guides without
having to re-explain them. Guides should be succint, like a skill :)

Closes: https://linear.app/vercel/issue/DOC-5574/nextjs-glossary

---------

Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
@github-actions github-actions Bot added the locked label Feb 6, 2026
@github-actions github-actions Bot locked as resolved and limited conversation to collaborators Feb 6, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

created-by: Next.js DevEx team PRs by the DX team. Documentation Related to Next.js' official documentation. locked

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants