Default repositories
-- Dedicated unofficial website to browse repositories:{' '} - - hacs-repositories.web.app - -
-- There are currently{' '} - {data.integration.length + - data.plugin.length + - data.appdaemon.length + - data.netdaemon.length + - data.python_script.length + - data.theme.length}{' '} - default repositories in HACS in {Object.keys(data).length} categories. -
- {categories.map((category) => ( - -- - {category.name} - - # - -
- {data[category.slug].length} Repositories in total. --
- {data[category.slug].map((repo) => (
-
- - - {repo} - - - ))} -
-
-
-### Danish HACS Installation Guide
-
-_by [Daniel Bahl](https://danielbahl.com)_
-
-You can find the complete danish walkthrough guide at Robotnet.dk
-
-
-
-
-
-
-
-
-
-### Install and Setup Walkthrough
-
-_by [DrZzs](https://www.youtube.com/channel/UC7G4tLa4Kt6A9e3hJ-HO8ng)_
-
-
-
-
-
-### Home Assistant Themes and Plugins with HACS!
-
-_by [KPeyanski](https://www.youtube.com/channel/UCiyU6otsAn6v2NbbtM85npg)_
-
-
-
-
-
-### German HACS Installation incl. first integration
-
-_by [Tristan](https://www.youtube.com/channel/UCe06G4hqXjUlYhB-rDmns4g)_
-
-
-
-
diff --git a/documentation/configuration/basic.md b/documentation/configuration/basic.md
deleted file mode 100644
index 8b5600b2..00000000
--- a/documentation/configuration/basic.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-id: basic
-title: Initial Configuration
-description: "Basic configuration"
----
-
-:::info
-_This page assume that you have already completed the [installation](/docs/installation/prerequisites)_
-:::
-
-## In your Home Assistant UI go to "Configuration", then click "Integrations"
-
-
-
-## Clear your browser cache
-
-Before HACS can show up in the list you need to clear your browser cache.
-
-:::warning
-You actually need to do this, don't skip it.
-:::
-
-## Click the "+" button in the bottom right corner
-
-
-
-## Search for or scroll down to find "HACS" and select it
-
-
-
-:::info
-You see this when Home Assistant is installing the requirements needed for the integration.
-
-
-If this takes longer than 10 minutes, you may have an issue with your Home Assistant installation.
-:::
-
-## Accept usage
-
-
-
-None of the items are optional, you need to accept everything before you can setup HACS.
-
-## Device registration
-
-HACS uses a device OAuth flow for authentication against the GitHub API.
-
-_If you do not want that, you can use a Personal Access Token if you [configure HACS with YAML](/docs/configuration/legacy)._
-
-***
-
-
-
-On the first screen you are presented with a device code, copy that to your clipboard and click on the [https://github.com/login/device](https://github.com/login/device) link to continue the setup.
-
-**Do not click on submit yet!**
-
-***
-
-
-
-If you are not signed in to GitHub in your browser you need to signup or signin now to continue the setup, if you are already signed in, you can skip this part.
-
-***
-
-
-
-When that page is loaded up, paste or type in your device code that was presented to you in the previous step.
-
-***
-
-
-
-Here you click on "Authorize hacs".
-
-***
-
-
-
-Once you see the confirmation screen, you can close the tab and go back to Home Assistant.
-
-***
-
-
-
-Now you can click "Submit" to complete the configuration of HACS.
-
-***
-
-
-
-_If something failed, you will be taken back to the [Add your configuration step](#add-your-configuration)_
-
-## Changing the configuration
-
-If you need to change the configuration, you first need to delete the integration from the integrations list, then you need to add it back again.
diff --git a/documentation/configuration/legacy.md b/documentation/configuration/legacy.md
deleted file mode 100644
index 8b2f5fd6..00000000
--- a/documentation/configuration/legacy.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-id: legacy
-title: Configure HACS with YAML
-sidebar_label: YAML (legacy)
-description: "Configure HACS with YAML (legacy)"
----
-
-:::info
-_This page assume that you have already finished the [installation](/docs/installation/prerequisites)_
-:::
-
-## Example configuration
-
-```yaml
-hacs:
- token: d73jds8f73jkr9d8sufv2br8sd9fy92nr9f80u23r97fhse (Don't copy+paste this token, create your own)
-```
-
-| key | optional | default | description |
-| ----------------- | -------- | ----------------- | -------------------------------------------------------------------------------------------------- |
-| `token` | False | | [A Github Personal Access Token](/docs/configuration/pat) |
-| `sidepanel_title` | True | Community | The name used for the sidepanel link. |
-| `sidepanel_icon` | True | "mdi:alpha-c-box" | The icon used for the sidepanel link. |
-| `appdaemon` | True | `False` | Enable tracking of AppDaemon apps. |
-| `netdaemon` | True | `False` | Enable tracking of NetDaemon apps. |
-| `country` | True | | Set a filter based on your [A2(ISO) country code](https://www.worldatlas.com/aatlas/ctycodes.htm). |
-| `release_limit` | True | `5` | Number of releases to show in the version selector. |
-| `experimental` | True | `False` | Boolean to enable experimental features. |
diff --git a/documentation/configuration/options.md b/documentation/configuration/options.md
deleted file mode 100644
index 0f50a6f6..00000000
--- a/documentation/configuration/options.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-id: options
-title: Configuration options
-description: "Configuration options"
----
-
-:::info
-_This page assumes that you have already finished the [initial configuration](/docs/configuration/basic)_
-:::
-
-:::warning
-**This does _not_ apply if you configured HACS with YAML(legacy)**
-:::
-
-## In your Home Assistant UI go to "Configuration", then click "Integrations".
-
-
-
-## Select "Options" on the card for "HACS"
-
-
-
-## Options
-
-
-
-- `Side panel title`: The name/title you want to display for HACS in the sidebar.
-- `Side panel icon`: The icon you want to display for HACS in the sidebar.
-- `Number of releases to show`: Number of releases to show in the dropdown.
-- `Filter with country code`: Only show repositories for your country (if the repository has information about that)
-- `Enable AppDaemon apps discovery & tracking`: Enables [AppDaemon](/docs/categories/appdaemon_apps)
-- `Enable NetDaemon apps discovery & tracking`: Enables [NetDaemon](/docs/categories/netdaemon_apps)
-- `Enable experimental features`: This enables experimental features in HACS.
-
-## Click submit and wait for confirmation
-
-_This will reload HACS and your changes will be reflected when you see the confirmation._
-
-
diff --git a/documentation/configuration/pat.md b/documentation/configuration/pat.md
deleted file mode 100644
index 6705d11d..00000000
--- a/documentation/configuration/pat.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-id: pat
-title: Github Personal Access Token
-description: "Create Github Personal Access Token"
----
-
-In order to work, HACS needs to retrieve information about repositories using Github's API.
-
-:::info
-Because of the [rate limits set by Github](https://developer.github.com/v3/#rate-limiting), HACS needs to be authenticated by a Personal Access Token, that you can generate using the following steps.
-:::
-
-## Step 1 - Open browser
-
-_You are probably looking at this in a browser, so we can probably check this off._
-
-## Step 2 - Go to your GitHub "Developer settings"
-
-_And then "Personal access tokens."_
-or click here: [https://github.com/settings/tokens](https://github.com/settings/tokens)
-
-
-## Step 3 - Start generation
-
-Click the "Generate new token" button.
-
-
-
-_If you are asked to login, do so._
-
-
-
-## Step 4 - Choices
-
-First give it a logical name so that you can recognize it.
-
-Then click the "Generate token" button at the bottom.
-
-You **do not** need to check _any_ of the boxes.
-
-
-
-## Step 5 - Copy
-
-Now you see the generated token, this will be the **only** time you see it, make sure that you copy it manually or by clicking the clipboard icon.
-
-
diff --git a/documentation/configuration/start.md b/documentation/configuration/start.md
deleted file mode 100644
index c7a96ab8..00000000
--- a/documentation/configuration/start.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-id: start
-title: Configuration
-description: "Configuration"
----
-
-:::info
-_This page assumes you have already completed the [installation](/docs/installation/prerequisites)_
-:::
-
-
-:::tip
-Read [this FAQ](/docs/faq/initial_startup) about the first startup of HACS.
-:::
diff --git a/documentation/developer/backend.md b/documentation/developer/backend.md
deleted file mode 100644
index ce0282e3..00000000
--- a/documentation/developer/backend.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-id: backend
-title: Backend
-description: "Backend development"
----
-
-This page should contain:
-
-- How to get started.
-- What branch to target.
-- How to test locally.
\ No newline at end of file
diff --git a/documentation/developer/devcontainer.md b/documentation/developer/devcontainer.md
deleted file mode 100644
index 1de48c03..00000000
--- a/documentation/developer/devcontainer.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-id: devcontainer
-title: Devcontainer
-description: "Set up devcontainer"
----
-
-[The easiest way to contribute is to spin up a devcontainer](https://code.visualstudio.com/docs/remote/containers) with Visual Studio Code (VS Code). It has all the tools you need included, and it does not interfere with your system.
-
-**Requirements:**
-
-- Docker
-- VS Code
-- Remote - Containers (VS Code extension)
-
-**Open a cloned repository:**
-
-1. Fork [the HACS repository](https://github.com/hacs) that you want to contribute to.
-2. Clone the repository to your computer.
-3. Open the repository using VS Code.
-
-When you open this repository with VS code you are asked to "Reopen in Container". This will start the build of the container.
-
-*If you don't see this notification, open the command pallet and select `Remote-Containers: Open Folder in Container`*
diff --git a/documentation/developer/documentation.md b/documentation/developer/documentation.md
deleted file mode 100644
index c7db7839..00000000
--- a/documentation/developer/documentation.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-id: documentation
-title: Documentation
-description: "Documentation development"
----
-
-[](https://app.netlify.com/sites/hacs/deploys)
-
-The documentation site for HACS is build with [Docusaurus](https://docusaurus.io) and hosted on [Netlify](https://www.netlify.com/)
-
-## Contribute to the documentation
-
-There are two ways of contributing to the documentation:
-
-- Using the "Edit this page" link at the bottom of every page.
-- Locally changing (devcontainer)
-
-_All changes to the documentation should go against the `master` branch._
-The repository for the documentation is hosted @ https://github.com/hacs/documentation
-
-### Edit this page
-
-When you see something that needs changing when you browse the documentation, scroll down to the bottom of the page you are looking at, and click the "Edit this page" link.
-
-
-
-This will take you to the GitHub page for it so you can change the content.
-
-### Locally changing (devcontainer)
-
-First spin up the [devcontainer](/docs/developer/devcontainer)
-
-When you have that running issue the following commands:
-
-```bash
-yarn start
-```
-
-You have now started a local webserver that hosts the documentation on http://localhost:3000
-
-That server will reload if you do changes to the documentation so you can live see how the changes look.
-
-When you are happy with the result, push the changes to your fork and create a PR to have it merged to the HACS base.
-
-## Contents
-
-All pages for the HACS documentation is located under:
-
-```text
-documentation/content/
-```
-
-All images for the HACS documentation is located under:
-
-```text
-documentation/static/img/
-```
-
-
-## Contents linking
-
-### Reference another page
-
-Lets say you need to reference another page that is located under:
-
-```text
-documentation/content/developer/features.md
-```
-Then you need to use:
-
-```md
-[Features](/docs/developer/features)
-```
-
-### Reference images
-
-Lets say you need to reference an image that is located under:
-
-```text
-documentation/static/img/features.png
-```
-Then you need to use:
-
-```md
-
-```
-
-## New pages
-
-1. Create a new `.md` file under `documentation/content/` in a sub-directory that fits the purpose of the file.
-1. Add a reference to that file in `documentation/sidebars.js`
-
-At the top of all pages you should have this:
-
-```text
----
-id: An ID for that file, ie. 'feature' (lowercase)
-title: A Title for the page, this will also be used in the sidebar, ie. Feature
-description: "A nice description here"
----
-```
diff --git a/documentation/developer/frontend.md b/documentation/developer/frontend.md
deleted file mode 100644
index 81fc5150..00000000
--- a/documentation/developer/frontend.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-id: frontend
-title: Frontend
-description: "Frontend development"
----
-
-_All changes to the documentation should go against the `master` branch._
-The repository for the frontend is hosted @ https://github.com/hacs/frontend
-
-First spin up the [devcontainer](/docs/developer/devcontainer)
-
-When you have that running issue the following commands:
-
-```bash
-yarn start
-```
-
-When this is running it spins up a dev server, which you can attach to from a Home Assistant instance that is running HACS.
-
-To attach the development frontend add this to your Home Assistant installation that is running HACS:
-
-```yaml
-panel_custom:
- - name: hacs-dev-frontend
- sidebar_title: HACS (Dev frontend server)
- sidebar_icon: mdi:alert-circle
- url_path: hacs_dev
- js_url: http://localhost:5000/main.js
-```
-
-Change `localhost` for the IP of your devserver if not the same.
diff --git a/documentation/developer/start.md b/documentation/developer/start.md
deleted file mode 100644
index 973e132d..00000000
--- a/documentation/developer/start.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-id: start
-title: Getting started
-description: "Getting started with HACS development"
----
-
-This integration is **massive** and there are a lot of areas to contribute to.
-
-- [Documentation](/docs/developer/documentation)
-- [Backend](/docs/developer/backend)
-- [Frontend](/docs/developer/frontend)
-- [Translation](/docs/developer/translation)
-
-[If you are looking for the documentation to publish your repository to be a part of the default repositories in HACS have a look here.](/docs/publish/start)
diff --git a/documentation/developer/translation.md b/documentation/developer/translation.md
deleted file mode 100644
index acb8b9ea..00000000
--- a/documentation/developer/translation.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-id: translation
-title: Translation
-description: "HACS Translations"
----
-
-To handle submissions of translated strings we are using [Lokalise](https://lokalise.com) they provide us with an amazing platform that is easy to use and maintain.
-
-
-
-To help out with the translation of HACS you need an account on Lokalise, the easiest way to get one is to [click here](https://lokalise.com/login/) then select "Log in with GitHub".
-
-When you have created your account [click here to join the HACS project on Lokalise.](https://lokalise.com/public/854515055f679055040b37.42677693/)
-
-If you are unsure on how to proceed their documentation is really good, and you can [find that here.](https://docs.lokalise.com/en/) or send me a message @ [discord](https://discord.gg/apgchf8) (username: `ludeeus#4212`)
-
-If you want to add translations for a language that is not listed please [open a FR here](https://github.com/hacs/frontend/issues/new)
-
-Before each release new translations are pulled from Lokalise, so if you have added something look for it in the next version of HACS.
-
-If you add elements to the UI of HACS that needs translations, update the [`en.json`](https://github.com/hacs/frontend/blob/master/src/localize/languages/en.json) file, when your PR are merged those new keys will be added to Lokalise ready to be translated.
diff --git a/documentation/faq/addons.md b/documentation/faq/addons.md
deleted file mode 100644
index 5feecdcb..00000000
--- a/documentation/faq/addons.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-id: addons
-title: Add-ons?
-description: "NO, no, nope, this is not an add-on, and does not handle add-ons"
----
-
-- You can not install HACS as an add-on, HACS is an integration, and not an add-on
-- HACS does not handle add-ons.
-
-Add-ons and HACS has nothing to do with each other, they are completely different.
\ No newline at end of file
diff --git a/documentation/faq/custom_repositories.md b/documentation/faq/custom_repositories.md
deleted file mode 100644
index 2f76218d..00000000
--- a/documentation/faq/custom_repositories.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-id: custom_repositories
-title: Custom Repositories
-description: "Custom repositories in HACS"
----
-
-[HACS already has a lot of repositories by default](https://hacs.xyz/default_repositories)
-
-But there are a number of different reasons why a developer might not want to publish their repository to HACS, for these situations you can in many cases add it to HACS as a custom repository.
-
-:::warning
-Not all repositories will work in HACS, since HACS still needs the repository to have a known structure.
-:::
-
-If you want to try and add a custom repository to HACS do the following:
-
-
-
-1. Go to any of the sections (integrations, frontend, automation).
-1. Click on the 3 dots in the top right corner.
-1. Select "Custom repositories"
-1. Add the URL to the repository.
-1. Select the correct category.
-1. Click the "ADD" button.
-
-
diff --git a/documentation/faq/hassio_only.md b/documentation/faq/hassio_only.md
deleted file mode 100644
index 772f20cc..00000000
--- a/documentation/faq/hassio_only.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-id: hassio_only
-title: Is this for hass.io only?
-description: "NO, no, nope, this is for all Home Assistant installations (windows may have issues)"
----
-
-# No
-
-It's not.
-
-You can use this on _any_ Home Assistant installation.
-
-_Windows might have issues, but if you are running HA on Windows you are probably used to that._
\ No newline at end of file
diff --git a/documentation/faq/highlights.md b/documentation/faq/highlights.md
deleted file mode 100644
index 90c8836b..00000000
--- a/documentation/faq/highlights.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-id: highlights
-title: What HACS can do
-description: "TLDR;"
----
-
-In short:
-
-- Help you discover new custom elements.
-- Help you install (download) new custom elements.
-- Help you keep track of your custom elements.
\ No newline at end of file
diff --git a/documentation/faq/initial_startup.md b/documentation/faq/initial_startup.md
deleted file mode 100644
index 80664d50..00000000
--- a/documentation/faq/initial_startup.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-id: initial_startup
-title: "Initial startup"
-description: "Initial startup"
----
-HACS does not ship with any knowledge about the repositories it is supposed to show.
-
-Since there is no central "HACS server", every installation of HACS fetches this information from GitHub, it has to get the information about all [default repositories](/default_repositories)
-
-To get the information that is needed to show a representation of the repository in HACS, HACS uses the [GitHub API](https://docs.github.com/en/rest), this API is [rate limited](https://docs.github.com/en/rest/overview/resources-in-the-rest-api#rate-limiting) and when you hit that rate limit HACS will pause any communitation to the GitHub API until the rate limit reset (can take up to one hour).
-
-:::info
-For new installation of HACS with the current amount of default repositories you will hit that rate limit on the initial startup after installing HACS.
-Because of this HACS will be in a "Starting up" state until it's done fetching the information for all [default repositories](/default_repositories)
-
-Which in return will cause the initial startup of HACS to take over 1 hour to finish.
-:::
\ No newline at end of file
diff --git a/documentation/faq/installation.md b/documentation/faq/installation.md
deleted file mode 100644
index 2303975e..00000000
--- a/documentation/faq/installation.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-id: installation
-title: "How does it work: Installation"
-description: "How does it work: Installation"
----
-When you install an element this is what's happening:
-
-1. The local target directory(folder) is deleted.
-1. A new local target directory is created.
-1. All expected files are downloaded to that directory.
-1. The files it downloads depends on the type.
\ No newline at end of file
diff --git a/documentation/faq/limitations.md b/documentation/faq/limitations.md
deleted file mode 100644
index 42707da3..00000000
--- a/documentation/faq/limitations.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-id: limitations
-title: Known limitations
-description: "Known limitations"
----
-- If you install/upgrade/remove or add a custom repository while the background task is running, do **not** restart Home Assistant until that task is done, if you do your action will not be saved.
\ No newline at end of file
diff --git a/documentation/faq/status_not_loaded.md b/documentation/faq/status_not_loaded.md
deleted file mode 100644
index 27c0426e..00000000
--- a/documentation/faq/status_not_loaded.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-id: status_not_loaded
-title: "Status: Not Loaded"
-description: "What to do if the status of a Lovelace element is not loaded"
----
-
-
-
-When you see this message you have one or more resources installed with HACS that are not properly loaded in Lovelace.
-
-To find out what element it is, look for the repository with a "Not Loaded" header in the Frontend section of HACS.
-
-
-
-This will trigger if you are not using the expected URL, or if it's not included in the first place.
-
-## Lovelace in storage more (UI)
-
-Something strange has happened, click the 3 dots in the card for the repository and select "Reinstall".
-
-## Lovelace in storage more (YAML)
-
-Add the correct URL to the `resource` key under your `lovelace` configuration entry.
-To find the URL click the 3 dots in the card for the repository and select "Reinstall".
-
-:::tip
-[For information about the base of URL have a look here.](/docs/categories/plugins#special-notes-about-downloaded-lovelace-plugins)
-:::
diff --git a/documentation/faq/upgrade.md b/documentation/faq/upgrade.md
deleted file mode 100644
index bdbb3df9..00000000
--- a/documentation/faq/upgrade.md
+++ /dev/null
@@ -1,6 +0,0 @@
----
-id: upgrade
-title: "How does it work: Upgrade"
-description: "How does it work: Upgrade"
----
-The same as installation.
\ No newline at end of file
diff --git a/documentation/faq/what.md b/documentation/faq/what.md
deleted file mode 100644
index 07816dd0..00000000
--- a/documentation/faq/what.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-id: what
-title: What is HACS?
-description: "What is HACS?"
----
-
-_Currently I have no idea what to write here..._
diff --git a/documentation/installation/installation.md b/documentation/installation/installation.md
deleted file mode 100644
index d99a5258..00000000
--- a/documentation/installation/installation.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-id: installation
-title: Installation
-description: "HACS installation steps"
----
-
-You install HACS by using the [HACS install script](https://github.com/hacs/install).
-
-:::info
-If you are not sure what type of Home Assistant you are using, then you should probably not install HACS (or any other custom integration), but if you really want to know, you can find it here:
-
-1. In your Home Assistant UI go to the Configuration panel
-1. Click on the "Info" block.
-1. Under the System health card it will say "Installation Type xxxx"
-:::
-
-## Home Assistant OS
-
-1. Go to the Supervisor panel
-1. Install one of the SSH add-ons (you need to enable advanced mode in your user profile to see them)
-1. Configure the SSH add-on you chose by following the documentation for it
-1. Start the SSH add-on
-1. Connect to the SSH add-on
-1. Run the HACS install script
-
-```bash
-wget -q -O - https://install.hacs.xyz | bash -
-```
-
-## Home Assistant Container
-
-For Home Assistant Container you have 2 options.
-
-### Option 1: Run the installer on the host OS
-
-1. Open a terminal
-1. Change directory to your Home Assistant configuration directory
-1. Run the HACS install script
-
-```bash
-wget -q -O - https://install.hacs.xyz | bash -
-```
-
-### Option 2: Run the installer inside the container
-
-1. Open a terminal
-1. Go inside the container with `docker exec -it homeassistant bash`
-1. Run the HACS install script
-
-```bash
-wget -q -O - https://install.hacs.xyz | bash -
-```
-
-4. Exit the container with `exit`
-
-
-## Home Assistant Core
-
-1. Open a terminal
-1. Change to the user that is running Home Assistant
-1. Run the HACS install script
-
-```bash
-wget -q -O - https://install.hacs.xyz | bash -
-```
-
-## Home Assistant Supervised
-
-The same as [Home Assistant OS](#home-assistant-os), but you can also run the script directly on the host OS.
-
-1. Open a terminal
-1. Run the HACS install script
-
-```bash
-wget -q -O - https://install.hacs.xyz | bash -
-```
\ No newline at end of file
diff --git a/documentation/installation/prerequisites.md b/documentation/installation/prerequisites.md
deleted file mode 100644
index c84f9bdb..00000000
--- a/documentation/installation/prerequisites.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-id: prerequisites
-title: Prerequisites
-description: "Prerequisites"
----
-
-## Requirements
-
-:::warning
-If you do not have or know **_all_** of the following, **do not** try to install/use HACS.
-:::
-
-- Home Assistant version `2020.12.0` or newer
-- A GitHub account
-- A [supported](https://github.com/home-assistant/architecture/blob/master/adr/0012-define-supported-installation-method.md) Home Assistant installation
-- Access to the filesystem where Home Assistant is located
-- **You know how to access the Home Assistant log file**
-- **A stable internet connection with sufficient available data or no data caps**
diff --git a/documentation/installation/remove.md b/documentation/installation/remove.md
deleted file mode 100644
index 36205ddf..00000000
--- a/documentation/installation/remove.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-id: remove
-title: Remove
-description: "Remove HACS"
----
-
-If you want to remove HACS you need to do that using the following steps.
-
-**This should _only_ be done if you are not planing on using HACS anymore!**
-
-1. Remove the configuration from `configuration.yaml` (if configured with legacy (YAML)) or remove it using the trashbin icon on the integration page.
-1. Restart Home Assistant **important**
-1. Restart Home Assistant (yes, this needs to be done twice) **important**
-1. Delete the `hacs` directory under `custom_components`.
-1. Delete all files and directories containing `hacs` under the `.storage` directory.
-1. Restart Home Assistant.
-
-When removed the wrong way. An option is to install it again.
-Just move hacs back to custom components and reboot. And start the remove procedure again.
-
-
-# Revoke OAuth access
-
-If you are using HACS with OAuth, you also need to revoke the access to complete the removal.
-
-1. Navigate to https://github.com/settings/applications
-1. Find HACS in the list of apps, click on the 3 dots to the right of HACS
-1. Select "Revoke"
\ No newline at end of file
diff --git a/documentation/issues.md b/documentation/issues.md
deleted file mode 100644
index b8e2d6b8..00000000
--- a/documentation/issues.md
+++ /dev/null
@@ -1,167 +0,0 @@
----
-id: issues
-title: Issues
-description: "Got issues?"
----
-
-**[First lets start out by stating that _ALL_ issues should be reported here](https://github.com/hacs/integration/issues)**
-
-# What should be in the issue?
-
-When you create an issue in the repository for HACS, you start by selecting a template.
-
-All templates have a defined structure and it is **expected** that you follow it.
-
-_Issues that are missing required information can (will) be closed._
-
-
-
-## Feature request
-
-You select this when you have an idea on how HACS could be better.
-
-To be able to handle a feature request you need to write a good description, it should show that this is something that you have invested time in.
-
-You can see examples of good/bad feature requests further down on this page.
-
-## Flag
-
-This should **only** be used, when there is grounds for removing (blacklisting) a repository in HACS.
-
-When you are flagging a repository you need to supply at least these:
-
-- A good description for why.
-- The name of the repository.
-- Proof that you have tried to contact the owner of that repository (link to issue)
-
-_If you are flagging it because you don't like it, have issues with it, or it's not working, you should report that to the repository and not here._
-
-## Issues
-
-You use this when you have issues with HACS.
-
-[To enable debug logs for HACS (required when adding an issue) have a look here](https://hacs.xyz/docs/basic/logs).
-
-Logs are **more** then _just_ errors, with debug logging it gives the person investigating the issue a full picture of what happened.
-
-
-**What an issue should contain depends on the type, but at least:**
-
-- A GOOD description of the issue.
-- Debug logs.
-- Steps to reproduce the issue.
-- If the issue is in the UI, add screenshots.
-
-You can see examples of good/bad issues further down on this page.
-
-:::warning
-_Issues that are missing required information can (will) be closed._
-:::
-
-:::tip
-oh... and almost forgot... `latest` is **NOT** a version.
-:::
-
-# Examples
-
-This is a collection of good/bad feature requests/issues.
-
-## Examples of bad feature requests
-
-```text
-Is it possible to get a persistent notification if there is a component or card has a upgrade?
-```
-
-***
-
-```text
-# Describe the solution you'd like
-Could be possible to add support for python_scripts?
-
-# Describe alternatives you've considered
-custom_updater support them.
-```
-
-## Examples of good feature requests
-
-```text
-# Is your feature request related to a problem? Please describe.
-I'm always frustrated when the different plugins and Lovelace cards don't have a decent description.
-
-For me, HACS is also a way to find new components of which I didn't know they even existed. But, a lot of the integration and components don't provide decent info. This requires me to navigate to the repository and sometimes even the source code to find out what the component is about.
-
-# Describe the solution you'd like
-Require a minimum amount of info (good description, info.md) before inclusion in HACS and perhaps a tagging system of what the integration/plugin is about.
-
-Examples of tags would be: Denkovi (manufacturer), Ethernet relay (product type), ...
-```
-
-***
-
-```text
-# Describe the solution you'd like
-One benefit of AppDaemon that I think is underutilized is how reusable and shareable apps are. I think a lot of Home Assistant users are put off by the learning curve of learning Python to use AppDaemon. However, it's very possible for people to create apps that anyone can use without modifying the underlying Python code, that just take some YAML configuration to set up. It would be great to be able to have a section in HACS, in addition to custom components and Lovelace plugins, for custom AppDaemon apps that could auto update.
-
-# Describe alternatives you've considered
-If this isn't something you're interested in implementing with HACS, I've looked at some other options for having apps auto update, but I think this would be the cleanest route and would put everything custom in one interface.
-
-# Additional context
-Apps would land in the appdaemon/apps/
-