🛠️ Documentation and build instructions for ReVanced
Go to file
2024-11-26 19:21:33 +01:00
.github/workflows ci: Format & simplify names & commit message 2024-07-27 03:49:53 +02:00
assets docs: Update documentations and submodules 2024-02-25 06:12:00 +01:00
docs feat: Remove integrations and document how to setup libraries 2024-11-26 19:21:33 +01:00
repositories chore: Update revanced-manager documentation to refs/heads/main 2024-11-10 14:56:24 +00:00
.gitmodules docs: Update documentations and submodules 2024-02-25 06:12:00 +01:00
LICENSE docs: init 2022-11-12 03:11:28 +01:00
README.md docs: Fix link to resources in README 2024-09-12 17:47:52 +02:00


                       

Continuing the legacy of Vanced

🗄 ReVanced Documentation

Collection of all ReVanced documentation.

📖 Table of contents

Warning

Under docs you will find symbolic links to the documentation of the respective repositories.

Because GitHub does not render symbolic links, you need to clone this repository recursively to see the content of the linked directories or browse the submodules directly under repositories.

🚀 Get started

  1. Checkout the repository recursively:

    git clone -c core.symlinks=true https://github.com/revanced/revanced-documentation --recursive && cd revanced-documentation
    git submodule update --remote
    
  2. Open the documentation in a reader of your choice, such as Visual Studio Code, Sublime Text, or Typora

📜 Licence

ReVanced Documentation is licensed under the GPLv3 license. Please see the license file for more information. tl;dr you may copy, distribute and modify ReVanced Documentation as long as you track changes/dates in source files. Any modifications to ReVanced Documentation must also be made available under the GPL, along with build & install instructions.