Made changes to summary and custom_frontend to match addition of asyncapi spec

This commit is contained in:
Gary Conroy 2021-02-26 15:44:16 +00:00
parent 6cb09643e9
commit e5edf73bf9
2 changed files with 2 additions and 2 deletions

View file

@ -21,7 +21,7 @@
- [Docker Development](contributing/docker_development.md)
- [Local Development](contributing/local_development.md)
- [Theming Guide](contributing/theming.md)
- [Websocket/HTTP API](contributing/websocket_http_api.md)
- [HTTP API](contributing/http_api.md)
- [Creating a Custom Frontend](contributing/custom_frontend.md)
- [Tests](contributing/tests.md)
- [Federation Development](contributing/federation_development.md)

View file

@ -1,6 +1,6 @@
# Creating a Custom Frontend
The backend and frontend are completely decoupled, and run in independent Docker containers. They only communicate over the [Lemmy API](websocket_http_api.md), which makes it quite easy to write alternative frontends.
The backend and frontend are completely decoupled, and run in independent Docker containers. They only communicate over the [Lemmy API](api_reference.md), which makes it quite easy to write alternative frontends.
This creates a lot of potential for custom frontends, which could change much of the design and user experience of Lemmy. For example, it would be possible to create a frontend in the style of a traditional forum like [phpBB](https://www.phpbb.com/), or a question-and-answer site like [stackoverflow](https://stackoverflow.com/). All without having to think about database queries, authentification or ActivityPub, which you essentially get for free.