html-email

Featured

Send-ready single-file email

AI & Automation 64,796 stars 10637 forks Updated yesterday CC0-1.0

Install

View on GitHub

Quality Score: 92/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# HTML email Design an HTML email as ONE self-contained .html file that survives real email clients. Email rendering is not browser rendering — Gmail, Outlook, and Apple Mail each strip or mangle different things, and the rules below are what reliably survives all three. When a rule here conflicts with normal web-design instincts, the rule wins. Layout and styling: - Structure with nested `<table role="presentation" cellpadding="0" cellspacing="0" border="0">` — no flexbox, no grid, no floats, no position. One centered wrapper table, max-width 600px, single-column flow (stacked rows beat side-by-side columns). - Inline EVERY style on the element it styles. A `<style>` block in `<head>` may additionally carry only what can't inline (media queries, dark-mode tweaks) — several clients drop it entirely, so the email must read correctly from inline styles alone. - No JavaScript anywhere (universally stripped). No external stylesheets. No web fonts — use email-safe stacks (Arial, Helvetica, Georgia, Verdana, Tahoma, 'Courier New') with generic fallbacks. - Build the visual design out of colored table cells, borders, spacer cells, and type — not images. There is nowhere to host project images from here: a referenced project file will not exist for recipients. If imagery is essential, leave a clearly-marked placeholder cell with alt text and tell the user to swap in a hosted https URL before sending. - Buttons are "bulletproof": a padded `<td>` with bgcolo...

Details

Author
asgeirtj
Repository
asgeirtj/system_prompts_leaks
Created
1 years ago
Last Updated
yesterday
Language
JavaScript
License
CC0-1.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category