fix(examples): the engine deck stops calling a shipped backend planned - #510
Merged
Conversation
Its first page listed PPTX as "Planned" beside a version badge reading v2.1.0 — the release that shipped it, and the release whose own copy of this deck is published as a .pptx. Three more sentences dated from when PDF was the only output: the library described as generating "structured business PDF documents", the pipeline ending at "PDFBox writes the bytes", and page two headed "From one Java file to a designed PDF". PPTX is now the live @beta backend it is, ordered ahead of the semantic-only DOCX export, and the prose covers both formats. The layout baseline moves with it. The only structural change is the backend cards reordering — Backend_PPTX shifts one position, the node count is unchanged — plus the tagline growing from one line to two and the sections below shifting by that height.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The deck contradicted itself on its own first page. The Output Backends column listed
PPTX as Planned, next to a version badge reading v2.1.0 — the release that shipped
it, and the release whose copy of this very deck is published as
engine-deck.pptx.Three more sentences dated from when PDF was the only output:
EngineDeckV2Example— the module-first deck — carries none of these, so this isconfined to one file pair.
What
EngineDeckData.backends(): PPTX becomes the live@Betabackend, ordered ahead ofthe semantic-only DOCX export.
it now cover both formats.
Tests
./mvnw -B -ntp clean verify→BUILD SUCCESS.The layout baseline was updated after diffing it rather than on sight. The node count is
unchanged; the differences are the backend cards reordering (
Backend_PPTXshifts oneposition, which is what the
entityNamemoves at indices 104–107 are) and the taglinegrowing from one line to two, with the sections below shifting by that height. Nothing
added, removed or retyped.
CommittedAssetDriftTestnamedengine-deck.pdfas the only preview that moved, andengine-deck-v2stayed put — confirming the change is contained.Rendered and inspected: the backends column now reads PDFBox / PPTX / DOCX with PPTX in
the live accent, and page 2 no longer promises a PDF-only pipeline.
Numbers on pages 3–4 are untouched; they come from the committed benchmark snapshot and
this change does not refresh it.