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

Feature: Creator Availability Status System

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

@Swaim-Sahay is already working on this.

Since Dec 2, 2025.

  • #210 by @Swaim-Sahay — open

Assessment

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

Research direction

No files, tests, or code entry points are identified. Start by locating the creator dashboard, creator profile, and search entry points, then trace how creator settings and search results are stored and rendered. Done means the three statuses, custom message, automatic saving, profile badge, availability filter, and hidden Not looking creators all work together.

Written by the indexing model from the issue text.

Description

Description

Right now there's no way for creators to show if they're available for work. Brands end up messaging people who aren't looking, and creators get spammed with offers when they're busy.

What we need

A simple toggle with 3 options:

  • Available (show me to brands)
  • Busy (I'm visible but booked)
  • Not looking (hide me from search)

Plus a text box for custom messages like "Available from Feb" or "Only open to tech brands"

Why this matters

Saves everyone time. Brands find the right people faster, creators get fewer irrelevant DMs.

What needs to work

  • Toggle shows up on creator dashboard
  • Changes save automatically
  • Brands see a badge on each creator's profile
  • Search has a filter for availability
  • "Not looking" creators don't show up in search

Thank you

Dominant language
TypeScript
Stars
101
Forks
145
PR merge metrics
No merged PRs in 30d

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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.

More from AOSSIE-Org/InPactAI

All issues in AOSSIE-Org/InPactAI

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.