docs: Tracking #2441
Description
Documentation of ReVanced Manager
This is a general list of stuff to do in the documentation-side
Target
Organisation-level
- Verification of package?
- Video animation/guide/explainer?
- Testing the development version of (x)?
- Use reference-style link for very long URL
Flutter & Compose
- Package name manipulation can cause package conflicts with an existing package when done improperly
- Verification using GitHub Attestation
Compose
- Use emoji-style quote as solution for GitHub formatting limitation (ref: Flutter)
- Since architecture issues isn't an problem anymore, rewrite troubleshooting for error code 135, 139 or 1
- Patch bundles (todo: how do I test this)
Flutter
- Last patched app documentation
- Prefer getting the app from ReVanced website instead
- Refresh update (manager and patches) by pulling down on dashboard