docs: add file imports, assets, and API calls guidance for custom React components #2294
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds documentation to the custom React components page addressing common user questions about file organization and capabilities. This was prompted by a user question in Slack asking about accessing other files, creating separate JS/CSS files, adding SVG assets, and making API calls with API keys.
New sections added:
Also adds a changelog entry for 2025-11-25.
Review & Testing Checklist for Human
mdx-componentsin docs.yml - confirm this is the correct approachRecommended test plan: Create a test Fern project with a custom React component that imports a CSS file, a utility module, and an SVG asset to verify the documented patterns work as described.
Local Testing
Documentation renders correctly in local dev server:
View original video (rec-638680df7a8d45c79e4032ac2c5f9ca9-edited.mp4)
Notes