onecrayon / onecrayon/api.ashes.live

Feature: Content creator channels

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

Nobody has claimed this yet.

Dominant language
Python
Stars
13
Forks
7
Avg merge
7h 39m
Merged PRs (30d)
1

Description

Had a request to be able to mark decks as "featured on such-and-such a stream" by content creators. Current idea:

  • Allow users to create content "channels" (could be a blog, video stream, podcast, etc.)
    • Can set users to as contributors, or revoke their own contributor status for the channel (as long as they aren't the last one)
    • Channels should have landing pages where a description of the channel lives, along with a list of the contributors, and a deck listing of decks that have been featured on that channel
    • Meta: name, description, general URL
  • Channel contributors can link any public deck to their channel with an arbitrary URL. This will show up in the deck sidebar as "featured on [channel name]" linked to the URL (so for instance a channel could link to the specific video where the deck was played)
    • Channel linkage should be tagged at a specific snapshot ID so that the system can distinguish between links to the current public version and links to past versions
  • Homepage should show a list of channels in the sidebar, ordered by activity (based on timestamps for decks that have been associated, maybe?)
  • Need moderation tools for admins:
    • Add or remove contributors to a channel
    • Modify channel title or description
    • Close/delete the channel (thus disabling all channel linkage across the site for that channel)
    • Add or remove channel links for specific decks

Contributor guide

No contributing guide indexed for this repository

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

No files, tests, or entry points are named. Start by locating the existing user, deck, snapshot, homepage, and admin API surfaces, then determine how channels, contributors, snapshot-specific links, landing pages, activity ordering, and moderation fit together. Done means the complete channel workflow and its moderation controls are implemented and tested.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.