Preserve approved mockups with controlled adjustments and recolorable assets (0.9.4)
This commit is contained in:
@@ -14,7 +14,9 @@ Keep exact supplied logos, figures and screenshots as independent source assets.
|
||||
|
||||
## Native reconstruction
|
||||
|
||||
Start from the selected template layout source, retaining its Master/Layout/placeholder metadata. Recreate normal text as native text with the external style's font family, discrete size, line spacing and alignment. Build simple panels, rules, arrows and diagram nodes as separate structural objects. Fit to the declared grid, not pixel-by-pixel ad hoc anchors.
|
||||
Start from the selected template layout source, retaining its Master/Layout/placeholder metadata. Recreate normal text as native text with the declared font family and active shared sizes, line spacing and alignment. For an approved mockup, [controlled project adjustments](visual-design.md#controlled-adjustments-for-approved-mockups) allow necessary content-area size, bounds, spacing and fit/alignment repairs with explicit integer/fixed-step values. Preserve its relative spatial relationships, visualization forms, icon identities and text styling, as well as fixed UI and locked structures. Build simple panels, rules, arrows and diagram nodes as separate structural objects. Use the declared template/project grid and shared roles, not pixel-by-pixel ad hoc anchors.
|
||||
|
||||
When native components or SVG are impractical for faithfully expressing an approved element, [use ImageGen for that element](visual-design.md#elements-that-need-imagegen) with the accepted reference, preserving its appearance, details and relationship cues. Keep it as a separate project asset and disclose the picture exception; do not swap its visualization/icon style, omit it or flatten the whole page. Exact evidence/identity originals retain their own source requirements.
|
||||
|
||||
Apply [text and container rules](text-and-containers.md) even when the reference image was built differently. Reconstruct a paragraph as one logical text block, preferably one native frame; do not turn each visible source line into an independently positioned box. Repeated container internals use one shared recipe. Essential explanations and limitations stay in the main information hierarchy, and different text functions need size/weight/color distinctions.
|
||||
|
||||
@@ -22,4 +24,4 @@ Use actual data for native charts; if source values are unavailable, preserve th
|
||||
|
||||
Preserve crop, aspect ratio and source meaning for image objects. Independently editable text over an unchanged full-page screenshot is not a reconstructed page. Keep repeated UI in inherited layers, rather than covering it with copied slide objects.
|
||||
|
||||
Build the current SVG through the project's declared builder using [native export](native-authoring.md), then compare the actual rendered page with the accepted design and element inventory at full size and a normal presentation view. Complete the [full-page hierarchy check](visual-design.md#full-page-hierarchy-check), including all font sizes, families, weights, spacing and content groups. Check density, line breaks, safe margins, alignment, clipping, asset identity and reading order. Native object checks establish object type and inheritance; they do not prove appearance. Complete the requested application checks before claiming editability acceptance.
|
||||
Build the current SVG through the project's declared builder using [native export](native-authoring.md), then compare the actual rendered page with the accepted design and element inventory at full size and a normal presentation view. Complete the [full-page hierarchy check](visual-design.md#full-page-hierarchy-check), including all font sizes, families, weights, spacing and content groups. After typography/geometry adjustments, complete both [container and page overflow checks](visual-design.md#controlled-adjustments-for-approved-mockups), including actual glyphs/formulas, strokes, clipping and occlusion; repair source, rebuild and inspect again. Check density, line breaks, safe margins, alignment, asset identity and reading order. Native object checks establish object type and inheritance; they do not prove appearance. Complete the requested application checks before claiming editability acceptance.
|
||||
|
||||
Reference in New Issue
Block a user