Skip to content

Commit 786f6e1

Browse files
Kapil GowruKapil Gowru
authored andcommitted
feat: udpating ve & swift generator
1 parent 100d32e commit 786f6e1

File tree

2 files changed

+8
-12
lines changed

2 files changed

+8
-12
lines changed

fern/products/docs/docs.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -97,6 +97,7 @@ navigation:
9797
icon: fa-duotone fa-comment
9898
- page: Fern Editor
9999
path: ./pages/component-library/writing-content/visual-editor.mdx
100+
slug: fern-editor
100101
- page: Reusable snippets
101102
path: ./pages/component-library/custom-components/reusable-markdown.mdx
102103
slug: reusable-markdown

fern/products/docs/pages/component-library/writing-content/visual-editor.mdx

Lines changed: 7 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,9 @@
11
---
22
title: Fern Editor
33
description: Update your docs visually with a GitHub-backed workflow that creates PRs.
4-
slug: /docs/content/fern-editor
54
---
65

7-
Fern Editor lets you modify your documentation without touching code. Make changes directly in your browser while maintaining your Git-based workflow.
6+
Fern Editor lets anyone on your team update documentation without learning code, markdown, or Git. Perfect for non-technical teammates like content writers, product managers, and marketers who want to contribute to docs without needing developer setup.
87

98
<Frame
109
caption="Edit your docs visually with Fern Editor"
@@ -24,15 +23,15 @@ Fern Editor lets you modify your documentation without touching code. Make chang
2423

2524
<CardGroup cols={2}>
2625
<Card title="Expressive rich text" icon="duotone edit">
27-
Edit Fern Docs from an intuitive Notion-style interface
26+
Write and edit like you would in Notion or Google Docs—no markdown or code required
2827
</Card>
2928

3029
<Card title="Fern components support" icon="duotone puzzle-piece">
3130
Create and edit Callouts, Cards, etc directly from UI, with more components coming soon ✨
3231
</Card>
3332

34-
<Card title="One-click PRs" icon="duotone code-compare">
35-
Seamlessly push changes up to GitHub for review and publishing
33+
<Card title="GitHub-backed workflow" icon="duotone code-compare">
34+
Maintains docs-as-code approach with Git history and review process—making content easily consumable by AI tools
3635
</Card>
3736

3837
<Card title="Dev mode" icon="duotone code">
@@ -84,8 +83,8 @@ Have feedback? Use the Feedback button in the top-right of the editor.
8483
<br />
8584
</Accordion>
8685

87-
<Accordion title="How is “WYSIWYG” related to Fern Editor?">
88-
WYSIWYG is a common term for visual editing. Fern Editor is our visual editor - same idea, clearer name.
86+
<Accordion title="How is 'What You See Is What You Get' related to Fern Editor?">
87+
"What You See Is What You Get" (WYSIWYG) is a common term for visual editing. Fern Editor is our visual editor - same idea, clearer name.
8988
</Accordion>
9089

9190
<Accordion title="Why is a GitHub‑backed editor important?">
@@ -104,12 +103,8 @@ Have feedback? Use the Feedback button in the top-right of the editor.
104103
Log in to the [Dashboard](https://dashboard.buildwithfern.com/), connect GitHub, then open Fern Editor from the top navigation.
105104
</Accordion>
106105

107-
<Accordion title="Is Fern Editor good for SEO and performance?">
108-
Yes. Pages are server‑rendered and optimized for SEO. Components within accordions and tabs are still indexable.
109-
</Accordion>
110-
111106
<Accordion title="What browsers and devices does Fern Editor support?">
112-
Modern Chromium, Firefox, and Safari on desktop. Mobile editing is not yet supported.
107+
Currently supports modern Chromium browsers on desktop only. Mobile editing and other browsers coming soon.
113108
</Accordion>
114109
</AccordionGroup>
115110

0 commit comments

Comments
 (0)