-
Notifications
You must be signed in to change notification settings - Fork 28
Revamp docs-starter with instructional content #87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
sbawabe
merged 10 commits into
main
from
devin/1765559062-revamp-docs-starter-instructional
Dec 15, 2025
Merged
Changes from 4 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
0e3027f
Revamp docs-starter with instructional content
devin-ai-integration[bot] 9402e41
Address PR feedback: simplify pages with card galleries and accordions
devin-ai-integration[bot] 972ca9e
Address PR feedback: update navbar link and simplify support page
devin-ai-integration[bot] ac2e42e
Update welcome page title and subtitle per PR feedback
devin-ai-integration[bot] 3abf200
Update API reference overview per PR feedback
devin-ai-integration[bot] 6b48d0c
Update theme colors, logo, and API reference overview
devin-ai-integration[bot] 9029640
Remove Fern Definition from supported specifications table per PR fee…
devin-ai-integration[bot] 75f989a
Update OpenAPI version description to include 2.0, 3.0, and 3.1 per P…
devin-ai-integration[bot] b490d22
various small updates, add more components
devalog 711da47
small change
devalog File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,114 @@ | ||
| --- | ||
| title: API reference | ||
| subtitle: Interactive documentation generated from your API specification | ||
| slug: api-reference | ||
| --- | ||
|
|
||
| Fern automatically generates interactive API reference documentation from your API specification. This starter template includes a sample Plant Store API to demonstrate the feature. | ||
|
|
||
| ## Supported specifications | ||
|
|
||
| Fern supports multiple API specification formats: | ||
|
|
||
| | Format | Description | | ||
| |--------|-------------| | ||
| | **OpenAPI** | The most widely used REST API specification format (versions 3.0 and 3.1) | | ||
| | **AsyncAPI** | For event-driven and message-based APIs | | ||
| | **gRPC** | Protocol buffer definitions for gRPC services | | ||
| | **Fern Definition** | Fern's native YAML-based API definition format | | ||
|
sbawabe marked this conversation as resolved.
Outdated
|
||
|
|
||
| <Note> | ||
| This starter template uses an OpenAPI specification. For documentation on other formats, see the [API definitions documentation](https://buildwithfern.com/learn/api-definitions/openapi/overview). | ||
| </Note> | ||
|
|
||
| ## How it works | ||
|
|
||
| Place your API specification file in the `fern/` directory and reference it in your `docs.yml` navigation: | ||
|
|
||
| ```yaml title="docs.yml" | ||
| navigation: | ||
| - section: Documentation | ||
| contents: | ||
| - page: Overview | ||
| path: docs/pages/overview.mdx | ||
| - api: API Reference | ||
| ``` | ||
|
|
||
| Fern parses your specification and generates: | ||
|
|
||
| - Endpoint documentation with request/response schemas | ||
| - Interactive API Explorer for testing endpoints | ||
| - Code snippets in multiple languages | ||
| - Type definitions and examples | ||
|
|
||
| ## API Explorer | ||
|
|
||
| The API Explorer lets users test API endpoints directly in the documentation. Users can fill in parameters, send requests, and see responses without leaving the page. | ||
|
|
||
| <Note> | ||
| For advanced API Explorer features like auto-populating API keys, see the [API Explorer documentation](https://buildwithfern.com/learn/docs/api-references/api-explorer/overview). | ||
| </Note> | ||
|
|
||
| ## Customizing the API reference | ||
|
|
||
| Control how your API reference appears using the `api` configuration in `docs.yml`: | ||
|
|
||
| ```yaml title="docs.yml" | ||
| navigation: | ||
| - api: API Reference | ||
| api-name: plantstore | ||
| paginated: true | ||
| ``` | ||
|
|
||
| You can also add custom content to API reference pages, organize endpoints into groups, and control which endpoints are visible. | ||
|
|
||
| <Note> | ||
| For detailed customization options, see the [API reference documentation](https://buildwithfern.com/learn/docs/api-references/generate-api-ref). | ||
| </Note> | ||
|
|
||
| ## SDK code snippets | ||
|
|
||
| If you generate SDKs with Fern, code snippets automatically appear in your API reference showing how to call each endpoint using your SDK: | ||
|
|
||
| ```yaml title="generators.yml" | ||
| groups: | ||
| python-sdk: | ||
| generators: | ||
| - name: fernapi/fern-python-sdk | ||
| version: 4.3.1 | ||
| output: | ||
| location: pypi | ||
| package-name: plantstore | ||
| ``` | ||
|
|
||
| <Note> | ||
| For more information on SDK generation, see the [SDK documentation](https://buildwithfern.com/learn/sdks/overview/introduction). | ||
| </Note> | ||
|
|
||
| ## Explore the Plant Store API | ||
|
|
||
| This starter template includes a sample Plant Store API with endpoints for managing plants, orders, and users. Browse the API reference below to see how Fern generates documentation from an OpenAPI specification. | ||
|
|
||
| <CardGroup cols={3}> | ||
| <Card | ||
| title="Plant endpoints" | ||
| icon="duotone seedling" | ||
| href="/api-reference/plant/addPlant" | ||
| > | ||
| Add, update, and search plants | ||
| </Card> | ||
| <Card | ||
| title="Store endpoints" | ||
| icon="duotone store" | ||
| href="/api-reference/store/getInventory" | ||
| > | ||
| Manage inventory and orders | ||
| </Card> | ||
| <Card | ||
| title="User endpoints" | ||
| icon="duotone user" | ||
| href="/api-reference/user/loginUser" | ||
| > | ||
| Authentication and user management | ||
| </Card> | ||
| </CardGroup> | ||
|
sbawabe marked this conversation as resolved.
Outdated
|
||
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sbawabe want to add: