Skip to content

docs: clarify component naming for markdown import #10545

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Josh-Cena merged 3 commits into from
Oct 2, 2024
Merged

docs: clarify component naming for markdown import #10545

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1fc0265
docs: clarify component naming for markdown import (#10542)
jackrabbit128 Oct 2, 2024
b9edccc
Apply review suggestion
jackrabbit128 Oct 2, 2024
81e3d8e
Update website/docs/guides/markdown-features/markdown-features-react.mdx
Josh-Cena Oct 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions website/docs/guides/markdown-features/markdown-features-react.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -301,6 +301,7 @@ This feature is experimental and might be subject to breaking API changes in the
## Importing Markdown {#importing-markdown}

You can use Markdown files as components and import them elsewhere, either in Markdown files or in React pages.
In the `import` statement, you can name the component anything you like but it must be capitalized.

By convention, using the **`_` filename prefix** will not create any doc page and means the Markdown file is a **"partial"**, to be imported by other files.

Expand Down