3.5 KiB
Reconstruct one visual page into editable objects
Treat the current visual page as a design reference with explicit source fidelity requirements. Determine the background and asset boundaries before writing native text over it; otherwise old text and newly editable text can coexist invisibly in a background picture.
Inventory the page: canvas, fixed UI, text levels, content groups, foreground images/icons, simple geometry/connectors, tables/charts, formulas, decorative patterns and intended layout slots. Keep every text value, evidence value and source asset tied to the user-provided content. Record each object's target type and source.
Background and materials
Solid backgrounds, ordinary panels, divider bands, repeated geometric patterns, axes and simple connectors can be authored as native geometry. Reuse a clean image region when it contains none of the foreground that will be rebuilt. For a complex illustration/photo background obscured by replaceable text or objects, use the host image editor to remove only those objects while preserving scene identity, camera, composition, lighting and texture. Inspect the repaired result for invented content and smearing.
Keep exact supplied logos, figures and screenshots as independent source assets. Use existing vector or layered assets when available. When visual identity depends on an inseparable bitmap illustration, isolate it through image editing or retain a disclosed image exception, according to the user's editability requirements. Do not replace it with an unrelated icon, approximate illustration or whole-page crop without authorization.
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.
Apply text and container rules 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.
Use actual data for native charts; if source values are unavailable, preserve the chart as an evidence image and say why. A native table uses native cells; native formulas require actual editable equation objects where the chosen compiler supports them. A formula bitmap, SVG picture or vector outline is still a picture/path exception. Preserve formula meaning and verify symbols against the source before conversion.
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.
Compile the current SVG through native export, then compare the actual rendered page with the accepted design at full size and a normal presentation view. Check hierarchy, 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.