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

Feature: first-class categories and tags

Open
#62 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, html

Research direction

Start by reading LearnStack.Core/Data/Models/LearningResource.cs:36 and LearnStack.Core/Services/LearningResourceService.cs:141-152, then trace ResourceForm and the existing migration setup. Check how current tag strings are stored, searched, and rendered before assessing the entity, join-table, migration, autocomplete, filter, and settings scope. Done means existing tags migrate without loss and the new search, editing, filtering, rename, and merge flows are verified.

Written by the indexing model from the issue text.

Description

enhancement

Tier 4 — feature idea

Why

Tags are a single comma-separated string on the resource today. There is no tag entity, so there is no autocomplete, no rename, no merge, no "all resources with this tag", and filtering is a LIKE '%tag%' scan that also matches substrings of unrelated tags.

Related: #2 (Categories for the resources).

Evidence
  • LearnStack.Core/Data/Models/LearningResource.cs:36 — string? Tags
  • LearnStack.Core/Services/LearningResourceService.cs:141-152 — Tags.ToLower().Contains(term)
Sketch

Tag entity + ResourceTag join table, migration splitting existing strings, autocomplete in ResourceForm, tag chips as filters, tag rename/merge in settings.

Notes

Worth doing before the library grows — the data migration gets harder with volume.

Dominant language
HTML
Stars
10
Forks
0
Avg merge
3h 42m
Merged PRs (30d)
14

Getting set up

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 kasuken/LearnStack

All issues in kasuken/LearnStack

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.