Internal · HRF Digital Team

Producing HTML for hrf.org with an AI tool? Start here.

If you use Lovable, Bolt, ChatGPT, Claude, Codex, Cursor, or any other AI tool to generate landing pages, RFPs, or program sections for HRF — this two-minute process catches the common breakages before they reach Tony's queue. Cuts the back-and-forth, ships faster.

1Check your page before sending it

After your AI tool produces the HTML, run it through the gate. The gate catches the ~80% of issues that would otherwise bounce back: theme conflicts, dead buttons, mobile overflow, missing alt text, dead links, exposed API keys.

→ Paste & check your HTML Recommended for Lovable, Bolt, v0, ChatGPT, Gemini, Perplexity, or any tool that produces HTML in a browser Power-user setup: have your AI tool do this automatically For Claude Code, Cursor, Codex CLI — paste one system-prompt block into your tool's settings and your agent will validate every page automatically until it passes. Zero clicks per page after setup.

2Fix what the gate flags

If the gate fails, the page tells you exactly what to fix and gives you a copy-paste prompt to drop back into your AI tool. The AI regenerates with the fixes applied. Repeat until you see PASS.

3Send the passing HTML to Tony

Once the gate passes, paste the HTML into Tony's queue or directly into your Elementor block. He no longer has to rebuild — he just styles.

The ten things the gate checks

Theme inheritance. Your HTML uses plain h1–h6, p, a tags. No embedded styles redefining headings or buttons. The Elementor theme handles all styling.
Working buttons. Every <a> has a real href. No href="#" placeholders.
Safari works. Cross-browser CSS prefixes (-webkit-) where needed.
Mobile friendly. No fixed widths over 480px, tap targets at least 44×44, no hover-only interaction on touchscreens.
SEO friendly. Meaningful alt text on images, descriptive link text, proper heading hierarchy, labeled form inputs.
No leaked credentials. No API keys or Bearer tokens in client-side scripts.
Accessibility baseline. Labels, alt text, semantic HTML5.
Links resolve. External URLs actually load — dead links and stale redirects are flagged.
HRF brand assets. No hot-linking the HRF logo from external CDNs.
HRF-controlled hosting. HRF-branded content lives on hrf.org, not on GitHub Pages or personal subdomains.

HRF voice — the part that's not about code

HRF copy uses binary moral framing — freedom vs. tyranny. Active voice, declarative sentences, collective "we", no softening language. "Dictators imprison dissidents." Not "some governments have less democratic practices." If you're producing copy, tell your AI tool to use HRF's voice and reference the voice brief.

One more ask

Tony and I are trying to figure out which AI tools the team is using so we can make this even easier. Two minutes:

Quick survey — which tool do you use? 5 questions. Anonymous. Helps us write tool-specific guides for the tools people actually use.

Built by ArcticBlue for the Human Rights Foundation · Questions: ping Tony Malak.
Source: github.com/hurleywhite/hrf-qa-system