restructure new content

Author: devalog

fern/snippets/redirects.mdx

@@ -2,8 +2,8 @@ The `redirects` object allows you to redirect traffic from one path to another.
 
 If your docs are hosted on a subpath (like `buildwithfern.com/learn`), include the subpath in both the source and destination paths. 
 
-
   <CodeBlock title="docs.yml">
+
     ```yml
     redirects:
       # Exact path redirects
@@ -35,11 +35,24 @@ If your docs are hosted on a subpath (like `buildwithfern.com/learn`), include t
   Parameters suffixed with an asterisk (`*`) match zero or more path segments, capturing everything that follows in the URL. Use this when redirecting entire folder structures while preserving nested paths.
 </Info>
 
+<ParamField path="source" type="string" required={true}>
+  The incoming request path pattern.
+</ParamField>
+
+<ParamField path="destination" type="string" required={true}>
+  The path you want to route to. Can be an internal path (`/new-path`) or an external URL (`https://example.com`). External URLs must include the full address, including `https`.
+</ParamField>
+
+<ParamField path="permanent" type="boolean" required={false}>
+  `true` or `false` - default is `true`. If `true`, will use the 308 status code which instructs clients/search engines to cache the redirect forever. If `false`, will use the 307 status code which is temporary and is not cached.
+</ParamField>
+
 ### Advanced patterns
 
-Fern uses [Path-to-RegExp](https://github.com/pillarjs/path-to-regexp) for pattern matching. Named capture groups can be defined with regex patterns and reused in destination URLs:
+You can define named capture groups with regex patterns and reuse them in destination URLs:
 
 <CodeBlock title="docs.yml">
+
 ```yml
 redirects:
   # Match 4-digit years
@@ -56,24 +69,17 @@ redirects:
 ```
 </CodeBlock>
 
-**Pattern syntax:**
-- `:name` - Captures a single path segment
-- `:name*` - Captures zero or more segments  
-- `:name(\\d+)` - Captures digits only
-- `:name(\\d{4})` - Captures exactly 4 digits
-- `{0}` - Literal character delimiter between parameters
+<Accordion title="Pattern syntax">
 
-<ParamField path="source" type="string" required={true}>
-  The incoming request path pattern.
-</ParamField>
+| Pattern | Description |
+|---------|-------------|
+| `:name` | Captures a single path segment |
+| `:name*` | Captures zero or more segments |
+| `:name(\\d+)` | Captures digits only |
+| `:name(\\d{4})` | Captures exactly 4 digits |
+| `{0}` | Literal character delimiter between parameters |
 
-<ParamField path="destination" type="string" required={true}>
-  The path you want to route to. Can be an internal path (`/new-path`) or an external URL (`https://example.com`). External URLs must include the full address, including `https`.
-</ParamField>
-
-<ParamField path="permanent" type="boolean" required={false}>
-  `true` or `false` - default is `true`. If `true`, will use the 308 status code which instructs clients/search engines to cache the redirect forever. If `false`, will use the 307 status code which is temporary and is not cached.
-</ParamField>
+</Accordion>
 
 ### Best practices