Build a student-informed content and SEO roadmap

Aberta
  • Algo errado?
#25 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Documentação
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
next.js, typescript
Domínio
content, documentation, search

Direção de pesquisa

Start with related issue #22, then read the README and content guide to understand the existing catalogues, sample note files, and SEO setup. Map student audiences and their needs to the first courses, branches, and placement topics, then define review and publishing criteria for each resource type. Done means a phased, student-informed roadmap that covers the listed acceptance criteria and updates the README or content guide where the publishing process changes.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Context

The course catalogue currently has no published subjects, and the guides and jobs catalogues are empty. Sample note files exist but are intentionally not published. The site already has technical SEO foundations, so useful reviewed content and accurate discovery signals need to grow together.

Proposal

Create a phased, student-informed plan for publishing original engineering study resources and placement guidance, then make genuinely useful pages easy to discover. Prioritize accuracy and curriculum fit over page count or arbitrary word-count targets.

Acceptance criteria

  • Identify the first student audiences, courses/branches, and placement topics to serve, using student needs to prioritize them.
  • Define review criteria and source/copyright expectations for notes, guides, and job/internship listings.
  • Publish only complete, useful resources; keep empty or placeholder routes out of the index and sitemap.
  • Ensure published pages have accurate titles, descriptions, canonical URLs, structured data where appropriate, and useful internal links.
  • Check the live sitemap, robots rules, broken links, mobile usability, and search performance as content is added.
  • Avoid thin, repetitive, keyword-stuffed pages and unsupported promises about rankings or placement outcomes.
  • Update the README/content guide when the publishing process or available catalogues change.

Related planning issue: #22.

Linguagem predominante
TypeScript
Estrelas
1
Forks
1
Merge médio
8h 58min
PRs com merge (30d)
37

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 procoderji-com/procoderji

Todas as issues de procoderji-com/procoderji

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.