MRGI LAYOUT / WORKFLOW FIELD GUIDE
Publish a regional field-note collection
Produce consistent editions while catching missing content before distribution.
01 / FROM INPUT TO HANDOFF
Follow the decisions.
This walkthrough describes the intended MRGI product behavior. The browser demo illustrates a small part of the workflow; it does not run the complete application.
- 01
Bind the edition set
- Start with
- A reusable template and fictional regional records.
- Work through
- Select the approved data version and required fields.
- Result
- A defined publication run.
- 02
Generate candidates
- Start with
- The template and selected records.
- Work through
- Merge content into the intended layouts.
- Result
- A set of draft editions.
- 03
Resolve exceptions
- Start with
- Missing-field and layout findings.
- Work through
- Correct the input or document an accepted exception; rerun affected records.
- Result
- A reviewed output set.
- 04
Distribute the run
- Start with
- The approved set and input references.
- Work through
- Record which editions were released and from which versions.
- Result
- A traceable publication collection.
02 / INPUTS & INTERCHANGE
What travels with the work.
These are foundation formats and intended handoff contracts. Support and fidelity must be confirmed for each released build.
| Artifact | Role | Review consideration |
|---|---|---|
| IDML | Layout interchange foundation | Text composition, placed assets, and styles need validation. |
| Approved tabular data | Bulk content input | Required fields and selection rules should be explicit. |
| Publication output | Fonts, bleed, output intent, and accessibility need separate checks. |
A deliberate cross-app boundary
Combine Grid datasets, Line brand releases, and Pixel imagery in the same reviewed publishing recipe.
The intended handoff should identify the selected resource, its version, the destination, and the user’s authorization. A linked application should not inherit unrestricted file access.
Explore the connected applications ↗03 / BOUNDARIES & READINESS
Know what this example establishes.
- The browser lab checks required text fields only.
- Page composition and print preflight are not implemented by this site.
- A valid data record can still produce a poor or overflowing layout.
Development status
The source foundation is imported. Governed batch publishing and the redesigned review experience are planned.
Before a production release
Validate real-file behavior and platform support, implement the stated authorization and review rules, and document the tested acceptance scope. The interactive website is a product demonstration, not a release candidate for the application.
04 / PRODUCT QUESTIONS
The details that matter.
Does data merge itself make Layout unique?
No. The proposed focus is an approved-input workflow, per-record exception review, and traceable releases around data merge.
Can one correction trigger a partial rerun?
That is a planned behavior. Shared template or asset changes may require a broader rerun to avoid mixed editions.
Open-source foundation
Page layout, text frames, data merge, preflight, and PDF/IDML workflows exist in DesignCraft. Approved-input publishing governance is the proposed addition. Read the credits and foundation mapping.
Keep exploring Layout.
Return to the product breakdown or try the local interactive example.