Use each catalog article’s Figma body ornaments instead of one shared pair.

Co-authored-by: Cursor <cursoragent@cursor.com>

docs/guides/content-creation.md

@@ -92,6 +92,7 @@ Each article uses SVGs in `public/content/blog/`. For a new article, duplicate a
    - `{slug}-vertical.svg` — 260px × 390px
    - `{slug}-horizontal.svg` — 320px × 225.5px (minimum width)
    - `{slug}-section.svg` — optional md+ banner (1920×672)
+   - `{slug}-ornament-right.png` / `{slug}-ornament-left.png` — body gutter shapes
    - `{slug}-tag.svg` — tag mark for content cards
 3. **Customize** the copied SVGs for your article
 4. **Add to frontmatter**:

docs/guides/static-assets.md

@@ -39,7 +39,8 @@ Do not duplicate the same glyph in both places unless migrating between systems.
   `shareIconPath`, `featurePanelPath`, `ASSETS`, …) over hardcoded
   `/assets/...` strings in components.
 - **Blog art** stays under `public/content/blog/` with
-  `{slug}-vertical.svg`, `-horizontal.svg`, `-section.svg`, `-tag.svg`.
+  `{slug}-vertical.svg`, `-horizontal.svg`, `-section.svg`, `-tag.svg`,
+  and `-ornament-right.png` / `-ornament-left.png` (body gutter shapes).
 - **Favicon** reuses `assets/logos/community-rule.svg` (`ASSETS.LOGO` in
   `app/layout.tsx` metadata) plus generated root binaries for Safari/iOS:
   `public/favicon.ico`, `favicon-16x16.png`, `favicon-32x32.png`, and