posit-dev / posit-dev/open-source-website

Confirm and normalize J.J. / JJ Allaire spelling

Open
#167 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
55
Forks
24
Avg merge
1d 21h
Merged PRs (30d)
17

Description

The site uses two forms: JJ Allaire (people page title, most content) and J.J. Allaire (a handful of posts). These produce different Hugo slugs (jj-allaire vs j.j.-allaire), so J.J. Allaire entries don't link to the /people/jj-allaire/ page.

#166 normalized blog posts to JJ Allaire to match the current people page title, but the preferred form may actually be J.J. Allaire.

To do

  1. Confirm which spelling is preferred
  2. Update content/people/jj-allaire/_index.md title
  3. Rename the directory to match the new slug (Hugo matches people values by slugifying them and comparing to the directory name)
  4. Re-run sync-videos.py and update-software-frontmatter.py — they read the people page title, so they'll propagate the change automatically
  5. Update blog posts (10 files)

Current state

Area JJ Allaire J.J. Allaire
Blog 10 0
Videos 120 2
Software 54 0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

First confirm the preferred spelling, then inspect content/people/jj-allaire/_index.md and the 10 affected blog posts. Read sync-videos.py and update-software-frontmatter.py before rerunning them, then verify the people directory slug and propagated references. Done means one consistent spelling, matching title and directory, and no stale links or front matter.

Written by the indexing model from the issue text.

Assessment

Tech stack
hugo, python
Domain
content
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.