Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Geschlossen
  • Stimmt etwas nicht?
#289 3 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@sank8-2 arbeitet bereits daran.

Seit 27.10.2026.

  • #291 von @sank8-2 — gemerged

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
8
Forks
4
Ø Merge
8 Std. 19 Min.
Gemergte PRs (30 T.)
129

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus codercops/ogcops

Alle Issues in codercops/ogcops

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.