Asset handover: new wiki pair for discussion #56
New pages (app commits 605811aa + 2aed483e):
- Asset-Handover (user)
- Asset-Handover-Developer-Guide
The dev guide records three decisions worth keeping:
1. The designer is BLOCKS, not a canvas, because the middle of the document
is a repeating region -- one row per asset, count unknown until render.
A WYSIWYG either cannot express that or makes the admin write a loop.
2. Escape FIRST, substitute SECOND. Merge values are user-supplied
(users.display_name arrives from the portal, from mail, from imports) and
this document is EMAILED, so getting the order backwards would put stored
markup into a mail client. Includes the test that proves it.
3. One renderer serves the printed page, the preview and the email. A preview
that is a separate approximation is a preview nobody can trust, and the
divergence surfaces on a document somebody has already signed.
Also records the users_assets stale-row trap (no foreign key; an INNER JOIN is
deliberate), why printing beats generating a PDF, and four honest gaps: no logo
in the emailed copy, one default template for the whole install, no record that
a handover happened, and 23 untranslated locales.
Every named file verified to exist; every link verified to resolve; the
factual claims (logo_path null, the 2000-char cap, the INNER JOIN) checked
against the source rather than recalled.