+- [yaml](http://yaml.org/) file configuration
+- Installable (pwa)
+- Search
+- Grouping
+- Theme customization
+- Offline health check
+- keyboard shortcuts:
+ - `/` Start searching.
+ - `Escape` Stop searching.
+ - `Enter` Open the first matching result (respects the bookmark's `_target` property).
+ - `Alt`/`Option` + `Enter` Open the first matching result in a new tab.
+
+## Getting started
+
+### Using Docker
+
+The fastest and recommended way to get your Homer instance up and running is
+with Docker. The Docker image comes with a web server built-in so that all you
+need to worry about is your config file.
+
+Internally, the Docker image looks for the assets in the `/www/assets` directory
+so you can bind a volume from your host machine to that directory in order to
+modify and persist the configuration files. The web server serves the dashboard
+on port 8080, but using a port binding will let you expose that to whatever
+external port you like.
+
+#### docker
+
+To launch container:
+
+```sh
+docker run -d \
+ -p 8080:8080 \
+ -v </your/local/assets>:/www/assets \
+ --restart=always \
+ b4bz/homer:latest
+```
+
+Use `UID` and/or `GID` env var to change the assets owner:
+
+```sh
+docker run -d \
+ -p 8080:8080 \
+ -v </your/local/assets>:/www/assets \
+ -e "UID=1000" -e "GID=1000" \
+ --restart=always \
+ b4bz/homer:latest
+```
+
+#### docker-compose
+
+It is recommended to use docker-compose to manage your Docker containers, and
+below you can find a simple compose yaml file. Copy the contents into a
+`docker-compose.yaml` and modify the volume binding to your desired directory to
+get started:
+
+```yaml
+version: '3.3'
+services:
+ homer:
+ restart: always
+ volumes:
+ - /your/local/assets:/www/assets
+ ports:
+ - 8080:8080
+ image: b4bz/homer
+```
+
+To launch container:
+
+```sh
+cd /path/to/docker-compose.yml
+docker-compose up -d
+```
+
+Use `UID` and/or `GID` env var to change the assets owner: