This adds greater flexibility to our existing partials / includes

Adds support for partials to include other partials in them

If you have a partial that should build upon another partial, just <Include /> it

For example:

filename: ./docs/_partials/welcome.mdx

Welcome to the Clerk Docs

<Include src="_partials/getting-started" />

filename: ./docs/_partials/getting-started.mdx

To get started, install the clerk dependency

filename: ./docs/index.mdx

Clerk Docs

<Include src="_partials/welcome" />

Would output:

filename: ./dist/index.mdx

Clerk Docs

Welcome to the Clerk Docs

To get started, install the clerk dependency

Adds support for a _partials folder to exist anywhere in the docs

a _partials folder can now be put anywhere in the ./docs folder, wherever is most relevant to the guides that will be consuming the partial. The existing partials can still be included using src="_partial/ while relative will need to be src="./_partial/ or src="../_partial/

For example:

filename: ./docs/billing/_partials/setup.mdx

To create subscriptions open the clerk dashboard

filename: ./docs/billing/getting-started.mdx

<Include src="./_partials/getting-started" />

Would output:

filename: ./dist/billing/getting-started.mdx

To create subscriptions open the clerk dashboard

Example pr

Checkout #2693 to see how the relative partials can be used. That pr builds on top of this pr.

Checklist

• I have clicked on "Files changed" and performed a thorough self-review
• All existing checks pass