Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Tags for Projects

Open
  • Is something wrong?
#21 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
html
Domain
frontend

Research direction

Start at the landing page’s project list, the only entry point named in the issue, and inspect how similar projects are currently distinguished. Define whether tags or folders are preferred, including statuses and document language, then confirm that project state is visible without opening each project.

Written by the indexing model from the issue text.

Description

requested feature

Is there currently a way to mark your projects as done so that it’s visible from the landing page? When I’m looking at a list of projects that are all named very similar things (because they’re all letters to and from the same people), there doesn’t seem to be a great way to figure out which ones I’ve done already than to click on them and find out, which can take a while when it’s being slow. If there’s not a way already, might I suggest some sort of tagging system? Not just “done,” but “in progress,” maybe the language of the document, etc. If we want people to use T-PEN for lots of projects, there needs to be an easy way to distinguish their project beyond just repository/shelfmark, especially when they’re from the same repository and have very similar shelfmarks. I suppose having folders on the landing page for projects would accomplish the same thing, but I always prefer tags so that you can easily have the same project associated with multiple categories.

sent from SMRS email

Dominant language
HTML
Stars
5
Forks
0
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CenterForDigitalHumanities/TPEN3

All issues in CenterForDigitalHumanities/TPEN3

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.