# HelloSiteWorks Field Notes newsletter kit

Draft design assets, not a send-ready campaign. No messages were sent, subscribers imported, credentials added, or email provider activated. The protected development preview cannot host images for public email recipients.

## Files
- template.html / template.txt: reusable HTML and complete plain-text structure.
- sample-issue.html / sample-issue.txt: a complete original sample issue with mandatory sender/link placeholders.
- assets/hellositeworks-wordmark.png: exact approved blue/light-blue logo (2172 × 724). Do not redraw it.

Open sample-issue.html locally with its assets folder beside it. The sample logo uses a relative path for local review. For email sending, replace that path with the publicly reachable HTTPS asset URL described below. The website’s sandboxed sample iframe is a draft visual demonstration.

## Before any send
1. Choose and approve a dedicated sending platform, sender identity, and appropriate permission-based audience. Configure these separately; this kit neither connects nor configures them.
2. Replace {{PUBLIC_SITE_BASE_URL}} with the approved public website base URL (no trailing slash). Article and service paths assume the matching pages have actually been published there. Do not use the SSO-protected development preview as the final destination.
3. Publish the approved logo at an authorized PUBLIC HTTPS asset location. Replace {{PUBLIC_ASSET_BASE_URL}} in template.html (no trailing slash). In sample-issue.html replace assets/hellositeworks-wordmark.png with that same full HTTPS logo URL. Check the URL works for anonymous recipients; never embed an access token or a preview bypass link.
4. Fill the content placeholders. Escape supplied text and validate link destinations; no automatic template engine or unsafe raw HTML processing is included. FEATURE_PATH and SPOTLIGHT_PATH must begin with /.
5. Set {{SENDER_ADDRESS}} and {{PHYSICAL_MAILING_ADDRESS}} using the business’s approved sender and mailing details. Replace {{ESP_UNSUBSCRIBE_URL}} and {{ESP_VIEW_ONLINE_URL}} with the sending platform’s working per-recipient merge fields, not a generic or fictional link. Map both HTML and text versions.
6. Keep the visible DRAFT banner during review. Remove it only after every placeholder and all recipient-facing copy have been reviewed for an authorized final send. Search for {{ and }} and inspect the platform’s assembled output; required platform merge fields must resolve in a test send.
7. Test Gmail, Outlook, Apple Mail, and any additionally agreed target clients: desktop/mobile, images off, dark mode, link destinations, unsubscribe, reply-to, and text alternative. Browser screenshots are layout evidence only, not real inbox/client acceptance.
8. Measure the final assembled HTML after the ESP inserts its footer and tracking. Each source HTML file is under 10 KB, comfortably below Gmail’s documented 102 KB clipping threshold; that does not guarantee the final assembled send will be unclipped.

Use HTML and text as alternatives within your chosen platform. The design uses a 600px presentation-table layout, inline core styles, explicit logo dimensions and descriptive alt text, real text headings/content, an optional narrow-screen media query, and an Outlook fixed-width wrapper. No scripts, forms, external fonts, base64 images, or tracking pixels are supplied. Rounded corners are not required for rendering.

## Technical references
- [Gmail CSS support](https://developers.google.com/workspace/gmail/design/css) documents supported style and media-query features; unsupported CSS can be ignored.
- [Mailchimp: Gmail clipping](https://mailchimp.com/help/gmail-is-clipping-my-email/) explains the HTML-size threshold and why final output matters.

No production-readiness, deliverability, legal compliance, universal-client compatibility, or live fulfillment is implied by this draft kit. These are specific acceptance steps needed to use the assets, not completed integrations.
