Skip to content

Commit 2a758d8

Browse files
Visual Editor: Update
1 parent 5e36799 commit 2a758d8

File tree

3 files changed

+139
-123
lines changed

3 files changed

+139
-123
lines changed

fern/products/docs/pages/getting-started/overview.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -155,4 +155,4 @@ subtitle: A website builder for beautiful agent and developer-friendly docs.
155155
</div>
156156
</a>
157157
</CardGroup>
158-
</div>
158+
</div>

fern/products/docs/pages/getting-started/quickstart.mdx

Lines changed: 136 additions & 119 deletions
Original file line numberDiff line numberDiff line change
@@ -11,141 +11,154 @@ In this guide, we'll show you how to get started with Fern in under 5 minutes.
1111

1212
<Steps toc={true}>
1313
### Initialize your `fern` folder
14-
15-
All the configurations for your docs live in the `fern` folder. Inside, you'll
16-
find a `docs.yml` file that contains all the settings for your documentation.
14+
15+
All the configurations for your docs live in the `fern` folder. Inside, you'll
16+
find a `docs.yml` file that contains all the settings for your documentation.
1717

1818
<AccordionGroup toc={true}>
19-
<Accordion title='Clone the starter repository'>
19+
<Accordion title="Clone the starter repository">
2020
Get started by cloning the [starter template](https://github.com/fern-api/docs-starter).
2121

22-
<CodeBlocks>
23-
```bash title="SSH"
24-
git clone [email protected]:fern-api/docs-starter.git
25-
```
26-
```bash title="HTTPS"
27-
git clone https://github.com/fern-api/docs-starter.git
28-
```
29-
</CodeBlocks>
22+
<CodeBlocks>
23+
```bash title="SSH"
24+
git clone [email protected]:fern-api/docs-starter.git
25+
```
3026

31-
Next, please update the template settings to use your organization.
27+
```bash title="HTTPS"
28+
git clone https://github.com/fern-api/docs-starter.git
29+
```
30+
</CodeBlocks>
31+
32+
Next, please update the template settings to use your organization.
3233

33-
<Warning title="Edit template settings">
34-
Please edit the details `fern.config.json` and `docs.yml` with your organization
35-
name.
34+
<Warning title="Edit template settings">
35+
Please edit the details `fern.config.json` and `docs.yml` with your organization name.
3636

37-
<CodeBlocks>
38-
<CodeBlock title="fern.config.json">
39-
```json {2}
37+
<CodeBlocks>
38+
<CodeBlock title="fern.config.json">
39+
```json {2}
4040
{
4141
"organization": "{{YOUR_ORGANIZATION}}",
4242
"version": "0.x.x"
4343
}
4444
```
45-
</CodeBlock>
46-
<CodeBlock title="docs.yml">
47-
```yml {2}
45+
</CodeBlock>
46+
47+
<CodeBlock title="docs.yml">
48+
```yml {2}
4849
instances:
4950
- url: {{YOUR_ORGANIZATION}}.docs.buildwithfern.com
5051
```
51-
</CodeBlock>
52-
</CodeBlocks>
53-
</Warning>
54-
Finally, navigate to the docs directory (where the `fern` folder is located) and execute the following command to generate your documentation:
52+
</CodeBlock>
53+
</CodeBlocks>
54+
</Warning>
55+
56+
Finally, navigate to the docs directory (where the `fern` folder is located) and execute the following command to generate your documentation:
57+
58+
```bash
59+
fern generate --docs
60+
```
5561

56-
```bash
57-
fern generate --docs
58-
```
5962
</Accordion>
60-
<Accordion title='Use the Fern CLI'>
61-
If you prefer, you can use our CLI to create a new project. Install the CLI
62-
by running
6363

64-
```bash
65-
npm install -g fern-api
66-
```
64+
<Accordion title="Use the Fern CLI">
65+
If you prefer, you can use our CLI to create a new project. Install the CLI by running
6766

68-
Then run
67+
```bash
68+
npm install -g fern-api
69+
```
6970

70-
```bash
71-
fern init --docs
72-
```
71+
Then run
7372

74-
You will see a new `fern` folder in your project with the following structure:
73+
```bash
74+
fern init --docs
75+
```
7576

76-
```bash
77-
fern
78-
├─ docs.yml
79-
└─ fern.config.json
80-
```
81-
Finally, navigate to the docs directory (where the `fern` folder is located) and execute the following command to generate your documentation:
77+
You will see a new `fern` folder in your project with the following structure:
78+
79+
```bash
80+
fern
81+
├─ docs.yml
82+
└─ fern.config.json
83+
```
84+
85+
Finally, navigate to the docs directory (where the `fern` folder is located) and execute the following command to generate your documentation:
86+
87+
```bash
88+
fern generate --docs
89+
```
8290

83-
```bash
84-
fern generate --docs
85-
```
8691
</Accordion>
8792

93+
<Accordion title="My next page">
94+
Here's my content.
95+
96+
<Callout intent="note">
97+
Warning you should save before closing
98+
99+
</Callout>
100+
</Accordion>
88101
</AccordionGroup>
89102

90103
### Update your docs
91104

92105
<Note>
93106
We provide a white-glove migration service as part of our Enterprise plan. Interested? Request it
94-
[here](https://buildwithfern.com/contact).
107+
[here](https://buildwithfern.com/contact).
108+
95109
</Note>
96110

97111
<AccordionGroup toc={true}>
98-
<Accordion title='Add content' >
99-
Add content with MDX files.
100-
101-
```markdown
102-
---
103-
title: "Page Title"
104-
description: "Subtitle (optional)"
105-
---
106-
107-
Hello world!
108-
```
112+
<Accordion title="Add content">
113+
Add content with MDX files.
114+
115+
```markdown
116+
---
117+
title: "Page Title"
118+
description: "Subtitle (optional)"
119+
---
120+
121+
Hello world!
122+
```
109123

110-
<Note title="Supported Syntax">
124+
<Note title="Supported Syntax">
111125
Fern supports [GitHub flavored Markdown (GFM)](https://github.github.com/gfm/) within MDX files, no plugin required.
112-
</Note>
126+
</Note>
113127

114-
In order for the Markdown page to show up, you'll need to reference them from your `docs.yml` file. You
115-
can reference the Markdown page within a section or as a standalone page.
128+
In order for the Markdown page to show up, you'll need to reference them from your `docs.yml` file. You can reference the Markdown page within a section or as a standalone page.
116129

117-
```yml
118-
navigation:
119-
- page: Hello World
120-
path: docs/pages/hello-world.mdx
121-
- section: Overview
122-
contents:
123-
- page: QuickStart
124-
path: docs/pages/hello-world.mdx
125-
```
126-
</Accordion>
127-
<Accordion title='Add an API Reference' >
128-
Add an API Reference by adding an OpenAPI Specification to your project.
130+
```
131+
navigation:
132+
- page: Hello World
133+
path: docs/pages/hello-world.mdx
134+
- section: Overview
135+
contents:
136+
- page: QuickStart
137+
path: docs/pages/hello-world.mdx
138+
```
139+
</Accordion>
129140

130-
```bash
131-
fern init --openapi /path/to/openapi.yml
132-
```
141+
<Accordion title="Add an API Reference">
142+
Add an API Reference by adding an OpenAPI Specification to your project.
133143

134-
This will create an `openapi.yml` file in your project. You can reference this file in your
135-
`docs.yml` file by adding an api block.
144+
```bash
145+
fern init --openapi /path/to/openapi.yml
146+
```
136147

137-
```yml
138-
navigation:
139-
- api: "API Reference"
140-
```
141-
</Accordion>
142-
<Accordion title='Brand your docs'>
143-
All of the branding for your docs can be configured in the `docs.yml` file.
148+
This will create an `openapi.yml` file in your project. You can reference this file in your `docs.yml` file by adding an api block.
144149

145-
For example, to set the logos, colors, and fonts for your docs, you can
146-
add the following to your `docs.yml` file:
150+
```
151+
navigation:
152+
- api: "API Reference"
153+
```
154+
</Accordion>
147155

148-
<CodeBlock title="docs.yml">
156+
<Accordion title="Brand your docs">
157+
All of the branding for your docs can be configured in the `docs.yml` file.
158+
159+
For example, to set the logos, colors, and fonts for your docs, you can add the following to your `docs.yml` file:
160+
161+
<CodeBlock title="docs.yml">
149162
```yml
150163
colors:
151164
accent-primary:
@@ -160,44 +173,48 @@ In this guide, we'll show you how to get started with Fern in under 5 minutes.
160173

161174
favicon: docs/assets/favicon.svg
162175
```
163-
</CodeBlock>
164-
165-
</Accordion>
176+
</CodeBlock>
177+
</Accordion>
166178
167179
</AccordionGroup>
168-
180+
169181
### Preview your docs
182+
170183
<AccordionGroup toc={true}>
171-
<Accordion title='Preview your docs locally'>
172-
You can preview your docs locally for testing purposes by following the instructions [here](/docs/preview-publish/previewing-changes-locally).
173-
</Accordion>
174-
<Accordion title='Preview your docs in a PR'>
175-
`PR previews` offer a way to preview changes from pull requests (PRs) before merging code to a production branch. Learn more [here](/docs/preview-publish/previewing-changes-in-a-pr).
176-
</Accordion>
184+
<Accordion title="Preview your docs locally">
185+
You can preview your docs locally for testing purposes by following the instructions [here](/docs/preview-publish/previewing-changes-locally).
186+
</Accordion>
187+
188+
<Accordion title="Preview your docs in a PR">
189+
`PR previews` offer a way to preview changes from pull requests (PRs) before merging code to a production branch. Learn more [here](/docs/preview-publish/previewing-changes-in-a-pr).
190+
</Accordion>
191+
177192
</AccordionGroup>
178-
193+
179194
### Publish to production
180195

181196
<AccordionGroup toc={true}>
182-
<Accordion title='Publishing your docs'>
183-
When you are ready for your docs to be publicly accessible, you can publish them using the Fern CLI.
197+
<Accordion title="Publishing your docs">
198+
When you are ready for your docs to be publicly accessible, you can publish them using the Fern CLI.
184199

185-
[Read more.](/learn/docs/preview-publish/publishing-your-docs)
186-
</Accordion>
187-
<Accordion title='Host on a custom domain'>
188-
Fern supports hosting your docs website on a custom domain or on a
189-
custom subpath (e.g. `https://example.com/docs`).
200+
[Read more.](/learn/docs/preview-publish/publishing-your-docs)
201+
</Accordion>
190202

191-
Please reach out to the Fern team at [email protected] to configure this.
192-
</Accordion>
193-
<Accordion title='Configure analytics'>
194-
Fern supports integrations with a variety of providers such as PostHog, Segment, Intercom,
195-
Google Tag Manager, etc.
196-
Find out more on this [page](/learn/docs/integrations/overview).
197-
</Accordion>
203+
<Accordion title="Host on a custom domain">
204+
Fern supports hosting your docs website on a custom domain or on a
205+
custom subpath (e.g. `https://example.com/docs`).
198206

199-
</AccordionGroup>
207+
Please reach out to the Fern team at [email protected] to configure this.
208+
</Accordion>
200209

210+
<Accordion title="Configure analytics">
211+
Fern supports integrations with a variety of providers such as PostHog, Segment, Intercom,
212+
Google Tag Manager, etc.
213+
Find out more on this [page](/learn/docs/integrations/overview).
214+
</Accordion>
215+
216+
</AccordionGroup>
201217
</Steps>
202218

203-
[View examples of documentation websites](https://buildwithfern.com/customers) that have been published using Fern.
219+
220+
[View examples of documentation websites](https://buildwithfern.com/customers) that have been published using Fern.

fern/products/home/pages/welcome.mdx

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,11 @@
11
---
22
title: Build with Fern
3-
description: Explore our guides for how to generate SDKs and Docs with Fern.
43
slug: /
4+
description: Explore our guides for how to generate SDKs and Docs with Fern.
55
hide-toc: true
66
layout: custom
77
---
88

9-
109
import { FernFooter } from "../../../components/FernFooter";
1110

1211
<div className="lp-page-container">
@@ -389,4 +388,4 @@ import { FernFooter } from "../../../components/FernFooter";
389388
</div>
390389

391390
</div>
392-
</div>
391+
</div>

0 commit comments

Comments
 (0)