Skip to content

Conversation

@devin-ai-integration
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot commented Nov 17, 2025

Update Fern Editor component support status and fix MDX parsing error

Summary

Updates the Fern Editor documentation to accurately reflect current component support status based on PR review feedback from Sarah (@sbawabe). Also includes an MDX parsing fix for the CLI changelog that was blocking CI.

Changes:

  1. Updated component support table to mark Button, Embed, endpoint snippets (Request/Response/Schema), and Sticky tables as "Supported" instead of "Coming soon"
  2. Removed the "Does Fern Editor support all components?" accordion as it was duplicative of the component support table
  3. Fixed MDX parsing error in CLI changelog (2025-11-14.mdx) by properly escaping {API name} and X/Y placeholders with backticks

Review & Testing Checklist for Human

  • Verify component support accuracy: Confirm that Button, Embed, all three endpoint snippet components, and Sticky tables are actually fully supported in Fern Editor (not just partially working). This is the most critical item - if any of these aren't fully functional, the docs will be misleading.
  • Check preview deployment: Navigate to the Fern Editor page in the preview and verify:
    • The component support table displays correctly with updated statuses
    • The removed accordion doesn't leave an awkward gap or break the page flow
    • All component links in the table work correctly
  • Verify "tables" interpretation: Confirm that updating "Sticky tables" status was the correct interpretation of Sarah's comment "add another row that tables are supported" (vs. adding a separate "Tables" entry)
  • Verify MDX fix: Navigate to /learn/cli-api-reference/cli-changelog and confirm the 2025-11-14 entry renders correctly without parse errors

Test Plan

  1. Visit the preview URL and navigate to /learn/docs/writing-content/fern-editor
  2. Scroll to the "What are the supported components?" section
  3. Verify the table shows Button, Embed, endpoint snippets, and Sticky tables as "Supported"
  4. Confirm the FAQ section flows naturally without the removed accordion
  5. Test each newly-marked-as-supported component in Fern Editor to ensure they actually work
  6. Navigate to /learn/cli-api-reference/cli-changelog and verify the 2025-11-14 entry displays correctly

Notes

@devin-ai-integration
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@github-actions
Copy link
Contributor

@github-actions
Copy link
Contributor

@github-actions
Copy link
Contributor

devin-ai-integration bot and others added 3 commits November 18, 2025 15:48
Update the 'Does Fern Editor support all components?' FAQ to accurately reflect that most components are supported with some still coming soon, making it consistent with the component support table above it.

Co-Authored-By: Chris McDonnell <chris@buildwithfern.com>
Remove time-relative term 'currently' and unnecessary adverb 'regularly' to make the FAQ answer more timeless and concise.

Co-Authored-By: Chris McDonnell <chris@buildwithfern.com>
- Remove 'Does Fern Editor support all components?' accordion (duplicative of table)
- Update Button status from 'Coming soon' to 'Supported'
- Update Embed status from 'Coming soon' to 'Supported'
- Update Endpoint Request/Response/Schema Snippet statuses to 'Supported'

Note: Still waiting for clarification on URL path for Tables component row.
Co-Authored-By: Chris McDonnell <chris@buildwithfern.com>
@devin-ai-integration devin-ai-integration bot force-pushed the devin/1763399335-update-fern-editor-components branch from 561c20f to 599764d Compare November 18, 2025 15:49
Wrap {API name} and X/Y placeholders in backticks to prevent MDX parser
from treating curly braces as JSX expressions. This fixes the 'Could not
parse expression with acorn' error that was blocking CI.

This fix is bundled with the Fern Editor component updates to unblock CI
on this PR. The same fix was proposed in PR #2065 but hasn't been merged yet.

Co-Authored-By: Chris McDonnell <chris@buildwithfern.com>
@github-actions
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot changed the title Fix contradictory FAQ about Fern Editor component support Update Fern Editor component support status and fix MDX parsing error Nov 18, 2025
Per Sarah's feedback, mark Sticky tables as 'Supported' in the component
support table.

Co-Authored-By: Chris McDonnell <chris@buildwithfern.com>
@github-actions
Copy link
Contributor

@github-actions
Copy link
Contributor

@github-actions
Copy link
Contributor

@sbawabe sbawabe merged commit 19ccf7b into main Nov 18, 2025
2 checks passed
@sbawabe sbawabe deleted the devin/1763399335-update-fern-editor-components branch November 18, 2025 16:21
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