Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add the Updated Post blog template (`blog-updated-post`)

Chiusa
#289 3 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@sank8-2 ci sta già lavorando.

Dal 27/10/2026.

  • #291 di @sank8-2 — integrata

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

good first issue hacktoberfest templates

Part of #5. For posts that were refreshed and want to say what changed.

Idea
A small "Updated" label in the accent color at the top, the post title large under it ("A practical guide to React Server Components"), and a dates line under that ("First published Mar 3, 2024" and "Updated Oct 27, 2026"). Then up to three short lines under a "What changed" heading ("Covers React 19", "New section on server actions", "Fixed the broken examples"), and the site name at the bottom.

Template details

  • File: src/templates/blog/updated-post.ts, id blog-updated-post
  • Fields: commonFields.title, published (text, optional, default "First published Mar 3, 2024"), updated (text, optional, default "Updated Oct 27, 2026"), change1 to change3 (text, optional, defaults "Covers React 19", "New section on server actions" and "Fixed the broken examples"), commonFields.siteName, commonFields.bgColor, commonFields.accentColor, commonFields.textColor

Where to look

  • Closest reference: src/templates/blog/table-of-contents.ts (a short list where blank rows are skipped), src/templates/event/rescheduled.ts (an old date and a new one on the same card)

Acceptance criteria

  • A long title shrinks with autoFontSize() and then truncates, blank change lines are skipped with no gaps, and the "What changed" heading hides when all three are blank
  • An empty published, updated or site name (or only spaces) hides cleanly, and the label and any accent text stay readable on a light background
  • Re-exported in src/templates/blog/index.ts and registered in the Blog block of src/templates/registry.ts
  • Meets the shared template checklist in #5

One template per contributor at a time, so more people get a chance.


Want to work on this? Comment below and I'll assign it to you. Please take one issue at a time, branch off dev, and open your PR against dev with Closes #289 in the description.

Lingua principale
TypeScript
Stelle
8
Fork
4
Merge medio
8h 19m
PR unite (30g)
129

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di codercops/ogcops

Tutte le issue di codercops/ogcops

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.