|7a142936f5||1 hour ago|
|.github||2 hours ago|
|assets||3 months ago|
|attic||3 months ago|
|changelogs||1 hour ago|
|content||2 weeks ago|
|data||1 hour ago|
|data-definitions||2 years ago|
|informal||11 months ago|
|layouts||2 days ago|
|meta||2 weeks ago|
|scripts||2 hours ago|
|static||8 months ago|
|themes||7 months ago|
|.gitignore||1 year ago|
|.gitmodules||2 years ago|
|.htmltest.yaml||7 months ago|
|CONTRIBUTING.rst||3 months ago|
|LICENSE||7 years ago|
|README.md||7 months ago|
|config.toml||2 weeks ago|
|openapi_extensions.md||12 months ago|
|package-lock.json||1 year ago|
|package.json||7 months ago|
|redocly.yaml||2 hours ago|
This repository contains the Matrix Specification. The current release version is rendered at https://spec.matrix.org, while the latest available build of the
main branch is at https://spec.matrix.org/unstable.
Developers looking to use Matrix should join #matrix-dev:matrix.org on Matrix for help.
Spec authors and proposal writers are welcome to join #matrix-spec:matrix.org. We welcome contributions! See CONTRIBUTING.rst for details.
The Matrix spec is compiled with Hugo (a static site generator) with the following structure:
/assets: assets that need postprocessing using Hugo Pipes. For example, Sass files would go here.
/content: files that will become pages in the site go here. Typically these are Markdown files with some YAML front matter indicating, among other things, what layout should be applied to this page. The organization of files under
/contentdetermines the organization of pages in the built site.
/data: this can contain TOML, YAML, or JSON files. Files kept here are directly available to template code as data objects, so templates don't need to load them from a file and parse them. This is also where our Swagger/OpenAPI definitions and schemas are.
/layouts: this contains Hugo templates. Some templates define the overall layout of a page: for example, whether it has header, footer, sidebar, and so on.
/layouts/partials: these templates can be called from other templates, so they can be used to factor out template code that's used in more than one template. An obvious example here is something like a sidebar, where several different page layouts might all include the sidebar. But also, partial templates can return values: this means they can be used like functions, that can be called by multiple templates to do some common processing.
/layouts/shortcodes: these templates can be called directly from files in
/static: static files which don't need preprocessing. JS or CSS files could live here.
/themes: you can use just Hugo or use it with a theme. Themes primarily provide additional templates, which are supplied in a
/themes/$theme_name/layoutsdirectory. You can use a theme but customise it by providing your own versions of any of the theme layouts in the base
/layoutsdirectory. That is, if a theme provides
/themes/$theme_name/layouts/sidebar.htmland you provide
/layouts/sidebar.html, then your version of the template will be used.
It also has the following top-level file:
config.toml: site-wide configuration settings. Some of these are built-in and you can add your own. Config settings defined here are available in templates. All these directories above are configurable via
Additionally, the following directories may be of interest:
/attic: Here contains historical sections of specification and legacy drafts for the specification.
/changelogs: Various bits of changelog for the specification areas.
/data-definitions: Bits of structured data consumable by Matrix implementations.
/meta: Documentation relating to the spec's processes that are otherwise untracked (release instructions, etc).
/scripts: Various scripts for generating the spec and validating its contents.
Authoring changes to the spec
Please read CONTRIBUTING.rst before authoring a change to the spec. Note that spec authoring takes place after an MSC has been accepted, not as part of a proposal itself.
Install the extended version (often the OS default) of Hugo: https://gohugo.io/getting-started/installing. Note that at least Hugo v0.93.0 is required.
Alternatively, use the Docker image at https://hub.docker.com/r/klakegg/hugo/. (The "extended edition" is required to process the SCSS.)
npm ito install the dependencies and fetch the docsy git submodule. Note that this will require NodeJS to be installed.
npm run get-proposalsto seed proposal data. This is merely for populating the content of the "Spec Change Proposals" page and is not required.
docker run --rm -it -v $(pwd):/src -p 1313:1313 klakegg/hugo:ext serve) to run a local webserver which builds whenever a file change is detected. If watching doesn't appear to be working for you, try adding
--disableFastRenderto the commandline.
Edit the specification 🙂
We use a highly customized Docsy theme for our generated site, which uses Bootstrap and Font Awesome. If you're looking at making design-related changes to the spec site, please coordinate with us in #matrix-docs:matrix.org before opening a PR.
Building the specification
If for some reason you're not a CI/CD system and want to render a static version of the spec for yourself, follow the above
steps for authoring changes to the specification and instead of
hugo serve run
hugo -d "spec" - this will generate the
/spec. If you'd like to serve the spec off a path instead of a domain root (eg:
hugo -d "spec" command.
For building the swagger definitions, create a python3 virtualenv and activate it. Then run
pip install -r ./scripts/requirements.txt
python ./scripts/dump-swagger.py to generate it to
./scripts/swagger/api-docs.json. To make use of the generated file,
there are a number of options:
- You can open
./scripts/swagger-preview.htmlin your browser, and then open the file by clicking on
Local JSON File.
- You can run a local HTTP server by running
./scripts/swagger-http-server.py, and then view the documentation by opening
./scripts/swagger-preview.htmlin your browser.
Specification issues are tracked on github at https://github.com/matrix-org/matrix-spec/issues.
See meta/github-labels.rst for information on what the labels mean.