JunkFood02/Seal

[Feature Request] - Wiki 馃摐馃摉

Open

#187 opened on Sep 3, 2022

View on GitHub
聽(3 comments)聽(0 reactions)聽(0 assignees)Kotlin聽(26,238 stars)聽(1,177 forks)batch import
documentationhelp wanted

Description

Checklist

  • This feature I'm requesting is already implemented in yt-dlp.
  • This feature is merely a UI/UX update.
  • This feature is suitable for primary users with little knowledge about yt-dlp.
  • This feature is available for most websites, not only the video platform I use.
  • This feature is suitable for a large variety of videos.
  • This feature is not going to conflict with many of the existing options.

Is your feature request related to a problem? Please describe.

Seal 馃Ν is growing day after day and the user base too which is something good but with a huge number of users comes also a lot of false reports because of minor understanding of how the app works.

Describe the solution you'd like

What About a little Wiki that teaches users how to use the latest new features to prevent common issues like duplicated reports and features requests

Video link

No response

Additional context

No response

Contributor guide

Tech stack
kotlinandroid
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic understanding of Seal app features
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
Review the existing app documentation and source code to understand all features. Look at yt dlp's documentation for reference. Propose a wiki structure covering common use cases and troubleshooting. The issue has no maintainer response, so you can start by gathering information from comments and app usage.