Changelog

This locks in tone, section names, bullet style, and tag taxonomy before you write anything.

2. Find the cutoff

Run git log --oneline -n 50 to see recent commits, then:

1. Find the most recent file in blog/ by filename date (filenames are YYYY-MM-DD-<slug>.md and the date in the filename is the source of truth, not the file mtime).
2. Use that date as the cutoff: include only commits after the most recent blog post date.
3. If the user specified a different range, use theirs instead.

Run git log --since=<cutoff-date> --pretty=format:"%h %ad %s" --date=short to get the relevant commits. If the result is empty or trivial (1–2 small commits), tell the user — don't fabricate a post just to have one.

3. Group commits semantically

Don't list commits one-for-one. Group them by area, then within each area decide whether each item is Added, Fixed, or Improved.

Section choices (use only the ones that apply, in this order):

• ## Added — new features, new adapters, new scenarios, new docs pages
• ## Fixed — bug fixes, broken links, typo fixes, config corrections
• ## Improved — refactors, clarity passes, restructuring, performance, UI polish

For larger posts (like initial-launch), you can omit the ## Added heading entirely and instead use bold subheaders as grouping (e.g., **YAML Node Types**, **Adapters**, **Site**). Use this style when there are 8+ items spanning multiple unrelated areas.

Common semantic groups in this repo:

• New CRM adapter docs → cluster as one bullet ("HubSpot adapter — full documentation for getCustomerDetails, newOpportunity, ...")
• Changes to src/data/scenarios.ts → "Scenario Marketplace" or per-scenario bullets
• Changes to src/components/, src/pages/, src/css/ → "Site" group
• Changes to docusaurus.config.ts, sidebars.ts, plugins → "Site" group
• Changes to existing docs in docs/YAML/Types/Func/ → group by function name or category
• Changes under .github/workflows/ → usually skip unless user-visible

4. Bullet format

Each bullet follows: - **Name** — short description. The em-dash (—, U+2014) is the separator, not a hyphen. The bold name should be the user-visible thing (a function name in code style, an adapter name as plain text, a feature name as plain text).

Examples drawn from existing posts:

- **Plando adapter** — full documentation for `getCustomerDetails`, `newOpportunity`, `openTicket`/`closeTicket`, and out-of-adapter endpoints (`log_activity`, `upload_contact_file`)
- **`log_activity`** — expanded with all supported API fields including contact identification options, record fields, and response handling
- **Send Media** — added dynamic URL tip (workaround for editor validation when using data injection in `doc:`/`media:`) and a line breaks in captions example

Sub-bullets are allowed (two spaces of indentation) for nested detail — see 2026-04-07-scenario-marketplace.md line 14–18 for the pattern.

5. Frontmatter

---