1 # About the Tor Specifications documents
3 The canonical, official, versions of these documents are on the
4 [Tor Specifications website](https://spec.torproject.org/)
5 maintained by the [Tor Project](https://www.torproject.org/).
7 Only the Tor Specifications themselves are approved.
8 The [Proposals](../proposals/) are, by their nature, drafts.
10 When linking to the Specifications,
11 consider using one of the links advertised in the
12 [Table of Permalinks](permalinks.html).
16 The Specifications and Proposals are maintained by the Tor Project
18 [gitlab repository](https://gitlab.torproject.org/tpo/core/torspec/).
20 Corrections and clarifications are welcome.
21 To propose a change to the Tor protocol, use the
22 [Proposals process](proposals/001-process.txt)
26 The documents are in Markdown and formatted with
27 [mdbook](https://rust-lang.github.io/mdBook/).
28 To build the formatted HTML:
32 git clone https://gitlab.torproject.org/tpo/core/torspec/
37 The output is then in `html/`.
39 ## Source code structure, and output webtree
41 There are two mdbook books here:
43 * **The Tor Specifications**: source code in `specs/`,
44 formatted output in `html/`.
46 * **Proposals**: source code in `proposals/`,
47 formatted output in `html/proposals/`.
49 Each book's source files are listed,
50 and the chapter defined,
52 The format is pretty restrictive;
54 [mdbook documentation](https://rust-lang.github.io/mdBook/format/summary.html).
58 To edit these specs, clone the
59 [git repository](https://gitlab.torproject.org/tpo/core/torspec/)
61 appropriate file in the `spec` directory. These files will match
62 the URLs of their corresponding pages, so if you want to edit
63 `tor-spec/flow-control.html`,
64 you'll be looking for a file
65 called `spec/tor-spec/flow-control.md`.
67 We have started a [style guide](./STYLE.md) for writing new parts of
68 this spec; as of 2023 it is quite preliminary. You should feel free to