证书版式与批量制作方案设计
围绕颁发事项设计证书文案、两套版式与字体配色,并给出批量字段、核验和印刷规范。
完整提示词
<context>
A certificate is a keepsake and a record. The recipient's name is the hero; the achievement and the issuer come next; date, signatures and an identifier close it. Common failures: the organisation's logo dominates the person's name; decorative script faces that cannot render long names, accents or non-Latin scripts; layouts that break when a merge field holds "Maria Fernanda Rodríguez-Castellanos"; wording that overstates what was achieved ("certified" for a one-hour webinar); and ornate seals that make a simple course certificate look like an official qualification. Certificates issued in bulk are produced by merging a spreadsheet into a template, so the design must survive the longest and shortest values.
</context>
<task>
Design a certificate for: {{certificate}}
{{#delivery}}Delivery: {{delivery}}{{/delivery}}
If it is unclear what is being recognised or who issues it, ask and stop.
1. **Wording.** The exact text for every element: title ("Certificate of Completion", "Award for ..."), presentation line, recipient name field, achievement line stating precisely what was done (course name, hours or dates, level), issuer, date, signatory names and roles, and certificate ID. Use honest verbs: "completed", "attended", "awarded"; use "certified" only if the issuer runs a real certification.
2. **Hierarchy.** Order of emphasis from first glance to last, with relative sizes.
3. **Layout options.** Two layouts (for example a classic centred formal layout and a modern asymmetric one), each with orientation, margins, placement of logo, name, text, signatures and any border or graphic.
4. **Typography and colour.** Typefaces for name, title and text with weights, checking that the name typeface covers the accents and scripts recipients will have; colour use that prints well and stays legible; restraint with borders and seals.
5. **Variable data.** The merge fields, the longest and shortest test values, how the name field shrinks or wraps, date format for the audience, and a checklist for proofing a merged batch.
6. **Authenticity and verification.** A unique ID per certificate, how someone could verify it (a register or verification page the issuer actually runs, or a contact), signature handling (signature images kept private and placed only by the issuer), and what not to do to avoid looking like a government or university document.
7. **Print and PDF specs.** Size (A4 or US Letter landscape unless asked), card weight and finish, bleed if there is edge colour, and for PDFs: embedded fonts, a tagged accessible PDF, file naming per recipient.
</task>
<constraints>
- Do not help imitate a certificate, diploma, licence or qualification from an organisation that is not the issuer, and do not add seals, crests or wording that suggest an accreditation the issuer does not hold. If asked to, decline briefly and offer an honest design instead.
- Do not invent accreditation bodies, credit hours or signatories; use placeholders.
{{> output/uncertainty}}
</constraints>
<output_format>
Markdown with the contract's sections in order. Wording as a table (Element, Text). Variable data as a table (Field, Example, Longest test value, Rule). Proofing as a checklist.
</output_format>可替换内容
- {{certificate}}
- {{#delivery}}
- {{delivery}}
- {{/delivery}}
- {{> output/uncertainty}}
分类与标签
设计创意、证书设计、排版设计、批量套印、印刷规范