@openpresentation/opf 0.10.1 → 0.11.1

package/dist/spec/catalogs/languages/nepali.json

@@ -4,6 +4,9 @@
   "name": "Nepali",
   "code": "NEP",
   "bcp47": "ne",
+  "ooxmlLang": "ne-NP",
+  "script": "Deva",
+  "direction": "ltr",
   "fontScheme": "mangal",
   "googleFontScheme": "noto-sans-devangari"
 }

package/dist/spec/catalogs/languages/norwegian.json

@@ -4,6 +4,9 @@
   "name": "Norwegian",
   "code": "NOR",
   "bcp47": "no",
+  "ooxmlLang": "nb-NO",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/odia.json

@@ -4,6 +4,9 @@
   "name": "Odia",
   "code": "ORI",
   "bcp47": "or",
+  "ooxmlLang": "or-IN",
+  "script": "Orya",
+  "direction": "ltr",
   "fontScheme": "kalinga",
   "googleFontScheme": "noto-sans-oriya"
 }

package/dist/spec/catalogs/languages/oromo.json

@@ -4,6 +4,9 @@
   "name": "Oromo",
   "code": "ORM",
   "bcp47": "om",
+  "ooxmlLang": "om-ET",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/pashto.json

@@ -4,6 +4,9 @@
   "name": "Pashto",
   "code": "PUS",
   "bcp47": "ps",
+  "ooxmlLang": "ps-AF",
+  "script": "Arab",
+  "direction": "rtl",
   "fontScheme": "arial",
   "googleFontScheme": "noto-sans-arabic"
 }

package/dist/spec/catalogs/languages/persian.json

@@ -4,6 +4,9 @@
   "name": "Persian",
   "code": "FAS",
   "bcp47": "fa",
+  "ooxmlLang": "fa-IR",
+  "script": "Arab",
+  "direction": "rtl",
   "fontScheme": "arabic-typesetting",
   "googleFontScheme": "noto-naksh-arabic"
 }

package/dist/spec/catalogs/languages/polish.json

@@ -4,6 +4,9 @@
   "name": "Polish",
   "code": "POL",
   "bcp47": "pl",
+  "ooxmlLang": "pl-PL",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/portuguese.json

@@ -4,6 +4,9 @@
   "name": "Portuguese",
   "code": "POR",
   "bcp47": "pt",
+  "ooxmlLang": "pt-BR",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/punjabi-gurmukhi.json

@@ -4,6 +4,9 @@
   "name": "Punjabi (Gurmukhi)",
   "code": "PAN",
   "bcp47": "pa-Guru",
+  "ooxmlLang": "pa-IN",
+  "script": "Guru",
+  "direction": "ltr",
   "fontScheme": "raavi",
   "googleFontScheme": "noto-sans-gurmukhi"
 }

package/dist/spec/catalogs/languages/punjabi-shahmukhi.json

@@ -4,6 +4,9 @@
   "name": "Punjabi (Shahmukhi)",
   "code": "PAN",
   "bcp47": "pa-Arab",
+  "ooxmlLang": "pa-Arab-PK",
+  "script": "Arab",
+  "direction": "rtl",
   "fontScheme": "arial",
   "googleFontScheme": "noto-nastaliq-urdu"
 }

package/dist/spec/catalogs/languages/romanian.json

@@ -4,6 +4,9 @@
   "name": "Romanian",
   "code": "RON",
   "bcp47": "ro",
+  "ooxmlLang": "ro-RO",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/russian.json

@@ -4,6 +4,9 @@
   "name": "Russian",
   "code": "RUS",
   "bcp47": "ru",
+  "ooxmlLang": "ru-RU",
+  "script": "Cyrl",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "noto-sans"
 }

package/dist/spec/catalogs/languages/serbian-cyrillic.json

@@ -4,6 +4,9 @@
   "name": "Serbian (Cyrillic)",
   "code": "SRP",
   "bcp47": "sr-Cyrl",
+  "ooxmlLang": "sr-Cyrl-RS",
+  "script": "Cyrl",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "noto-sans"
 }

package/dist/spec/catalogs/languages/serbian-latin.json

@@ -4,6 +4,9 @@
   "name": "Serbian (Latin)",
   "code": "SRP",
   "bcp47": "sr-Latn",
+  "ooxmlLang": "sr-Latn-RS",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/shona.json

@@ -4,6 +4,9 @@
   "name": "Shona",
   "code": "SNA",
   "bcp47": "sn",
+  "ooxmlLang": "sn-Latn-ZW",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/slovak.json

@@ -4,6 +4,9 @@
   "name": "Slovak",
   "code": "SLK",
   "bcp47": "sk",
+  "ooxmlLang": "sk-SK",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/slovenian.json

@@ -4,6 +4,9 @@
   "name": "Slovenian",
   "code": "SLV",
   "bcp47": "sl",
+  "ooxmlLang": "sl-SI",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/somali.json

@@ -4,6 +4,9 @@
   "name": "Somali",
   "code": "SOM",
   "bcp47": "so",
+  "ooxmlLang": "so-SO",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/spanish.json

@@ -4,6 +4,9 @@
   "name": "Spanish",
   "code": "SPA",
   "bcp47": "es",
+  "ooxmlLang": "es-ES",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/swahili.json

@@ -4,6 +4,9 @@
   "name": "Swahili",
   "code": "SWA",
   "bcp47": "sw",
+  "ooxmlLang": "sw-KE",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/swedish.json

@@ -4,6 +4,9 @@
   "name": "Swedish",
   "code": "SWE",
   "bcp47": "sv",
+  "ooxmlLang": "sv-SE",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/tagalog.json

@@ -4,6 +4,9 @@
   "name": "Tagalog",
   "code": "TGL",
   "bcp47": "tl",
+  "ooxmlLang": "fil-PH",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/tajik.json

@@ -4,6 +4,9 @@
   "name": "Tajik",
   "code": "TGK",
   "bcp47": "tg",
+  "ooxmlLang": "tg-Cyrl-TJ",
+  "script": "Cyrl",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "noto-sans"
 }

package/dist/spec/catalogs/languages/tamil.json

@@ -4,6 +4,9 @@
   "name": "Tamil",
   "code": "TAM",
   "bcp47": "ta",
+  "ooxmlLang": "ta-IN",
+  "script": "Taml",
+  "direction": "ltr",
   "fontScheme": "latha",
   "googleFontScheme": "noto-sans-tamil"
 }

package/dist/spec/catalogs/languages/telugu.json

@@ -4,6 +4,9 @@
   "name": "Telugu",
   "code": "TEL",
   "bcp47": "te",
+  "ooxmlLang": "te-IN",
+  "script": "Telu",
+  "direction": "ltr",
   "fontScheme": "gautami",
   "googleFontScheme": "noto-sans-telugu"
 }

package/dist/spec/catalogs/languages/thai.json

@@ -4,6 +4,9 @@
   "name": "Thai",
   "code": "THA",
   "bcp47": "th",
+  "ooxmlLang": "th-TH",
+  "script": "Thai",
+  "direction": "ltr",
   "fontScheme": "angsana-new",
   "googleFontScheme": "noto-sans-thai"
 }

package/dist/spec/catalogs/languages/turkish.json

@@ -4,6 +4,9 @@
   "name": "Turkish",
   "code": "TUR",
   "bcp47": "tr",
+  "ooxmlLang": "tr-TR",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/ukrainian.json

@@ -4,6 +4,9 @@
   "name": "Ukrainian",
   "code": "UKR",
   "bcp47": "uk",
+  "ooxmlLang": "uk-UA",
+  "script": "Cyrl",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "noto-sans"
 }

package/dist/spec/catalogs/languages/urdu.json

@@ -4,6 +4,9 @@
   "name": "Urdu",
   "code": "URD",
   "bcp47": "ur",
+  "ooxmlLang": "ur-PK",
+  "script": "Arab",
+  "direction": "rtl",
   "fontScheme": "arabic-typesetting",
   "googleFontScheme": "noto-nastaliq-urdu"
 }

package/dist/spec/catalogs/languages/uzbek-latin.json

@@ -4,6 +4,9 @@
   "name": "Uzbek (Latin)",
   "code": "UZB",
   "bcp47": "uz-Latn",
+  "ooxmlLang": "uz-Latn-UZ",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/vietnamese-quoc-ngu.json

@@ -4,6 +4,9 @@
   "name": "Vietnamese (Quốc Ngữ)",
   "code": "VIE",
   "bcp47": "vi-Latn",
+  "ooxmlLang": "vi-VN",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/xhosa.json

@@ -4,6 +4,9 @@
   "name": "Xhosa",
   "code": "XHO",
   "bcp47": "xh",
+  "ooxmlLang": "xh-ZA",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/yoruba.json

@@ -4,6 +4,9 @@
   "name": "Yoruba",
   "code": "YOR",
   "bcp47": "yo",
+  "ooxmlLang": "yo-NG",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/languages/zulu.json

@@ -4,6 +4,9 @@
   "name": "Zulu",
   "code": "ZUL",
   "bcp47": "zu",
+  "ooxmlLang": "zu-ZA",
+  "script": "Latn",
+  "direction": "ltr",
   "fontScheme": "aptos",
   "googleFontScheme": "roboto"
 }

package/dist/spec/catalogs/narratives/board-meeting.json

@@ -24,7 +24,7 @@
       "id": "introduction",
       "name": "Introduction",
       "description": "Set the tone for the meeting and walk through the agenda in one slide. Signal which sections are for discussion versus information so directors know where their time is most valuable.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Set the tone",
       "slideType": "text"
     },
@@ -34,7 +34,7 @@
       "description": "Deliver the CEO's view of the period: what changed, what mattered, where the company stands. Two or three sentences in the speaker's voice — board members read this slide first.",
       "instructions": "Deliver company insights",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "highlights",
@@ -42,7 +42,7 @@
       "description": "Share major successes across the business. Customer wins, launches, hires, milestones. Specific and brief; this is the slide that sets the tone, not the slide that proves the case.",
       "instructions": "Share major successes",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "challenges",
@@ -50,7 +50,7 @@
       "description": "Address the obstacles facing the business honestly. Boards earn their value when surfaced to real problems; under-disclosure here erodes trust faster than the problems themselves.",
       "instructions": "Address potential obstacles",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "company-needs",
@@ -58,7 +58,7 @@
       "description": "Identify where the business needs the board's help: introductions, decisions, advice. Specific asks turn the meeting from a report into a working session.",
       "instructions": "Identify support requirements",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "funnel-metrics",
@@ -66,7 +66,7 @@
       "description": "Discuss the sales pipeline: leads, conversion, velocity, win rate. Use the metrics that match the company's current motion; resist the temptation to show the same chart you showed last quarter for continuity's sake.",
       "instructions": "Discuss sales progress",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "engagement-metrics",
@@ -74,7 +74,7 @@
       "description": "Analyze customer interaction: usage, retention, NPS, expansion. Show whether the product is being loved or only being bought.",
       "instructions": "Analyze customer interaction",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "financial-metrics",
@@ -82,7 +82,7 @@
       "description": "Review fiscal health: revenue, gross margin, burn, runway, cash. One slide directors can scan in twenty seconds and trust the numbers on.",
       "instructions": "Review fiscal health",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "performance-vs-plan",
@@ -90,7 +90,7 @@
       "description": "Compare actuals to plan across the metrics that matter most. Variance is the slide directors will probe; show your work, name the drivers, propose adjustments.",
       "instructions": "Compare objectives and actuals",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "org-chart",
@@ -98,7 +98,7 @@
       "description": "Present the team structure and any key changes since the last meeting. Directors track org evolution as a leading indicator; help them see hires, departures, and reshapes clearly.",
       "instructions": "Present team structure",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "product-roadmap",
@@ -106,7 +106,7 @@
       "description": "Highlight the product plan and what ships when. Pair each major bet with the customer or business outcome it serves.",
       "instructions": "Highlight future plans",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "quality",
@@ -114,7 +114,7 @@
       "description": "Showcase the product quality bar: reliability, defect rates, support outcomes. Directors take quality as a proxy for engineering culture; let the data speak.",
       "instructions": "Showcase product's standards",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "engineering-update",
@@ -122,7 +122,7 @@
       "description": "Communicate technical progress, key bets, and platform investments. Translate engineering work into business consequences directors can evaluate.",
       "instructions": "Communicate technical progress",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "marketing-update",
@@ -130,7 +130,7 @@
       "description": "Update on demand-gen, brand, and category-shaping efforts. Connect spend to pipeline and pipeline to revenue; avoid 'campaigns we ran' lists.",
       "instructions": "Update on promotional efforts",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "business-development-update",
@@ -138,7 +138,7 @@
       "description": "Speak to growth initiatives: partnerships, channels, alliances. Each entry should have a stage, an owner, and a credible upside.",
       "instructions": "Speak on growth initiatives",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "operations-update",
@@ -146,7 +146,7 @@
       "description": "Discuss day-to-day operations: people ops, finance, legal, IT. Brief but explicit — directors notice when ops is missing.",
       "instructions": "Discuss day-to-day activities",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "special-topic-1",
@@ -154,7 +154,7 @@
       "description": "Discuss the period's first deep-dive topic. This is where the board does its highest-leverage work; pose the question, show the analysis, ask for their view.",
       "instructions": "Discuss selected subject",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "special-topic-2",
@@ -162,7 +162,7 @@
       "description": "Cover the second deep-dive topic, framed the same way. Two specials per meeting; more, and the meeting becomes a recital.",
       "instructions": "Touch on additional topic",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "feedback",
@@ -170,7 +170,7 @@
       "description": "Elicit the board's perspective with concrete prompts. The strength of board governance is in its candor — invite it explicitly.",
       "instructions": "Elicit board's thoughts",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "formalities",
@@ -178,13 +178,13 @@
       "description": "Conclude with the necessary governance items: votes, approvals, committee reports, document acknowledgments. Run them efficiently and document the outcomes.",
       "instructions": "Conclude with necessary formalities",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "closing-remarks",
       "name": "Closing Remarks",
       "description": "Close with concluding observations and the agenda for the next meeting. End on a forward-looking note; directors should leave knowing what to watch.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Concluding observations",
       "slideType": "text"
     }

package/dist/spec/catalogs/narratives/business-narrative.json

@@ -25,7 +25,7 @@
       "description": "Engage the audience and set expectations for the next twenty minutes. Tell them you're going to tell them a story — and then start telling it. Avoid a separate agenda slide; the introduction is the first scene.",
       "instructions": "Engage and set expectations",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "setting",
@@ -33,7 +33,7 @@
       "description": "Establish the world the story takes place in: the team, the market, the moment. Just enough context that the challenge will feel meaningful when it arrives.",
       "instructions": "Establish the environment",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "challenge",
@@ -41,7 +41,7 @@
       "description": "Identify the issue at hand. Concrete, specific, attributable. The challenge is the inciting incident — the thing that pulled the rest of the story into motion.",
       "instructions": "Identify the issue at hand",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "tension",
@@ -49,7 +49,7 @@
       "description": "Raise the stakes. What happens if the challenge isn't met? Quantify the cost, name the people affected, surface the trade-offs that make the choice hard. Tension is what makes the audience lean in.",
       "instructions": "Emphasize the stakes",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "solution",
@@ -57,7 +57,7 @@
       "description": "Reveal the strategy or hero of the story. Lead with what changes for the audience or customer when the solution is in place. This is the turn from problem to promise.",
       "instructions": "Present the hero/strategy",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "implementation",
@@ -65,7 +65,7 @@
       "description": "Describe the path to success. Phases, owners, milestones, key bets. Show the audience that the solution has weight behind it — not just intent.",
       "instructions": "Describe the path to success",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "recap",
@@ -73,13 +73,13 @@
       "description": "Bring the audience back to the surface with a clear summary of what was said and decided. Echo the language from the opening so the story feels closed.",
       "instructions": "Review key points and insights",
       "slideType": "text",
-      "layoutHint": "text-1x-left"
+      "layoutHint": "text-1x"
     },
     {
       "id": "conclusion",
       "name": "Conclusion",
       "description": "Reinforce the key message and the call to action. End on the line you most want repeated in tomorrow's hallway conversations.",
-      "layoutHint": "title-left",
+      "layoutHint": "title",
       "instructions": "Reinforce takeaways and call to action",
       "slideType": "text"
     }