MatrixSynapse/docs
Andrew Morgan ec9224bf9a
Make `POST /_matrix/client/v3/rooms/{roomId}/report/{eventId}` endpoint return 404 if event exists, but the user lacks access (#15300)
2023-03-21 13:24:03 +00:00
..
admin_api Admin API endpoint to delete a reported event (#15116) 2023-02-28 12:09:10 +00:00
changelogs
development Document how to run Synapse (#15022) 2023-02-08 12:58:36 +00:00
modules Update spam checker documentation for moved media modules. (#15175) 2023-02-28 12:51:11 -05:00
other
privacy_policy_templates/en
setup Document that our Docker images are mirrored to GHCR. (#15282) 2023-03-21 12:51:03 +01:00
systemd-with-workers Include `x_forwarded` in workers example configs (#14667) 2023-01-13 14:06:58 +00:00
usage Correct documentation about registration_shared_secret_path (#15168) 2023-02-28 11:09:31 +00:00
website_files
.sample_config_header.yaml
CAPTCHA_SETUP.md
README.md
SUMMARY.md Initial batch of notes on faster joins (#14677) 2023-01-30 21:27:52 +00:00
ancient_architecture_notes.md
application_services.md Fix missing field in AS documentation (#14845) 2023-01-16 12:59:15 +00:00
architecture.md
auth_chain_diff.dot
auth_chain_diff.dot.png
auth_chain_difference_algorithm.md
code_style.md Remove outdated commands from the code style doc & point to the contributing guide. (#14773) 2023-01-11 15:21:12 +00:00
consent_tracking.md
delegate.md Clarify limitations of SRV delegation in documentation (#14959) 2023-02-08 10:44:19 +00:00
deprecation_policy.md
favicon.png
favicon.svg
federate.md
jwt.md
log_contexts.md
manhole.md
media_repository.md
message_retention_policies.md
metrics-howto.md
openid.md Documentation using Shibboleth with OIDC Plugin for SSO. (#15112) 2023-02-23 12:54:03 -05:00
opentracing.md
password_auth_providers.md
postgres.md
presence_router_module.md
replication.md
reverse_proxy.md
room_and_user_statistics.md
sample_config.yaml
sample_log_config.yaml
server_notices.md
spam_checker.md
sso_mapping_providers.md
structured_logging.md
synctl_workers.md
tcp_replication.md
templates.md
turn-howto.md
upgrade.md Make `POST /_matrix/client/v3/rooms/{roomId}/report/{eventId}` endpoint return 404 if event exists, but the user lacks access (#15300) 2023-03-21 13:24:03 +00:00
user_directory.md
welcome_and_overview.md
workers.md Load `/register/available` endpoint on workers (#15268) 2023-03-17 09:50:31 -04:00

README.md

Synapse Documentation

The documentation is currently hosted here. Please update any links to point to the new website instead.

About

This directory currently holds a series of markdown files documenting how to install, use and develop Synapse. The documentation is readable directly from this repository, but it is recommended to instead browse through the website for easier discoverability.

Adding to the documentation

Most of the documentation currently exists as top-level files, as when organising them into a structured website, these files were kept in place so that existing links would not break. The rest of the documentation is stored in folders, such as setup, usage, and development etc. All new documentation files should be placed in structured folders. For example:

To create a new user-facing documentation page about a new Single Sign-On protocol named "MyCoolProtocol", one should create a new file with a relevant name, such as "my_cool_protocol.md". This file might fit into the documentation structure at:

  • Usage
    • Configuration
      • User Authentication
        • Single Sign-On
          • My Cool Protocol

Given that, one would place the new file under usage/configuration/user_authentication/single_sign_on/my_cool_protocol.md.

Note that the structure of the documentation (and thus the left sidebar on the website) is determined by the list in SUMMARY.md. The final thing to do when adding a new page is to add a new line linking to the new documentation file:

- [My Cool Protocol](usage/configuration/user_authentication/single_sign_on/my_cool_protocol.md)

Building the documentation

The documentation is built with mdbook, and the outline of the documentation is determined by the structure of SUMMARY.md.

First, get mdbook. Then, from the root of the repository, build the documentation with:

mdbook build

The rendered contents will be outputted to a new book/ directory at the root of the repository. Please note that index.html is not built by default, it is created by copying over the file welcome_and_overview.html to index.html during deployment. Thus, when running mdbook serve locally the book will initially show a 404 in place of the index due to the above. Do not be alarmed!

You can also have mdbook host the docs on a local webserver with hot-reload functionality via:

mdbook serve

The URL at which the docs can be viewed at will be logged.

Configuration and theming

The look and behaviour of the website is configured by the book.toml file at the root of the repository. See mdbook's documentation on configuration for available options.

The site can be themed and additionally extended with extra UI and features. See website_files/README.md for details.