| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Adding an additional output plugin to mdbook causes it to create an
extra level of subdirectories in its build directory; one for each
output plugin.
We add an intermediate build directory `build`, and after building the
individual mdbooks, construct the `html` directory with the desired
layout.
|
|
Suppose in raw markdown we have:
```markdown
See [foo][barr].
[bar]: https://link-to-bar
```
The intent is to link the text "foo", but because of a typo it used the
label barr instead of bar. The result is that the rendered html won't
have a link at all. The text will be rendered literally as
`[foo][barr]`. Since there's no link (not even a broken one), a link
checker run over the rendered output won't spot the problem.
The mdbook-linkcheck plugin correctly detects this issue. However, it
doesn't understand links that go between our two mdbook projects since
the relative paths in the source don't match the relative paths in the
rendered output. Since checking whether the links are non-broken is
already covered by `bin/check_links` (using linklint), we can disable
checking the link destinations altogether.
|
|
This is much more convenient for folks who don't want to mess
with the jenga tower that is mermaid-cli.
|
|
The build script now only uses mmdc and a temporary conditionally,
and otherwise (for now) leaves mermaid blocks unformatted.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For those that are already correct, list the correct URL on the main
site, and mark them as "implicit" so we can double-check them.
For those that remain, remove all old links to gitweb.tpo, and
link to gitlab.tpo instead.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This deliberately doesn't make any changes in the current formatting
or targets (yet); that can come later. It uses the existing yaml
format and file.
|
|
|
|
|
|
|
|
|
|
|
