Skip to content

Add multi-source example with homepage + 3 sub-paths#6

Open
devin-ai-integration[bot] wants to merge 1 commit intomainfrom
devin/1777573514-add-multi-source-example
Open

Add multi-source example with homepage + 3 sub-paths#6
devin-ai-integration[bot] wants to merge 1 commit intomainfrom
devin/1777573514-add-multi-source-example

Conversation

@devin-ai-integration
Copy link
Copy Markdown
Contributor

Summary

Adds a multi-source/ example demonstrating how multiple teams can publish to the same domain from independent repositories using Fern's multi-source docs feature.

The example contains 4 standalone Fern projects:

  • homepage/ — landing page at the domain root with a CardGroup linking to each team's sub-path
  • seeds/ — publishes to /seeds with seed catalog and planting guide content
  • greenhouses/ — publishes to /greenhouses with climate control and monitoring content
  • nursery/ — publishes to /nursery with plant care and propagation content

All four projects target multi-source.docs.buildwithfern.com, set multi-source: true, and share the same branding. Each has its own fern/ directory with docs.yml, fern.config.json, and sample MDX pages.

This matches the "homepage + 3 teams" pattern documented in the multi-source docs page.

Review & Testing Checklist for Human

  • Verify the docs.yml configurations look correct (URLs, multi-source flag, navigation)
  • Confirm the homepage CardGroup links match the team sub-paths
  • Check that page content uses appropriate Fern components (CardGroup, Steps, AccordionGroup)

Notes

The example README notes that in production, teams should use a global theme instead of duplicating colors/logos across repos.

Link to Devin session: https://app.devin.ai/sessions/b3a9f06371964eb780a68b4e88cb81ab

Co-Authored-By: kenny <kenny@buildwithfern.com>
@devin-ai-integration
Copy link
Copy Markdown
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
Copy Markdown

@github-actions
Copy link
Copy Markdown

@github-actions
Copy link
Copy Markdown

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.

0 participants