ima-claude 2.18.0 → 2.25.0

package/plugins/ima-claude/skills/agentic-workflows/references/standards/draft-format.md

@@ -0,0 +1,159 @@
+# Draft Format
+
+Structural rules for drafts produced by the draft phase. Injected by the consumer when the recipe declares this file.
+
+---
+
+## What a Draft Is
+
+A draft is a complete post blueprint that reads like the published page. Every structural element is in place. Every placeholder is marked with the exact placeholder format. An editor reading the draft should be able to move it to production with minimal changes.
+
+A draft is not a partial document. It is not a summary of what will be written. It is not an outline with some prose filled in. If an element is missing, the draft is incomplete.
+
+---
+
+## 10 Required Elements
+
+Produce all 10 elements in this order. Recipes may modify the sequence or add elements — follow recipe overrides when they conflict with this default.
+
+### 1. Meta Description
+
+150–160 characters. Keyword-rich. Describes what the reader will get from the page. Written as a complete sentence or two fragments. Does not begin with the site name.
+
+```
+Meta: [150–160 character description]
+```
+
+### 2. Title
+
+Clear, specific, benefit-oriented. Not a topic label — a claim, a promise, or a question the reader is already asking. The title from the outline is a starting point; refine it for the draft.
+
+```
+# [Title]
+```
+
+### 3. Excerpt
+
+The first paragraph of the piece, set apart as the excerpt. Must contain one bolded key phrase — the most important idea for a scanner to land on. The bolded phrase should be a noun phrase or short clause, not a single word.
+
+```
+**[bolded key phrase]** — [rest of excerpt paragraph]
+```
+
+Or the bold can fall mid-paragraph where it is most impactful.
+
+### 4. Hero Element
+
+One of:
+- `[VIDEO EMBED: brief description of video content]`
+- `[HERO IMAGE: brief description — subject, mood, source if known]`
+
+Do not place a second visual element immediately after the hero. The prose intro follows.
+
+### 5. Prose Intro
+
+Two to three paragraphs that hook, frame, and set up the piece. Follows the hook/frame/setup structure from the outline's intro. Written in full prose — not bullets, not headers.
+
+The intro should give the reader a reason to keep reading. It does not summarize the entire piece. It earns the reader's next scroll.
+
+### 6. Citation Block
+
+For content based on a study or published research, include the citation immediately after the intro:
+
+```
+**Citation:** [Author Last Names]. "[Study Title]." *[Journal Name]*. [Year]. [DOI or URL if available]
+```
+
+For content not based on a primary study, omit this element.
+
+### 7. Body Sections
+
+For each section from the outline, produce:
+
+- An H2 header that states the section's core argument (not just the topic)
+- Prose developing the argument, incorporating key points from the outline
+- At least one bolded key phrase per section
+- Inline blockquotes where the outline marked quote placements
+- Asset placeholders where the outline marked asset placements
+- A subheader (`###`) if the section covers more than two distinct sub-topics
+
+No section should run more than four consecutive paragraphs without a visual break (image, quote, or subheader). Wall-of-text sections will be flagged in review.
+
+Blockquote format:
+```
+> [Speaker Name]: "[near-verbatim quote]"
+```
+
+### 8. Related Reading
+
+A list of three to five related resources with brief descriptions. Format:
+
+```
+## Related Reading
+
+- **[Resource Title]** — [one sentence description] [URL or placeholder]
+- **[Resource Title]** — [one sentence description] [URL or placeholder]
+```
+
+### 9. Forums Button
+
+A call to action pointing to the IMA community forums. Use the standard placeholder:
+
+```
+[Forums Button]
+```
+
+Recipes may specify different community CTAs — follow the recipe override.
+
+### 10. Asset Table
+
+A reference block listing all embeds, downloads, and CTAs used in the piece. The editor uses this to confirm all assets are live before publishing.
+
+```
+## Asset Table
+
+| Asset | Type | Location in Draft | Status |
+|-------|------|-------------------|--------|
+| [description] | Video embed | After intro | [URL or "TBD"] |
+| [description] | Image | Section 2 | [URL or "TBD"] |
+| [description] | PDF download | Related Reading | [URL or "TBD"] |
+```
+
+---
+
+## Placeholder Conventions
+
+Use these exact formats. Do not improvise placeholder syntax — the consumer may parse them.
+
+| Placeholder | Use For |
+|-------------|---------|
+| `[VIDEO EMBED: description]` | Video that should be embedded |
+| `[HERO IMAGE: description]` | Hero image at top of piece |
+| `[STUDY SCREENSHOT: description]` | Figure or table from a study |
+| `[Figure N: description]` | Any numbered figure |
+| `[Interstitial: CTA name]` | Mid-content CTA (between sections) |
+| `[Forums Button]` | Standard IMA forums CTA |
+| `[specific missing data]` | Any specific fact not in source material — describe what is needed |
+
+---
+
+## Naming Rule
+
+If the source material names it, the draft names it. There is no acceptable substitution of a specific reference for a generic one when the specific reference is available.
+
+- Named study → use the study name
+- Named drug or protocol → use the exact name as it appears in the source
+- Named speaker → full name on first mention, last name only after
+- Named institution → exact name, no abbreviation on first mention
+
+If the source material does not name something, use the appropriate placeholder.
+
+---
+
+## What Does NOT Belong
+
+- Body prose without structural elements — every piece of prose must live inside a named structural element
+- Deferred decisions — "the editor can decide X" — make the decision and note it in editorial watch items if it is uncertain
+- Generic references when specific ones are available in the source material
+- Assets that have not been seen or confirmed — use a placeholder, not an invented description
+- Prose summaries of what sections will contain — write the sections, do not summarize them

package/plugins/ima-claude/skills/agentic-workflows/references/standards/editorial-standards.md

@@ -0,0 +1,160 @@
+# Editorial Standards
+
+Universal quality criteria for IMA content. Injected by the consumer when the recipe declares this file.
+
+---
+
+## Voice Archetypes
+
+IMA content blends three archetypes simultaneously. Do not use them in turns or in separate sections — the blend must be present in every paragraph.
+
+| Archetype | What It Brings | How It Shows |
+|-----------|---------------|--------------|
+| **Caregiver** | Warmth, solidarity, human stakes | Acknowledges what patients are living with; writes to an ally, not a target |
+| **Sage** | Evidence, precision, credibility | Names studies, cites journals, qualifies claims accurately |
+| **Outlaw** | Institutional critique, moral clarity | Names specific actors when warranted; earned intensity, not reflexive antagonism |
+
+The blend should be invisible. Readers should feel it, not label it.
+
+---
+
+## Writing Principles
+
+### Lead with Progress
+
+Open with what has been learned, discovered, or achieved — not with the problem alone. The reader should leave the opening paragraph feeling informed, not alarmed.
+
+### Organize Around Principles
+
+Structure body sections around the insights a reader can act on or carry forward. Do not organize around the source material's sequence unless that sequence is the best reader sequence.
+
+### Quotes Near-Verbatim
+
+Quote speakers with fidelity to their actual words. Minor grammatical cleanup is acceptable. Do not paraphrase a direct quote and present it as a quote. If you cannot quote exactly, use indirect attribution.
+
+### Never Fabricate
+
+Do not invent statistics, study names, speaker quotes, dates, or institutional details. If information is not in the source material, use a placeholder: `[specific data needed]`. Placeholders are preferable to fabrications.
+
+### Evergreen Where Possible
+
+Write in a way that will not be immediately dated. Avoid "this week," "recently," "just published" — use the specific date or publication name instead.
+
+### Speaker Attribution
+
+Name speakers on first mention with full name and title. Use last name only on subsequent mentions within the same section. Do not refer to speakers as "the expert" or "the researcher" — use their name.
+
+### Conviction, Not Dramatization
+
+State positions directly when the evidence supports them. Do not manufacture urgency through exclamation points, all-caps, or breathless phrasing. Earned intensity comes from the weight of the evidence, not from theatrical framing.
+
+### Strongest Findings Proportional
+
+Lead with the findings that are most supported and most significant. Do not bury the main finding in a middle section. If the study's central finding is X, X should appear in the intro or the first body section.
+
+### Cumulative Burden Framing
+
+When presenting multiple findings, build toward a conclusion. Do not list findings as isolated data points. Connect them: this plus this plus this means something.
+
+---
+
+## Formatting Rules
+
+### Markdown
+
+Use pure markdown. No HTML. No inline styles.
+
+### Colons in Lists
+
+Use colons to introduce lists: `**Key finding:** explanation`. Do not use en-dashes or em-dashes as list introducers.
+
+### Em-Dashes
+
+Use sparingly — only when a comma or parenthetical won't do. Not more than two per piece.
+
+### One Idea Per Visual Block
+
+Each image, callout, or embedded asset should stand alone visually. Do not stack two visual elements without prose between them.
+
+### Bold One Phrase Per Section
+
+Every H2 section should have exactly one bolded key phrase — the most important takeaway for a scanner. Do not bold entire sentences or multiple phrases per section.
+
+### Bold Keyword in H2s
+
+H2 section headers should contain the most important keyword for that section. Write headers that communicate the section's core argument, not just its topic.
+
+### No Unearned Jargon
+
+Define any medical term, acronym, or technical concept on first use. Format: `[term] ([brief plain-language definition])`. Do not assume the reader knows clinical terminology.
+
+### Single-Sentence Paragraphs
+
+Acceptable when the sentence carries enough weight to stand alone. Not acceptable as padding or as a substitute for developing an argument.
+
+### 3+ Findings = Bullet List
+
+When presenting three or more discrete findings, use a bullet list. Prose strings of findings are harder to scan and easier to misread.
+
+### Multiple Sub-Topics = Bold Sub-Headers + Preview List
+
+When a section covers more than two distinct sub-topics, introduce them with a brief preview list before the sub-headers. This helps scanners navigate.
+
+---
+
+## AI Tells to Avoid
+
+These phrases signal AI-generated content and must not appear in any draft:
+
+- "In today's rapidly evolving..."
+- "In the realm of..."
+- "It's worth noting that..."
+- "It is important to note that..."
+- "At its core,..."
+- "Let's delve into..."
+- "This begs the question..."
+- "In conclusion,..."
+- "Moreover,..." (as a paragraph opener — occasional mid-sentence use is fine)
+- "Furthermore,..." (as a paragraph opener)
+- "That being said,..."
+- "Navigate the complexities of..."
+- "Unlock the potential of..."
+- "Leverage" (when "use" will do)
+- "Robust" (as a generic intensifier)
+- "Comprehensive" (as a generic intensifier)
+- "Innovative" (without specific description of what is new)
+- "Cutting-edge" (without specific description)
+- "Seamless" (as a generic positive)
+- "Deep dive"
+- "Unpack"
+- "Explore" (as a verb for what the piece will do — use "examine," "analyze," or "show")
+
+If three or more AI tells appear in a draft, the Brand Voice score drops one letter grade.
+
+---
+
+## IMA Terminology
+
+| Avoid | Use Instead | Why |
+|-------|-------------|-----|
+| FLCCC | IMA / Independent Medical Alliance | Rebrand complete |
+| "Cure" (unqualified) | "Protocol," "approach," "may help with" | Precision |
+| "Treatment" (unqualified) | "Protocol," "approach" | Precision |
+| "You should" | "You may consider," "Research suggests" | Patient autonomy |
+| "Alternative medicine" | "Integrative medicine," "complementary approaches" | Accurate framing |
+| "Big Pharma" (as sole descriptor) | Name the company, or "pharmaceutical industry" | Credibility |
+| "We believe" (for science) | "Evidence shows," "Research indicates" | Evidence-based positioning |
+| "Anti-vaccine" (describing IMA) | "Pro-informed-consent," "independent" | Accuracy |
+
+---
+
+## Independence Signal
+
+At least one of the following must appear in any long-form piece:
+
+- "Independent" in the organizational description
+- "No pharma funding" or equivalent
+- "501(c)(3) nonprofit" identification
+- "Funded by people" / "funded by donors" language
+
+Social posts are exempt — the profile bio carries this. Op-eds and statements are not exempt.

package/plugins/ima-claude/skills/agentic-workflows/references/standards/outline-format.md

@@ -0,0 +1,110 @@
+# Outline Format
+
+Structural rules for outlines produced by the outline phase. Injected by the consumer when the recipe declares this file.
+
+---
+
+## What an Outline Is
+
+An outline is a structural proposal in bullet points. It is not a draft. It contains no prose paragraphs. It communicates architecture — what sections exist, in what order, what each section argues, and where visual elements land.
+
+The outline is the contract between the outline phase and the draft phase. The draft phase follows the outline unless a deviation is explicitly documented.
+
+---
+
+## Governing Principle
+
+Structure around reader needs, not source material architecture.
+
+The source material (transcript, study, press release) has its own sequence driven by how it was produced. That sequence is rarely the best sequence for a reader encountering the material for the first time. The outline phase's job is to find the reader's sequence.
+
+Ask: what does the reader need to know first to understand what comes next? Start there.
+
+---
+
+## Required Elements
+
+Every outline must contain these elements in this order:
+
+### Title
+A proposed headline. Clear, specific, benefit-oriented. Not a topic label — a claim or a promise. The draft phase may refine it, but the outline provides a working title.
+
+### Intro
+Three components:
+- **Hook** — the entry point that earns the reader's attention. One sentence. Can be a bold claim, a striking finding, a tension, or a question the reader is already asking.
+- **Frame** — what this piece is about and why it matters now. One to two sentences.
+- **Setup** — what the reader will get from reading. One sentence.
+
+### Body Sections (3–5)
+For each section:
+- **Section title** — communicates the core argument, not just the topic
+- **Core argument** — one sentence stating what this section claims
+- **Key points** — bullet list of the specific evidence, data, or ideas that support the core argument
+- **Asset placements** — where images, video embeds, or CTAs land within this section (if applicable)
+- **Quote placements** — where blockquotes land inline, with the speaker and a fragment of the quote
+
+Sections must not overlap in argument. If two sections are making the same point, merge them.
+
+### Related Reading
+Three to five links or resource types. Can be TBD if assets are not yet confirmed. Include a brief description of each.
+
+### Editorial Watch Items
+Things the draft phase should pay special attention to:
+- Naming sensitivities (speakers, institutions, studies)
+- Attribution requirements (quotes that must be near-verbatim)
+- Gaps that need `[bracket]` treatment
+- Recipe-specific requirements the draft phase must apply
+- Anything from the gather phase gaps section that was not resolved
+
+### Word Target
+Carry forward from the gather phase. If the outline reveals the scope is larger or smaller than estimated, adjust and explain the change in one sentence.
+
+---
+
+## Section Scope
+
+Each body section argues exactly one thing. The section title states that argument. Every key point in the section supports that argument. If a section has key points that pull in two directions, split it into two sections.
+
+Aim for 3–5 sections. Fewer than 3 means the content lacks depth. More than 5 means the scope is too broad or the arguments are not being consolidated.
+
+---
+
+## Visual Element Placement
+
+Apply these rules for every asset:
+
+- **No adjacent visual elements** — never place two images, embeds, or CTAs in sequence without prose between them
+- **Images break up content within sections** — place images mid-section when a section runs long, not at the top as a header image (unless the recipe specifies a hero)
+- **CTAs go between sections** — interstitial CTAs belong in the transition between sections, not embedded within a section's prose
+- **Video embeds** — typically at the top of the piece as the hero element; note this in the intro element, not a body section
+
+---
+
+## Quote Placement
+
+Quotes belong inline where they would naturally land if the reader encountered them in prose — not in a separate "Quotes" section.
+
+For each quote, mark its placement in the relevant section's key points:
+
+```
+- Quote: [Speaker last name]: "[fragment of quote]" — after point about [topic]
+```
+
+Blockquote format in the draft:
+```
+> [Speaker Name]: "exact or near-verbatim quote"
+```
+
+Select quotes that advance the section's core argument. Do not include quotes for variety or because they seem interesting. Every quote should be the best available evidence for the point it follows.
+
+---
+
+## What Does NOT Belong in an Outline
+
+- Prose paragraphs — outlines use bullets, not paragraphs
+- Every detail from the source material — only what advances the reader's understanding
+- Meta descriptions — these belong in the draft
+- A separate "Quotes" section — quotes go inline
+- The source material's own section structure — unless it happens to be the best reader sequence
+- Stacked visual elements — no two adjacent assets
+- Speculative sections — if you are not confident a section belongs, it does not belong

package/plugins/ima-claude/skills/agentic-workflows/references/templates/avada-construction-guide.md

@@ -0,0 +1,263 @@
+# Avada/Fusion Builder Construction Guide
+
+General reference for building IMA blog posts and editorial pages in the WordPress backend using Fusion Builder shortcode markup. This document covers building blocks, syntax patterns, and placement principles. It is content-type agnostic. Content-type-specific templates (webinar summaries, research posts, etc.) live in their respective project instruction files and reference this guide for construction mechanics.
+
+---
+
+## Core Container Structure
+
+Every post is wrapped in a single container → row → column stack:
+
+```
+[fusion_builder_container]
+  [fusion_builder_row]
+    [fusion_builder_column type="1_1"]
+      <!-- all content blocks go here -->
+    [/fusion_builder_column]
+  [/fusion_builder_row]
+[/fusion_builder_container]
+```
+
+This outer wrapper never changes. Copy verbatim from any existing post.
+
+---
+
+## Content Block Types
+
+### Text Block
+The workhorse. Used for body paragraphs, bullet lists, blockquotes, and inline links.
+
+```
+[fusion_text]
+<p>Paragraph content here with <strong>strategic bold</strong> for emphasis.</p>
+
+<blockquote>"Speaker quote here." — <strong>Name</strong></blockquote>
+
+<ul>
+  <li><strong>Label:</strong> Description text</li>
+  <li><strong>Label:</strong> Description text</li>
+</ul>
+[/fusion_text]
+```
+
+**Usage notes:**
+- One `fusion_text` block per logical content section. Don't cram an entire post into one block.
+- Break into new blocks at natural visual anchor points: before/after images, at section transitions.
+- `<strong>` for emphasis within paragraphs. Don't bold entire sentences.
+- `<blockquote>` for speaker/researcher quotes with em-dash attribution.
+
+### Title Block
+Used for section headers and styled intro text.
+
+```
+[fusion_title title_type="text" style_type="none" title_tag="h2"]
+<strong>N.</strong> Section Title
+[/fusion_title]
+```
+
+For styled intro blocks (non-heading text that needs title-level formatting):
+
+```
+[fusion_title title_type="text" style_type="none" size="div"]
+Intro text styled as a title block
+[/fusion_title]
+```
+
+**Usage notes:**
+- Numbered sections use `<h2><strong>N.</strong> Section Title</h2>` inside a `fusion_text` block (not `fusion_title`) for consistency with existing posts.
+- `fusion_title` is primarily for standalone headers and styled intro text.
+
+### Image Block
+Used for slide images, diagrams, headshots, promo graphics, and resource covers.
+
+```
+[fusion_imageframe
+  image_id="ATTACHMENT_ID|full"
+  style_type="none"
+  alt="Descriptive alt text"
+  align="center"
+  lightbox="yes"
+  margin_top="20px"
+  margin_bottom="20px"]
+  https://imahealth.org/wp-content/uploads/path/to/image.jpg
+[/fusion_imageframe]
+```
+
+**Lightbox rules:**
+- `lightbox="yes"` for diagrams, charts, slides, data tables — anything the reader might want to zoom into
+- `lightbox="no"` for promo images and linked graphics. Add `link` attribute when the image should click through to a page.
+
+**Sizing:**
+- Headshots: `max_width="200"` in a `1_4` column
+- Slide images: full-width within the content column
+- Promo images: full-width, linked, no lightbox
+
+**Border treatment for covers, figures, and charts:**
+- Study covers, guide covers, book covers, figures, charts, and graphs: `bordersize="3" bordercolor="#00066f" borderradius="10"`
+- This applies to any image that represents a document or data visualization. It does not apply to promo images, headshots, or hero images.
+
+**External links:**
+- All links to external sites (anything outside imahealth.org) must include `linktarget="_blank"` on imageframes and `target="_blank"` on `<a>` tags within fusion_text blocks.
+
+**Video embed spacing:**
+- The first `fusion_text` block after a video embed should include `margin_top="30px"` for breathing room between the video player and the body text.
+
+### Button Block
+Used for CTAs (forums, donation, external links).
+
+```
+[fusion_button
+  link="https://imahealth.org/forums/"
+  icon="fa-comments fas"
+  alignment="center"]
+  Continue the conversation at the Forums
+[/fusion_button]
+```
+
+### Separator Block
+Used for visual breaks between major sections.
+
+```
+[fusion_separator style_type="single solid" sep_color="#e0e0e0" border_size="2"][/fusion_separator]
+```
+
+### Code Block (for embeds)
+Used for video embeds and any content requiring base64-encoded shortcodes.
+
+```
+[fusion_code]BASE64_ENCODED_SHORTCODE_HERE[/fusion_code]
+```
+
+**Common use:** Cloudflare stream video embeds. Encode the stream shortcode as base64 and place inside `fusion_code`.
+
+---
+
+## Layout Patterns
+
+### Single Column (default)
+Most content uses the outer 1_1 column. No inner rows needed.
+
+### Two-Column Split (e.g., resource covers, side-by-side elements)
+Nested inner row with two half-width columns:
+
+```
+[fusion_builder_row_inner]
+  [fusion_builder_column_inner type="1_2"]
+    [fusion_imageframe ...]image_url[/fusion_imageframe]
+    [fusion_text]<p style="text-align: center;"><strong>Title</strong><br>One-line description</p>[/fusion_text]
+  [/fusion_builder_column_inner]
+  [fusion_builder_column_inner type="1_2"]
+    [fusion_imageframe ...]image_url[/fusion_imageframe]
+    [fusion_text]<p style="text-align: center;"><strong>Title</strong><br>One-line description</p>[/fusion_text]
+  [/fusion_builder_column_inner]
+[/fusion_builder_row_inner]
+```
+
+**Use when:** Featuring two related resources side by side (PDF covers, guide pairs, before/after comparisons).
+
+### Headshot + Bio (e.g., expert profiles, author intros)
+Quarter-width image column + three-quarter text column:
+
+```
+[fusion_builder_row_inner]
+  [fusion_builder_column_inner type="1_4"]
+    [fusion_imageframe image_id="ID|full" max_width="200" style_type="none" align="center"]
+      headshot_url
+    [/fusion_imageframe]
+  [/fusion_builder_column_inner]
+  [fusion_builder_column_inner type="3_4"]
+    [fusion_text]
+    <p><strong>Name</strong><br><em>Title, Credentials</em></p>
+    <p>Bio paragraph.</p>
+    [/fusion_text]
+  [/fusion_builder_column_inner]
+[/fusion_builder_row_inner]
+```
+
+**Credential structure:** Keep parallel across multiple experts. If some lack titles/achievements, simplify everyone to the same level of detail (e.g., institution affiliation only).
+
+---
+
+## Interstitials (Global Blocks)
+
+Reusable CTA blocks stored as Fusion Builder globals. Each global block requires the full `row_inner` → `column_inner` → content structure inline. The `fusion_global` attribute syncs with WordPress, but **the inline content is what renders**. Never swap a global ID without swapping the full content block.
+
+**Available blocks and their full markup live in the CTA Block Catalog** (`cta-block-catalog.md`). That file is the single source of truth for all globals. Copy the markup verbatim from the catalog when placing CTAs in post markup.
+
+### Placement Principles
+
+- One interstitial every 1–2 sections
+- Never back to back
+- Place at natural pause points, not mid-argument
+- Engagement CTAs (Journal, Research Hub, Substack, Conference) go earlier in the post as informational breaks
+- Donation CTAs are the ask: they go late, typically before the emotional close or final section
+- Match the donation CTA to the content topic (webinar → Webinar Donation, cancer → Cancer Research Donation, research study → Research Donation, journal → Journal Donation). The CTA catalog has usage notes for each block.
+
+---
+
+## Image Placement Decision Framework
+
+1. **Does the section introduce a visual concept (framework, diagram, cycle)?** → Place the corresponding image immediately after the text introduces it, before the next paragraph continues.
+
+2. **Are new resources being released?** → Use the two-column PDF cover split in the section that introduces them.
+
+3. **Is there a contextually relevant promo?** → Place after the final body section. Must be earned by the content (e.g., speakers mentioned in the post are at the conference).
+
+4. **Are there 2+ sections in a row without a visual break?** → Insert an interstitial between them.
+
+5. **Does the post feel visually dense in the middle?** → Rearrange interstitials to create breathing room.
+
+---
+
+## TODO Placeholders
+
+Use these standardized placeholders in templates. Replace before publishing.
+
+| Placeholder Pattern | What to Replace With |
+|---------------------|---------------------|
+| `VIDEO_EMBED_BASE64_HERE` | Base64-encoded fusion_code shortcode |
+| `*_HEADSHOT_ID` | WordPress media library attachment ID |
+| `PATH_TO_*.jpg` | Full URL path to image in media library |
+| `*_COVER_ID` | Media library ID for guide/resource cover images |
+| Any `image_id="*_ID\|full"` | Actual WordPress attachment ID |
+
+---
+
+## Related Reading Block
+
+Standard footer block before the forums button. Curated links relevant to the post content.
+
+```
+[fusion_text]
+<h2>Related Reading</h2>
+<ul>
+  <li><strong>Label:</strong> <a href="URL">Title</a></li>
+  <li><strong>Label:</strong> <a href="URL">Title</a></li>
+</ul>
+[/fusion_text]
+```
+
+**Format:** Bold type label + linked title. No descriptions. Labels indicate content type (Guide, Monograph, Webinar, Hub, etc.).
+
+---
+
+## Forums Button (standard footer)
+
+Appears at the bottom of every post. Copy verbatim.
+
+```
+[fusion_button link="/forums/" icon="fa-comments fas" alignment="center"]
+  Continue the conversation at the Forums
+[/fusion_button]
+```
+
+---
+
+## Transition to LiveCanvas / Bootstrap
+
+When the environment changes, the principles carry over:
+
+- **Content structure** (intro → experts → body sections → related reading) doesn't change
+- **Image placement logic** doesn't change
+- **Interstitial placement logic** doesn't change
+- **What changes:** The markup language. Fusion Builder shortcodes become Bootstrap utility classes and HTML. This document will be updated with new markup patterns, but the structural logic transfers directly.