Skip to content

Commit a516edc

Browse files
committed
add repo structure section to all pages
1 parent 8d3591b commit a516edc

File tree

2 files changed

+8
-0
lines changed

2 files changed

+8
-0
lines changed

advanced/subpath/cloudflare.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,10 @@ To host your documentation at a custom subpath such as `yoursite.com/docs` using
1111
Before you begin, you need a Cloudflare account and a domain name (can be managed on or off Cloudflare).
1212
</Info>
1313

14+
## Repository structure
15+
16+
Your documentation files must be organized within your repository to match your chosen subpath structure. For example, if you want your documentation at `yoursite.com/docs`, you would create a `docs/` directory with all of your documentation files.
17+
1418
## Set up a Cloudflare Worker
1519

1620
Create a Cloudflare Worker by following the [Cloudflare Workers getting started guide](https://developers.cloudflare.com/workers/get-started/dashboard/), if you have not already.

advanced/subpath/route53-cloudfront.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,10 @@ import Propagating from "/snippets/custom-subpath-propagating.mdx";
88

99
To host your documentation at a custom subpath such as `yoursite.com/docs` using AWS Route 53 and CloudFront, you need to configure your DNS provider to point to your CloudFront distribution.
1010

11+
## Repository structure
12+
13+
Your documentation files must be organized within your repository to match your chosen subpath structure. For example, if you want your documentation at `yoursite.com/docs`, you would create a `docs/` directory with all of your documentation files.
14+
1115
## Proxies with Vercel deployments
1216

1317
If you use AWS CloudFront as a proxy with Vercel deployments, you must configure CloudFront to avoid interfering with Vercel's domain verification and SSL certificate provisioning.

0 commit comments

Comments
 (0)