feat(templates): pixel-port invoice/v2 ModernInvoice to the cinematic look#264
Merged
Conversation
… look Retune BrandTheme.invoiceModern() to mirror BusinessTheme.modern() and align ModernInvoice so it renders the exact builtins/InvoiceTemplateV2 appearance on the layered stack — verified pixel-identical (0% raster diff) against the cinematic builtin. - core.theme: Palette.invoiceModern() / Typography.invoiceModern() values now match modern() (cream page, soft-tan panels, deep-teal title + table header, gold accent, Helvetica 28 / 11 / 10). - ModernInvoice: title + table header use a preset-local teal; hero accent + status use gold; labels + footer read the theme. Line-item cells inherit the DSL default table text to stay a pixel match for the builtin (documented inline). - example: render on the cream page background. - InvoiceV2VisualParityTest + blessed baseline lock the look against drift. - data.invoice package-info: note it now backs both the builtin and invoice/v2.
This was referenced Jun 29, 2026
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
#257 stood up
invoice/v2as a skeleton. This PR finishes the cinematic step:ModernInvoicenow renders the exactbuiltins/InvoiceTemplateV2appearance on the layeredcore+BrandThemestack, so the layered family can replace the builtin without a visual change.What
Palette.invoiceModern()/Typography.invoiceModern()values retuned to mirrorBusinessTheme.modern()— cream page (252,248,240), soft-tan panels (244,238,228), deep-teal title + table header (20,60,75), gold accent (196,153,76), Helvetica 28 / 11 / 10.CvV2VisualParityTest).invoice/v2).Verified pixel-identical: rasterised
ModernInvoice(onBrandTheme.invoiceModern()) vs the cinematicInvoiceTemplateV2(onBusinessTheme.modern()) → 0% differing pixels (every tolerance, empty diff bbox).Note: the line-item body cells render at the engine default (Helvetica 14 black), faithfully reproducing the builtin. Making them theme-driven would be a deliberate divergence from the cinematic — out of scope here.
Follow-up (PR 2.3): migrate the 5 invoice examples off
builtins.InvoiceTemplateV2(coordinated with proposal).Tests
./mvnw verify javadoc:javadoc -pl .→ BUILD SUCCESS, 1618 tests, 0 failures; javadoc clean. New visual parity test green against the committed baseline.