Marketing
Move the budget, not the deck
Move a campaign budget with a four-line patch instead of a new copy of the deck.
A campaign plan changes every week, and every change usually means a new copy of the deck. Then someone has to work out which copy has the right budget. Here's the same plan kept as one OPF file, where a budget change is a reviewable patch.
The example is a spring launch plan from Halfmoon Kettle Co., a fictional coffee company, for its new Cold Brew Sampler. Every name and figure in it is example data.
Start with one slide
These commands use the opf CLI from @openpresentation/cli 0.27.0, the version in the video. To run them without installing anything, put npx @openpresentation/cli@0.27.0 in place of opf:
opf create deck.opf.json --title "Halfmoon Kettle Co. Spring Launch Campaign Plan"That writes a valid 242-byte deck. Each later slide is a small JSON Patch applied with opf edit -i, in this order: the goal, the audience, the channel budget, the timeline, the expected orders and the next steps.
opf edit deck.opf.json -i --patch patches/04-budget.jsonThe budget is data, not a screenshot
The budget slide is a table inside the deck. A reviewer can read it in a pull request, and an export turns it into a native table:
{
"id": "channels-budget",
"title": "Channels and budget (example data).",
"tag": "Example data",
"table": {
"columns": ["Channel", "Budget"],
"rows": [
["Email", "$4,000"],
["Paid social", "$9,000"],
["Creator partnerships", "$6,000"],
["Search", "$5,000"],
["Total", "$24,000"]
],
"alt": "Example campaign budget: email $4,000, paid social $9,000, creator partnerships $6,000, search $5,000; total $24,000."
}
}Loading preview…
The expected-orders slide is a bar chart built the same way, with columns, rows and alt text.
opf validate deck.opf.json --fail-on warning --format textdeck.opf.json: 0 findings (0 errors, 0 warnings, 0 info). Checked: syntax, schema, references, accessibility, content, layout (estimated).Moving $2,000 is a four-line patch
Halfway through planning, the team moves $2,000 from search to creators. The patch first checks that the total row still reads $24,000, and the edit fails if it doesn't. Then it changes the two cells and the table's alt text:
[
{ "op": "test", "path": "/slides/3/table/rows/4", "value": ["Total", "$24,000"] },
{ "op": "replace", "path": "/slides/3/table/rows/2/1", "value": "$8,000" },
{ "op": "replace", "path": "/slides/3/table/rows/3/1", "value": "$3,000" },
{ "op": "replace", "path": "/slides/3/table/alt", "value": "Example campaign budget after moving $2,000 from search to creators: email $4,000, paid social $9,000, creator partnerships $8,000, search $3,000; total $24,000." }
]opf edit deck.opf.json deck-variant.opf.json --patch budget-shift.patch.json
opf diff deck.opf.json deck-variant.opf.json --format text3 changes (slides: 1 modified)
Slides
~ slide #4 "Channels and budget (example data)." (id channels-budget)
~ table.rows[2][1] "$6,000" -> "$8,000"
~ table.rows[3][1] "$5,000" -> "$3,000"
~ table.alt "Example campaign budget: email $4,000, paid social $9,000, …" -> "Example campaign budget after moving $2,000 from search to …"The reviewer sees the two budget cells that moved and the alt text that describes them, not a new 7-slide file.
Check both, then hand off PowerPoint
opf validate deck.opf.json deck-variant.opf.json --fail-on warning --format textdeck.opf.json: 0 findings (0 errors, 0 warnings, 0 info). Checked: syntax, schema, references, accessibility, content, layout (estimated).
deck-variant.opf.json: 0 findings (0 errors, 0 warnings, 0 info). Checked: syntax, schema, references, accessibility, content, layout (estimated).opf convert deck-variant.opf.json deck-variant.pptxThe team gets an editable PowerPoint of the new plan, and the source still holds both versions.
Why it matters: the plan lives in one reviewed file, a budget change is a diff that anyone can read, and a test op stops a patch from applying to the wrong numbers.
CLI reference · PowerPoint is a handoff
Download the deck and the budget-shift patch. All names and figures in these examples are illustrative.