WindowsMeosu/peppypedia

peppypedia: todo checklist

Open

#70 opened on Oct 2, 2023

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Ruby (2 forks)auto 404
enhancementgood first issuehelp wantedrepo

Repository metrics

Stars
 (2 stars)
PR merge metrics
 (PR metrics pending)

Description

resolves https://github.com/WindowsMeosu/peppypedia-old/issues/38, https://github.com/WindowsMeosu/peppypedia-old/issues/39

  • cleanup: delete unused or otherwise useless files, and also remove unnecessary stuff in markdown files
  • transition to more a markdown-based style (tables, etc. are handled with html at the moment for most pages | will eventually)
  • incorporate an api-like system (which would be limited)
  • workflow for checkouts (in the works)
  • display authors and contributors before page headers
  • medal series
  • add potential articles that were planned but scrapped
  • finish bancho series (will finish later on)

Contributor guide

Research direction
Inspect the repository structure to understand how pages are currently rendered, focusing on the use of HTML tables versus Markdown. Choose an open checklist item, such as converting HTML tables to Markdown or adding planned articles, and work on that item. Look at existing completed tasks for examples of expected changes. If you pick the Markdown transition, find pages with HTML tables and convert them. If you pick adding articles, check the issue references for context on what articles were planned.
Tech stack
rubyhtml
Domain
documentation
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65