RSSNext / RSSNext/Folo

Flexible Content Categorization System

Open
#598 4 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
39k
Forks
2.1k
Avg merge
1d 4h
Merged PRs (30d)
10

Description

Clear and concise description of the problem

As a user of this project, I want a flexible content categorization system and not be forced to include Articles, Social Media, Pictures, Videos, Audio, and Notifications, so that I can efficiently organize and filter my content based on my preferences.

Suggested solution

In the app's content organization system, we could:

  1. Implement current content types system as a preset: Articles, Social Media, Pictures, Videos, Audio, and Notifications
  2. Allow users to add, remove, or customize these content types
  3. Use a clear term for these groupings (e.g., "content types", "feed types", or "labels")
  4. Develop a filtering system that enables users to show/hide specific content types
Alternative

An alternative could be a tag-based system where users can create and assign multiple tags to each feed, allowing for more granular and flexible organization.

Additional context

Some users might only want to use Follow for Feeds and Social Media, finding the other types distracting or unhelpful. The current system doesn't allow for this level of customization. Examples of similar systems in other contexts could include email folders/labels, social media content filters, or news app categories.

Validations
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Contributor guide

Open the contributing guide

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.

Research direction

The issue does not name any files, tests, or entry points, so start by locating the current content-type organization and filtering implementation. Clarify whether customizable content types or a tag-based system is intended, then define completion around user-managed categories and filtering that can show or hide them.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.