Broken-looking link previews on News and Adoptions pages (og:description)

Open Beginner friendly
#168 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
hugo
Domain
content

Research direction

Find the source files for /resources/news/ and /community/adoptions/ and compare their front matter with docs/overview.md, which already sets a description. Add explicit descriptions for both pages and verify that their social previews no longer combine dates or section headings into garbled text.

Written by the indexing model from the issue text.

Description

Checked the social preview text (og:description) for a couple of pages and it's coming out garbled:

/resources/news/:

Highlights Here are our news highlights. For a complete list, see the Press section. May 2026 The European Union Agency for Cybersecurity (ENISA) published a draft Technical Advisory... June 16, 2021 The Sigstore community live-streamed...

A May 2026 item and a June 2021 item get run together mid-sentence.

/community/adoptions/:

Each TUF adoption listed below links to an article, presentation, or repository containing relevant code. Ongoing Others Docker registry bindings A Rust implementation

"Ongoing" and "Others" are section headers, not sentence text.

Both pages are missing a description: field in front matter, so Hugo falls back to auto-summarizing the body - which doesn't work well here since the content is short fragments/dates rather than prose. Other pages like docs/overview.md already set one explicitly. Can send a PR adding it to both files if useful.

Dominant language
HTML
Stars
25
Forks
46
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from theupdateframework/theupdateframework.io

All issues in theupdateframework/theupdateframework.io

Similar issues

More Content issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.