Product: Mingcedar Studio DESIGNER

Export, publish, and delivery check | Mingcedar Studio

Before delivery, test the exported package in Mingcedar and verify every important behavior.

Published 2026-10-25T12:48:42.655688949Z Updated 2026-10-25T12:48:42.655688147Z

<div class="manual-doc-article manual-doc-article-section"><h2 id="delivery">Delivery: Export, publish, and delivery check</h2>

Before delivery, test the exported package in Mingcedar and verify every important behavior.

<h3 id="delivery-item-1">Use this order before a formal export</h3>

<p>Save pages and templates, clean up as needed, choose the export scope and directory, then check the exported main, popup and interaction pages.</p>

<ul>

<li>Save the presentation and templates.</li>

<li>Run Batch Replace within the intended scope.</li>

<li>Choose Export HTML or This Page according to impact.</li>

<li>Test key pages after export.</li>

</ul>

</article>

<h3 id="delivery-item-2">One PPT is one screen package</h3>

<p>Treat one presentation as one complete screen package in Mingcedar. Keep page HTML, SVG, page scripts, images, and manifests together. Do not maintain the package as unrelated loose files.</p>

<ul>

<li>Same-package navigation: hqVisuDesigner.openPage(...).</li>

<li>Cross-package navigation: hqVisuDesigner.openScreen(screenCode).</li>

<li>Keep the exported directory structure intact.</li>

<li>Use a full package for formal delivery and version archives.</li>

</ul>

</article>

<h3 id="delivery-item-3">Choose full-package or current-page export</h3>

<p>Use Export HTML for first release, formal delivery, shared files, page additions or removals, page renames, and navigation changes. Use This Page only for a clearly isolated page change whose Page Code and package structure remain unchanged.</p>

<ul>

<li>Formal delivery: full package.</li>

<li>Local page-only update: This Page.</li>

<li>Any change crossing the current page boundary: full package.</li>

<li>Decide whether this run is a preview or a release before choosing the folder.</li>

</ul>

</article>

<h3 id="delivery-item-4">What Batch Replace can change</h3>

<p>Batch Replace scans the current selection or page across Bindings & tags, Animations & behaviors, Scripts, Targets & links, Page & shape text, and Colors. It builds a read-only preview first; the document changes only after Replace. Find is exact and case-sensitive, with surrounding spaces ignored.</p>

<ul>

<li>Scope: Selected content or Current page.</li>

<li>Variables: detected template variables in the active scope.</li>

<li>Categories: choose allowed types and click Apply filter.</li>

<li>Preview: Type, Object, Replace in, Current value, Replacement preview.</li>

<li>Find next or F3: move to the next exact match.</li>

<li>Blank Replace with: remove each exact match.</li>

</ul>

</article>

<h3 id="delivery-item-5">Run Batch Replace from filter to replacement</h3>

<p>Select the intended objects, or leave the selection empty for the current page. Open Batch Replace, verify Scope, choose Categories, and click Apply filter. Enter Find and Replace with, review every replacement preview, use Find next to locate uncertain rows in PowerPoint, then click Replace.</p>

<ul>

<li>A few objects only: select them before opening the window.</li>

<li>Current page: confirm Scope says Current page.</li>

<li>Color changes: use the color buttons and enable Colors.</li>

<li>Unexpected preview rows: remove that category and apply the filter again.</li>

<li>After Replace, inspect text, tags, scripts, links, and colors on the slide.</li>

</ul>

</article>

<h3 id="delivery-item-6">Separate template variables from display text</h3>

<p>Template-variable matches identify instance parameters such as <PLC> or <RUN_TAG>. Page text, Default Text, and Language Key belong to display configuration. Review Type and Replace in before replacing so an instance parameter is not mistaken for visible copy.</p>

</article>

<h3 id="delivery-item-7">Plan export folders and versions</h3>

<p>Use separate locations for previews and formal releases, and include a clear release identifier in the parent directory name. Export History remembers paths only; it does not classify a release or preserve package versions.</p>

</article>

<h3 id="delivery-item-8">Export History is not version control</h3>

<p>Export History remembers recent paths; clearing entries does not delete directories. Keep release directories or version archives for rollback.</p>

</article>

<h3 id="delivery-item-9">Publish and acceptance check</h3>

<p>Upload the complete export result to Mingcedar, configure the menu entry, and open the package. Test page navigation, popups, tag reads, tag writes, language text, template inputs, charts, and browser-console errors before handoff.</p>

<ul>

<li>The expected entry page opens.</li>

<li>Every same-package and cross-package link reaches the correct target.</li>

<li>Writes show the expected permission, confirmation, reason, and result.</li>

<li>Images, templates, scripts, and charts load without missing resources.</li>

<li>The package can be traced to the source PPT and release folder.</li>

</ul>

</article>

</div>

<strong>Figure 1: Batch Replace</strong>

<p>Check Scope, Categories, and the preview table first. This example lists searchable items; the document changes only after Replace.</p>

</figcaption>

</figure>

<strong>Figure 2: Export HTML</strong>

<p>Choose the export folder and recent locations before exporting runtime HTML, SVG, CSS, JS, and image assets.</p>

</figcaption>

</figure>

<strong>Figure 3: Export history</strong>

<p>Export history remembers recent folders, but it is not a version manager or rollback tool.</p>

</figcaption>

</figure>

<strong>Figure 4: Export progress</strong>

<p>The window shows export status, a progress bar, and execution logs; keep the PowerPoint file and export folder available when troubleshooting.</p>

</figcaption>

</figure>

</div>