feat: udpating ve #931
feat: udpating ve #931
Conversation
fern-support
commented
Sep 23, 2025
fern-support
commented
- added swift icon in homepage
- updating ve content
| description: Edit your docs visually, no code required | ||
| title: Fern Editor | ||
| description: Update your docs visually with a GitHub-backed workflow that creates PRs. | ||
| slug: /docs/content/fern-editor |
There was a problem hiding this comment.
Can you put slugs in docs.yml instead of frontmatter for consistency?
docs/fern/products/docs/docs.yml
Lines 65 to 68 in 1fd9ed7
| </Note> | ||
|
|
||
| The Fern Visual Editor lets you modify your documentation without touching code. Make changes directly in your browser while maintaining your Git-based workflow. | ||
| Fern Editor lets you modify your documentation without touching code. Make changes directly in your browser while maintaining your Git-based workflow. |
There was a problem hiding this comment.
modify seems like small changes. How about:
Fern Editor brings a Notion-like editing experience to your documentation site. Write, edit, and publish directly in the browser—no need to open a code editor or learn markdown. The result is faster authoring, easier contributions for non-technical teammates, and a best-in-class visual editing experience powered by TipTap.
| </Button> | ||
| </div> | ||
|
|
||
| After logging in, connect your GitHub account. Then open Fern Editor from the Docs settings.it |
There was a problem hiding this comment.
Feels like an incomplete thought.
| </Card> | ||
| </CardGroup> | ||
|
|
||
| All Fern components are supported. See the full list in the Components Overview: [Components Overview](https://buildwithfern.com/learn/docs/writing-content/components/overview). |
There was a problem hiding this comment.
would eliminate fern before components
|
|
||
| ## Why Fern Editor | ||
|
|
||
| - Makes updating your docs site super simple |
There was a problem hiding this comment.
biggest benefit is around usability by non-technical teammates who aren't familiar with a code editor, terminal, markdown, or yaml.
| ## FAQ | ||
|
|
||
| <AccordionGroup> | ||
| <Accordion title="How is “WYSIWYG” related to Fern Editor?"> |
There was a problem hiding this comment.
would remove quotes from WYSIWYG and spell out the acronym
There was a problem hiding this comment.
could be the question:
Is Fern Editor a WYSIWYG editor?
|
|
||
| <AccordionGroup> | ||
| <Accordion title="How is “WYSIWYG” related to Fern Editor?"> | ||
| “WYSIWYG” is a common term for visual editing. Fern Editor is our visual editor - same idea, clearer name. |
There was a problem hiding this comment.
Can the answer just be "yes, Fern Editor is a WYSIWYG editor."
| </Accordion> | ||
|
|
||
| <Accordion title="Why is a GitHub‑backed editor important?"> | ||
| Your changes become pull requests. That means code review, auditability, CI checks, and merge control with branch protections - no surprises in production. |
There was a problem hiding this comment.
Would mention docs-as-code here. Would mention that docs-as-code makes consumption by AI tools easier.
| Log in to the [Dashboard](https://dashboard.buildwithfern.com/), connect GitHub, then open Fern Editor from the top navigation. | ||
| </Accordion> | ||
|
|
||
| <Accordion title="Is Fern Editor good for SEO and performance?"> |
There was a problem hiding this comment.
Would remove. Don't think anyone will ask this question.
| Yes. Pages are server‑rendered and optimized for SEO. Components within accordions and tabs are still indexable. | ||
| </Accordion> | ||
|
|
||
| <Accordion title="What browsers and devices does Fern Editor support?"> |
