For Tony Malak · HRF Digital Team

Test these prototypes in Elementor

Two body-only HTML fragments, designed to paste straight into Elementor HTML widgets. Both pass the QA gate in embed mode (no h1, theme-compatible classes, real URLs, no exposed secrets). Test plan and known TODOs at the bottom of this page.

The two test files

alex-rfp-v4.body.html Gate · Pass

Theme-conformant rebuild of the AI for Individual Rights RFP page. Body-only — paste into an Elementor HTML widget at hrf.org/program/ai-for-individual-rights/. Includes hero, mission, 3 grant tiers, 8 focus areas, North Star checklist, 6 featured grantees, eligibility, 4-step application process, final CTA, newsletter signup.

r2-bdf-v4.body.html Gate · Pass

Theme-conformant rebuild of the Bitcoin Development Fund page. Body-only — paste into an Elementor HTML widget at hrf.org/program/financial-freedom/bitcoin-development-fund/. Includes program overview, key stats, full searchable / filterable grantee table with inline JS (no external dependencies), and program areas.

Test plan — what to check in Elementor

The fragments above pass the QA gate, but only in-Elementor testing confirms they wrap cleanly in HRF's actual theme. Quick checklist:

  1. Paste each fragment into a new Elementor HTML widget on a staging page. Save and preview.
  2. Confirm typography inherits the theme. Headings should be Gilroy (or your current site font), not a fallback. Body text should look like other hrf.org content.
  3. Confirm buttons inherit the theme. The "Apply for a Grant", "Start an application", and "Subscribe" buttons use Elementor classes (elementor-button elementor-button-link elementor-size-sm). They should render in your usual button style.
  4. Test on mobile. Open the page on a phone (or DevTools mobile emulator). Confirm no horizontal scrolling, readable text, tappable CTAs.
  5. BDF only: test the grantee table. Type in the search box, change the region/category filters. Verify rows hide/show. Test on mobile too — the table should be scrollable horizontally.
  6. Check the Apply for a Grant button. Both pages link to hrf.org/program/ai-for-individual-rights/ai-grants/ and the BDF Monday.com form respectively. Confirm those URLs are still the canonical destinations.
  7. Verify the canonical URL meta tag matches the WordPress permalink. If WordPress wants a different canonical, override in Yoast / Elementor's SEO settings.
  8. Report back any styling or layout issues — those tell us what HRF-specific theme classes the gate's rules should be tightened around.

Known TODOs in the files

alex-rfp-v4.body.html — newsletter form action

The newsletter <form> action is set to REPLACE_WITH_HRF_NEWSLETTER_ENDPOINT. This is intentionally invalid so it can't silently send subscriber emails to a third party.

Replace with HRF's real endpoint: a Zapier webhook, n8n flow, Mailchimp form action, or HRF-approved server endpoint. The gate forbids direct Airtable POSTs from the page.

Both files — HRF logo

Currently both pages use a typographic brand mark ("Human Rights Foundation" as text) rather than the HRF logo image. The original Alex Gladstein prototype hot-linked the logo from an HRF CDN, which the gate flags as a brand-governance risk (HRF can't refresh or revoke cached copies it doesn't own).

To add the logo: serve it from hrf.org/wp-content/uploads/... or another HRF-controlled URL, and add an <img> with a meaningful alt attribute at the top of each page's <header>.

Both files — final review

The HRF voice should be re-checked against the latest voice brief. The content was synthesized from the live alex-hrf-ai-rfp.finite.vip page and r2-vibes.github.io/hrf-bdf — language is close to the originals but should be reviewed for any HRF-specific phrasing updates.

If something breaks

The fastest way to flag an issue is to:

  1. Capture a screenshot of the broken state in Elementor.
  2. Note which page (alex-rfp or bdf) and which section.
  3. Send to Hurley with the screenshot.

If the breakage is an HRF-theme-specific styling conflict, it tells us a new rule to add to the QA gate so future submissions catch it automatically.

System reference for the rollout

The full QA system Tony can hand to staff: