Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Fechada
  • Algo errado?
#289 3 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@sank8-2 já está trabalhando nisso.

Desde 27/10/2026.

  • #291 de @sank8-2 — integrado

Avaliação

Esta issue ainda não foi avaliada.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
8
Forks
4
Merge médio
8h 19min
PRs com merge (30d)
129

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de codercops/ogcops

Todas as issues de codercops/ogcops

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.