@openpresentation/opf 0.11.0 → 0.11.2

package/dist/spec/catalogs/narratives/index.json

@@ -21,6 +21,33 @@
       "tags": ["executive", "strategy", "consulting", "minto", "pyramid"],
       "file": "scqa.json"
     },
+    {
+      "id": "pyramid-principle",
+      "name": "Pyramid Principle",
+      "summary": "Lead with your conclusion, then provide supporting logic. Respects audience time and attention.",
+      "audienceFit": ["executive", "board", "time-pressed-decision-makers"],
+      "durationRange": { "minMinutes": 5, "maxMinutes": 20 },
+      "tags": ["executive", "strategy", "deductive", "recommendation"],
+      "file": "pyramid-principle.json"
+    },
+    {
+      "id": "situation-complication-resolution",
+      "name": "Situation-Complication-Resolution",
+      "summary": "McKinsey-style structure that builds tension before delivering insights.",
+      "audienceFit": ["senior-leadership", "consultants", "strategy-teams"],
+      "durationRange": { "minMinutes": 5, "maxMinutes": 20 },
+      "tags": ["strategy", "consulting", "minto", "recommendation"],
+      "file": "situation-complication-resolution.json"
+    },
+    {
+      "id": "what-so-what-now-what",
+      "name": "What-So What-Now What",
+      "summary": "Concise framework that connects information to meaning to action. Perfect for executive audiences.",
+      "audienceFit": ["executive", "senior-managers", "board"],
+      "durationRange": { "minMinutes": 5, "maxMinutes": 15 },
+      "tags": ["executive", "briefing", "analytical", "action"],
+      "file": "what-so-what-now-what.json"
+    },
     {
       "id": "strategic-narrative",
       "name": "Strategic Narrative",
@@ -93,6 +120,15 @@
       "tags": ["sales", "go-to-market", "outbound", "discovery"],
       "file": "persuasive-sales.json"
     },
+    {
+      "id": "sparkline",
+      "name": "Sparkline",
+      "summary": "A tight comparison arc showing the transformation from an inferior state to a superior one, anchored by contrast.",
+      "audienceFit": ["prospective-buyers", "skeptical-stakeholders", "evaluation-committees"],
+      "durationRange": { "minMinutes": 3, "maxMinutes": 15 },
+      "tags": ["contrast", "transformation", "product", "roi"],
+      "file": "sparkline.json"
+    },
     {
       "id": "company-intro",
       "name": "Company Intro",
@@ -147,6 +183,15 @@
       "tags": ["management", "proposal", "internal", "planning"],
       "file": "project-proposal.json"
     },
+    {
+      "id": "vision-roadmap",
+      "name": "Vision to Roadmap",
+      "summary": "Connects a compelling long-term vision to near-term executable plans, bridging aspiration and action.",
+      "audienceFit": ["leadership-teams", "board", "product-and-strategy-teams", "all-hands"],
+      "durationRange": { "minMinutes": 15, "maxMinutes": 45 },
+      "tags": ["strategy", "roadmap", "planning", "vision"],
+      "file": "vision-roadmap.json"
+    },
     {
       "id": "failure-analysis",
       "name": "Failure Analysis",
@@ -156,6 +201,15 @@
       "tags": ["postmortem", "incident", "review", "accountability"],
       "file": "failure-analysis.json"
     },
+    {
+      "id": "star-method",
+      "name": "STAR Method",
+      "summary": "Results-focused framework that demonstrates impact through concrete examples.",
+      "audienceFit": ["hr-and-talent", "performance-reviewers", "award-committees"],
+      "durationRange": { "minMinutes": 5, "maxMinutes": 15 },
+      "tags": ["case-study", "proof", "results", "retrospective"],
+      "file": "star-method.json"
+    },
     {
       "id": "classic-story",
       "name": "Classic Story",
@@ -165,6 +219,15 @@
       "tags": ["storytelling", "general", "engagement"],
       "file": "classic-story.json"
     },
+    {
+      "id": "heros-journey",
+      "name": "Hero's Journey",
+      "summary": "Storytelling framework that takes the audience on an emotional journey of change and growth.",
+      "audienceFit": ["general-public", "employees", "community"],
+      "durationRange": { "minMinutes": 5, "maxMinutes": 20 },
+      "tags": ["storytelling", "brand", "change", "emotional"],
+      "file": "heros-journey.json"
+    },
     {
       "id": "business-narrative",
       "name": "Business Narrative",
@@ -174,6 +237,15 @@
       "tags": ["management", "storytelling", "internal", "strategy"],
       "file": "business-narrative.json"
     },
+    {
+      "id": "change-story",
+      "name": "Change Story",
+      "summary": "A change management narrative that addresses the emotional and rational objections employees face when asked to change.",
+      "audienceFit": ["employees", "team-leads", "cross-functional-teams"],
+      "durationRange": { "minMinutes": 15, "maxMinutes": 45 },
+      "tags": ["change-management", "transformation", "internal", "alignment"],
+      "file": "change-story.json"
+    },
     {
       "id": "rags-to-riches",
       "name": "Rags to Riches",
@@ -327,6 +399,15 @@
       "tags": ["data-driven", "forecasting", "strategy", "analysis"],
       "file": "trend-analysis.json"
     },
+    {
+      "id": "data-story",
+      "name": "Data Story",
+      "summary": "A data-first narrative that builds from evidence to insight to action, ideal for analysts and data-driven teams.",
+      "audienceFit": ["data-teams", "operations-and-finance", "product-managers", "analytics-stakeholders"],
+      "durationRange": { "minMinutes": 10, "maxMinutes": 30 },
+      "tags": ["analytics", "data", "insight", "recommendation"],
+      "file": "data-story.json"
+    },
     {
       "id": "employee-review",
       "name": "Employee Review",

package/dist/spec/catalogs/narratives/pyramid-principle.json

@@ -0,0 +1,48 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "pyramid-principle",
+  "name": "Pyramid Principle",
+  "summary": "Lead with your conclusion, then provide supporting logic. Respects audience time and attention.",
+  "description": "Lead with the conclusion, then provide the supporting logic. State the main recommendation up front, follow with three or four arguments that support it, then back each argument with data and examples. The tone is deductive: conclusion first, reasoning second, so the audience never waits for the point. Best for executive presentations, recommendations, and time-constrained settings; typical decks run 3-8 slides (consulting recommendation, investment thesis, strategic options analysis).",
+  "audienceFit": [
+    "executive",
+    "board",
+    "time-pressed-decision-makers"
+  ],
+  "durationRange": {
+    "minMinutes": 5,
+    "maxMinutes": 20
+  },
+  "tags": [
+    "executive",
+    "strategy",
+    "deductive",
+    "recommendation"
+  ],
+  "beats": [
+    {
+      "id": "answer-first",
+      "name": "Answer First",
+      "description": "Lead with your main point or recommendation. Don't make executives wait for it.",
+      "instructions": "Lead with the conclusion or recommendation.",
+      "slideType": "text",
+      "layoutHint": "title"
+    },
+    {
+      "id": "key-arguments",
+      "name": "Key Arguments",
+      "description": "Provide 3-4 supporting reasons that logically support your answer.",
+      "instructions": "Group the main reasons supporting the answer.",
+      "slideType": "text",
+      "layoutHint": "text-3x"
+    },
+    {
+      "id": "supporting-evidence",
+      "name": "Supporting Evidence",
+      "description": "Back each argument with data, examples, or proof points.",
+      "instructions": "Back each argument with verifiable proof.",
+      "slideType": "chart",
+      "layoutHint": "chart-1x"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/situation-complication-resolution.json

@@ -0,0 +1,56 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "situation-complication-resolution",
+  "name": "Situation-Complication-Resolution",
+  "summary": "McKinsey-style structure that builds tension before delivering insights.",
+  "description": "A McKinsey-style structure that builds tension before delivering the insight. Establish the context everyone already agrees on, introduce what has changed or what challenge has emerged, name the key question that change raises, then deliver the recommendation that resolves it. The tone is logical: a tight causal chain from context to recommendation. Best for strategy presentations, consulting decks, and analytical reports; typical decks run 4-10 slides (management consulting report, strategic recommendation, board update).",
+  "audienceFit": [
+    "senior-leadership",
+    "consultants",
+    "strategy-teams"
+  ],
+  "durationRange": {
+    "minMinutes": 5,
+    "maxMinutes": 20
+  },
+  "tags": [
+    "strategy",
+    "consulting",
+    "minto",
+    "recommendation"
+  ],
+  "beats": [
+    {
+      "id": "situation",
+      "name": "Situation",
+      "description": "Set the scene with relevant background and context everyone agrees on.",
+      "instructions": "State the shared context the audience already accepts.",
+      "slideType": "list",
+      "layoutHint": "list-1x"
+    },
+    {
+      "id": "complication",
+      "name": "Complication",
+      "description": "Introduce what has changed or what challenge has emerged.",
+      "instructions": "Introduce the change, risk, or tension.",
+      "slideType": "text",
+      "layoutHint": "text-2x"
+    },
+    {
+      "id": "question",
+      "name": "Question",
+      "description": "Articulate the key question that the complication raises.",
+      "instructions": "Frame the decision question raised by the complication.",
+      "slideType": "text",
+      "layoutHint": "title"
+    },
+    {
+      "id": "answer",
+      "name": "Answer",
+      "description": "Deliver your recommendation or insight that resolves the question.",
+      "instructions": "Deliver the recommendation that resolves the question.",
+      "slideType": "timeline",
+      "layoutHint": "timeline-1x"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/sparkline.json

@@ -0,0 +1,56 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "sparkline",
+  "name": "Sparkline",
+  "summary": "A tight comparison arc showing the transformation from an inferior state to a superior one, anchored by contrast.",
+  "description": "A tight comparison arc that shows the move from an inferior state to a superior one, anchored by contrast. Make the painful before state vivid, reveal the product, decision, or event that changes the trajectory, present the new reality in concrete terms, then prove it with data or testimonial. The tone is contrastive: it makes the gap between old and new viscerally clear. Best for product demos, case study summaries, ROI presentations, and before-and-after technology comparisons; typical decks run 4-6 slides.",
+  "audienceFit": [
+    "prospective-buyers",
+    "skeptical-stakeholders",
+    "evaluation-committees"
+  ],
+  "durationRange": {
+    "minMinutes": 3,
+    "maxMinutes": 15
+  },
+  "tags": [
+    "contrast",
+    "transformation",
+    "product",
+    "roi"
+  ],
+  "beats": [
+    {
+      "id": "before-state",
+      "name": "Before State",
+      "description": "Make the current pain or limitation vivid with numbers, stories, or visuals that make the problem real.",
+      "instructions": "Make the current pain or limitation vivid.",
+      "slideType": "text",
+      "layoutHint": "text-2x"
+    },
+    {
+      "id": "contrast-moment",
+      "name": "Contrast Moment",
+      "description": "Introduce the change agent, product, or decision that shifts the trajectory.",
+      "instructions": "Introduce the decision, product, or event that changes the trajectory.",
+      "slideType": "text",
+      "layoutHint": "title"
+    },
+    {
+      "id": "after-state",
+      "name": "After State",
+      "description": "Show the improved reality. Make it concrete and specific instead of relying on vague benefit language.",
+      "instructions": "Show the new reality created by the change.",
+      "slideType": "text",
+      "layoutHint": "text-1x"
+    },
+    {
+      "id": "proof",
+      "name": "Proof",
+      "description": "Validate the after state with metrics, testimonials, or third-party evidence.",
+      "instructions": "Validate the change with evidence.",
+      "slideType": "metric",
+      "layoutHint": "number-1x"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/star-method.json

@@ -0,0 +1,56 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "star-method",
+  "name": "STAR Method",
+  "summary": "Results-focused framework that demonstrates impact through concrete examples.",
+  "description": "A results-focused framework that demonstrates impact through a concrete example: the Situation, the Task you were responsible for, the Actions you took, and the measurable Result. The tone is evidential: every claim is grounded in a specific, verifiable outcome. Best for project reviews, portfolio presentations, and achievement showcases; typical decks run 4-8 slides (case study, customer success story, project retrospective).",
+  "audienceFit": [
+    "hr-and-talent",
+    "performance-reviewers",
+    "award-committees"
+  ],
+  "durationRange": {
+    "minMinutes": 5,
+    "maxMinutes": 15
+  },
+  "tags": [
+    "case-study",
+    "proof",
+    "results",
+    "retrospective"
+  ],
+  "beats": [
+    {
+      "id": "situation",
+      "name": "Situation",
+      "description": "Describe the context and background of the scenario.",
+      "instructions": "Describe the relevant context and constraints.",
+      "slideType": "text",
+      "layoutHint": "text-1x"
+    },
+    {
+      "id": "task",
+      "name": "Task",
+      "description": "Explain your specific role and responsibilities in this situation.",
+      "instructions": "Explain the responsibility or target outcome.",
+      "slideType": "list",
+      "layoutHint": "list-2x"
+    },
+    {
+      "id": "action",
+      "name": "Action",
+      "description": "Detail the specific steps you took to address the challenge.",
+      "instructions": "Detail the actions taken and choices made.",
+      "slideType": "timeline",
+      "layoutHint": "timeline-1x"
+    },
+    {
+      "id": "result",
+      "name": "Result",
+      "description": "Share the measurable outcomes and impact of your actions.",
+      "instructions": "Show measurable impact and proof.",
+      "slideType": "metric",
+      "layoutHint": "number-1x"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/vision-roadmap.json

@@ -0,0 +1,65 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "vision-roadmap",
+  "name": "Vision to Roadmap",
+  "summary": "Connects a compelling long-term vision to near-term executable plans, bridging aspiration and action.",
+  "description": "Connects a compelling long-term vision to near-term executable plans, bridging aspiration and action. Open with a specific three-to-five-year North Star, honestly diagnose the gap between today and that vision, organize the strategy into two to four named pillars, show the phased roadmap with milestones and dependencies, and end with concrete, assigned first steps for the next 30-90 days. The tone is inspirational and strategic: it creates shared direction and commitment to a plan. Best for strategic planning, annual kickoffs, product strategy, and OKR launches; typical decks run 8-20 slides.",
+  "audienceFit": [
+    "leadership-teams",
+    "board",
+    "product-and-strategy-teams",
+    "all-hands"
+  ],
+  "durationRange": {
+    "minMinutes": 15,
+    "maxMinutes": 45
+  },
+  "tags": [
+    "strategy",
+    "roadmap",
+    "planning",
+    "vision"
+  ],
+  "beats": [
+    {
+      "id": "vision",
+      "name": "Vision",
+      "description": "State the 3-5 year North Star. It should be specific, memorable, and directional rather than generic.",
+      "instructions": "Paint the future state clearly.",
+      "slideType": "text",
+      "layoutHint": "title-subtitle"
+    },
+    {
+      "id": "current-state-gap",
+      "name": "Current State Gap",
+      "description": "Honestly assess where you are today versus the vision. The gap justifies the plan.",
+      "instructions": "Define the gap between today and the vision.",
+      "slideType": "text",
+      "layoutHint": "text-2x"
+    },
+    {
+      "id": "strategic-pillars",
+      "name": "Strategic Pillars",
+      "description": "Organize the strategy into 2-4 named priority themes. Each pillar should be independently compelling.",
+      "instructions": "Name the strategic pillars that close the gap.",
+      "slideType": "text",
+      "layoutHint": "text-3x"
+    },
+    {
+      "id": "roadmap",
+      "name": "Roadmap",
+      "description": "Show the phased execution plan with timeframes, milestones, and dependencies. Gantt or swim lane formats work well.",
+      "instructions": "Sequence the initiatives over time.",
+      "slideType": "timeline",
+      "layoutHint": "timeline-1x"
+    },
+    {
+      "id": "first-steps",
+      "name": "First Steps",
+      "description": "Close with concrete, assigned actions for the next 30-90 days. Remove the gap between inspiration and execution.",
+      "instructions": "Identify the immediate moves that start execution.",
+      "slideType": "text",
+      "layoutHint": "title"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/what-so-what-now-what.json

@@ -0,0 +1,48 @@
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "what-so-what-now-what",
+  "name": "What-So What-Now What",
+  "summary": "Concise framework that connects information to meaning to action. Perfect for executive audiences.",
+  "description": "A concise framework that connects information to meaning to action. Present the facts or findings objectively, explain why they matter to this audience, then state the decisions or next steps they require. The tone is analytical: data-forward and respectful of executive time, with no scene-setting beyond what the facts need. Best for executive briefings, status updates, and research findings; typical decks run 3-6 slides (analytics report, team performance review, strategy update).",
+  "audienceFit": [
+    "executive",
+    "senior-managers",
+    "board"
+  ],
+  "durationRange": {
+    "minMinutes": 5,
+    "maxMinutes": 15
+  },
+  "tags": [
+    "executive",
+    "briefing",
+    "analytical",
+    "action"
+  ],
+  "beats": [
+    {
+      "id": "what",
+      "name": "What",
+      "description": "Present the facts, data, or findings objectively and clearly.",
+      "instructions": "Present the facts, data, or findings objectively and clearly.",
+      "slideType": "chart",
+      "layoutHint": "chart-1x"
+    },
+    {
+      "id": "so-what",
+      "name": "So What",
+      "description": "Explain the significance. Why should your audience care about this information?",
+      "instructions": "Explain the significance. Why should your audience care about this information?",
+      "slideType": "metric",
+      "layoutHint": "number-2x"
+    },
+    {
+      "id": "now-what",
+      "name": "Now What",
+      "description": "Define the action required. What decisions or next steps follow from this?",
+      "instructions": "Define the action required. What decisions or next steps follow from this?",
+      "slideType": "text",
+      "layoutHint": "title"
+    }
+  ]
+}

package/dist/spec/reference/engine-defaults.json

@@ -1,5 +1,5 @@
 {
-  "description": "Reference example of engine-side defaults consumed by an OPF runtime. Not part of the OPF document contract - engines load this file (or their own copy) at startup to fall back when an OPF document doesn't specify a value. There is no companion JSON Schema for this file: it is engine config, not a catalog record. Every catalog-referencing value below is resolved through the catalog system the same way an explicit reference in an OPF document would be (inline catalogs.<kind>.records[] -> catalogs.<kind>.source -> default catalog at https://www.pptx.gallery/<kind>). The optional catalogs.<kind>.source overrides below let a deployment redirect all default catalog fetches at once (e.g., to an internal mirror or local package), without each OPF document needing its own catalogs block. The 'chartTypes' array is in priority order: chartTypes[0] is the engine's primary chart type, chartTypes[1] secondary, chartTypes[2] tertiary.",
+  "description": "Reference example of engine-side defaults consumed by an OPF runtime. Not part of the OPF document contract - engines load this file (or their own copy) at startup to fall back when an OPF document doesn't specify a value. There is no companion JSON Schema for this file: it is engine config, not a catalog record. Every catalog-referencing value below is resolved through the catalog system the same way an explicit reference in an OPF document would be (inline catalogs.<kind>.records[] -> catalogs.<kind>.source -> default catalog at https://www.pptx.gallery/<kind>). The optional catalogs.<kind>.source overrides below let a deployment redirect all default catalog fetches at once (e.g., to an internal mirror or local package), without each OPF document needing its own catalogs block. The 'chartTypes' array is in priority order: chartTypes[0] is the engine's primary chart type, chartTypes[1] secondary, chartTypes[2] tertiary. 'fontScheme.pptx' holds the last-resort font scheme that every current engine shares: core pagination, preview, editor and PPTX export all use 'aptos' (exported by @openpresentation/opf as DEFAULT_FONT_SCHEME), so a custom theme without a font scheme is measured, previewed and exported in the same fonts. No current engine reads 'fontScheme.google': it is the intended default for a future Google Slides exporter, whose output renders in Google-hosted fonts.",
 
   "catalogs": {
     "narratives":   { "source": "https://www.pptx.gallery/narratives" },
@@ -29,7 +29,7 @@
   "chartTypes": [
     "stacked-column-3x",
     "stacked-area-3x",
-    "line-with-markers-3x"
+    "line-with-markers"
   ]
 }