Rladies blog post
Write, structure, and ship a blog post on the RLadies+ website (rladies.org, the rladies/rladies.github.io Hugo site). Use this when someone wants to draft, propose, format, or submit an RLadies+ blog post or news item — scaffolding the page bundle, filling the YAML frontmatter (author/editor directory_id, contributions, date, image alt), authoring in Markdown / R Markdown / Quarto, using the site's shortcodes and render hooks (callout, button, rlogo, figures, mermaid), passing the blog-lint / Lighthouse / i18n CI checks, and getting it scheduled via the pending label and merge-pending workflow. Builds on rladies-voice for voice and the drafting pass, and rladies-brand for naming/inclusive-language/visual identity. For translating an existing post use rladies-translate-page. Source: guide.rladies.org website/blog and admin_guide.From its SKILL.md
npx -y skills add rladies/grimoire --skill rladies-blog-postAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
6.5 KB, as published. Nobody here has run it
Writing an RLadies+ Blog Post
The blog lives in the Hugo site rladies/rladies.github.io. Write in the
RLadies+ voice (warm, spotlight people, 💜) and run
it through that skill's tell list so the draft doesn't read AI-generated; the
inclusive-language rule ("gender minorities in R") is in rladies-brand. The
mechanics below are RLadies+-specific; for generic Hugo and Markdown patterns
lean on the hugo-site and markdown skills.
Propose first, then draft
Strongly prefer pitching an idea before writing a full post — open the
blog-post proposal form. An editor plans the
calendar (so posts don't compete) and shapes scope before you spend hours, and can pair
you up or convert a Google Doc if Git isn't your thing. Proposals and tasks live in an
Airtable base wired to #team-blog (see
references/editorial-and-ci.md).
Scaffold the page bundle
Posts are page bundles under the year, with a MM-DD-slug folder for chronological
sorting:
content/blog/<year>/<MM-DD-slug>/
└── index.en.md # add index.es.md / index.pt.md / index.fr.md for translations
Scaffold with the archetype:
hugo new --kind blog blog/2026/06-iwd-recap/index.en.md
The feature image and any other assets live in the same folder next to index.en.md.
Frontmatter
Minimum required (blog-lint hard-fails without title, author, date, and on a
date not in YYYY-MM-DD, and on body images without alt text):
---
title: "Spelling and casing of the post title"
description: |
One-line subtitle, used in OG meta and listings. Markdown supported.
author:
- name: Your Name
directory_id: "your-directory-slug" # optional but encouraged
editorial:
- name: Editor Name
directory_id: "editor-directory-slug"
date: "2026-06-12"
categories: [community]
tags: [iwd, recap, oslo]
image:
path: "feature-image.png"
alt: "Description of the feature image, for screen readers"
summary: |
Optional override for the listing summary.
---
title— sentence case, no trailing period.directory_id— when an author/editor/translator has a directory profile, add their slug; the byline becomes a link and the post shows under "Posts by this author". No profile? Omit it (renders as plain text) or add it later via the directory form.contributions— to credit who did what, declare a post-level map and per-person lists (both are required or the superscripts silently disappear). See the full worked example and field catalog in references/editorial-and-ci.md.
Authoring engine
- Plain Markdown — the minimum; needs only Hugo Extended (≥ 0.144).
- R Markdown (blogdown or hugodown) or Quarto (
format: hugo-md) — render to.mdlocally and commit both the source and the rendered.md; Hugo only sees the.md, the source is kept for reproducibility.ignoreFilesexcludes*.Rmd/*.qmdfrom the build. The site does not userenvfor blog posts. - Figures from code — set both
fig-alt(what the figure shows, for screen readers) andfig-cap(why it matters, the visible caption). They do different jobs; if you only setfig-capit's reused as alt text, but write both.
Shortcodes & render hooks
These are automatic — don't hand-write the HTML:
- Images become figures —
renders as a<figure>with<figcaption>andloading="lazy". Title = visible caption; omit the title for alt-only. Always provide alt text. - External links — any
http(s)link auto-getstarget="_blank" rel="noopener noreferrer". - Mermaid — fenced
```mermaidblocks render as diagrams (loaded only on pages that use them).
Shortcodes — callout (types tip/info/note/warning/danger, override
title=/icon=), button for one big call-to-action (not in-prose links), and
rlogo (image-fillable via image=):
{{< callout type="warning" >}}
The directory data is private. **Do not** copy entries into a public PR.
{{< /callout >}}
Full syntax catalog in references/editorial-and-ci.md.
Submit and schedule
- Work on a feature branch; website-team members push directly to
rladies/rladies.github.io, others fork and PR. Both get a Netlify preview comment. - Commit the post (and rendered
.md+ source if applicable) and open the PR. - CI runs: production build, blog-lint (required fields / date format / body-image alt text — hard fails), Lighthouse (fails the PR if an audited image lacks alt text), i18n coverage (informational), and an editorial checklist comment.
- A website-team reviewer is auto-assigned; apply suggestions and push again.
- To schedule: set the frontmatter
dateto the publication date and add thependinglabel. Themerge-pending.yamlworkflow runs weekdays at 10:58 UTC and squash-merges anypendingPR whosedateis today. Without thependinglabel nothing auto-merges — each post is opted in explicitly.
The CI checks, Airtable editorial workflow, automations, and the full frontmatter / shortcode catalog are in references/editorial-and-ci.md.
Related skills
- Voice and the drafting pass →
rladies-voice. Inclusive language, brand →rladies-brand. - Translating a post into ES/PT/FR →
rladies-translate-page. - Announcing the post on social →
rladies-social-posts. - Generic Hugo / Markdown mechanics →
hugo-site,markdown.