Editing the home page
The rladies.org home page is composed of a stack of sections — hero, impact, chapters, get-involved, featured members, latest posts, sponsors. Each section’s text and imagery live in frontmatter, not in i18n files or template code, so contributors can change copy and visuals without touching the theme.
Where the home content lives
Each language file is independent — title, descriptions, CTAs, and image alt text are translated by editing the file for that language. Image files are shared across languages (page resources are bundle-wide), so only _img/ needs one copy.
The frontmatter shape
A trimmed example, showing one of every kind of block:
Most fields are plain strings — change them and re-deploy. The two collections worth knowing in detail are impact.stats and involved.cards.
Stats (impact.stats)
Each stat is one card on the “Our Global Impact” row:
-
icon— any Font Awesome 6 solid icon class (fa-…). -
label— the visible label (translated per language). -
count_source— which dynamic count to display. Currently supported values:chapter_countries— number of countries with at least one chapteractive_chapters— number of currently active chaptersevents_past— total events ever held (pulled live from the meetup archive)
Adding a new
count_sourcevalue requires a small template change — ask the website team. -
color—blue,rose, or omit for the default purple.
Stats render in the order listed. To add or remove a stat, edit the YAML — no template change needed.
Cards (involved.cards)
Each card is one tile in the “Get Involved” row:
iconandcolor— same options as stats.cta.url— internal paths (e.g.chapters/) are passed throughrelLangURLso they pick up the language prefix automatically. For external links, setexternal: true; the rendered link getstarget="_blank" rel="noopener".cta.button_class— overrides the defaultbtn-outline. We usebtn-accent-rosefor the “Donate” card so it stands out in pink.image— same shape as everywhere else on the site (see Images on the website).
Cards render in the order listed. To rearrange, swap them in the YAML; to remove a card, delete its entry; to add a fourth, append a new one (the layout is a 3-column grid by default — adding a fourth card may need a CSS tweak).
What’s not in frontmatter
A handful of generic UI strings stay in the i18n files (i18n/en.yaml, i18n/es.yaml, …) because they’re reused across the site, not just on the home page:
countries,chapters,events— used as fallback labels when astatsentry doesn’t define onephoto_credit— the literal word “Photo” before a credit line
If you need to change one of those, edit the i18n file and translate to all four languages.
Adding a new language
- Copy
content/_index.en.mdtocontent/_index.<lang>.md. - Translate every string value (titles, subtitles, descriptions, CTA labels, image
alttexts,credittext if attribution differs). - Leave the
path:values,count_sourcevalues,iconclasses, andcolorvalues unchanged — those are not user-facing text. - Add the language to
config/_default/languages.yaml.
See Multi-lingual content for the broader translation workflow.