mirror of
https://github.com/zulip/zulip.git
synced 2025-10-23 04:52:12 +00:00
docs: Update .html links to .md.
Sphinx/ReadTheDocs supports automatically translating links written as to `.md` files to point to the corresponding `.html` files, so this migration does not change the resulting HTML output in ReadTheDocs. But it does fix apparent broken links on GitHub. This doesn't prevent people from reading the documentation on GitHub (so doesn't mitigate the fact that some rtd-specific syntax does not render properly on GH), but it will prevent us from getting erroneous issues reported about the hyperlinks not working. Fixes: #11087.
This commit is contained in:
committed by
Tim Abbott
parent
6191b4d93a
commit
c87893feea
@@ -92,12 +92,12 @@ the backend, but does in JavaScript.
|
||||
|
||||
For the third-party services like Postgres, Redis, Nginx, and RabbitMQ
|
||||
that are documented in the
|
||||
[architecture overview](../overview/architecture-overview.html), we rely on the
|
||||
[architecture overview](../overview/architecture-overview.md), we rely on the
|
||||
versions of those packages provided alongside the Linux distribution
|
||||
on which Zulip is deployed. Because Zulip
|
||||
[only supports Ubuntu in production](../production/requirements.html), this
|
||||
[only supports Ubuntu in production](../production/requirements.md), this
|
||||
usually means `apt`, though we do support
|
||||
[other platforms in development](../development/setup-advanced.html). Since
|
||||
[other platforms in development](../development/setup-advanced.md). Since
|
||||
we don't control the versions of these dependencies, we avoid relying
|
||||
on specific versions of these packages wherever possible.
|
||||
|
||||
@@ -120,7 +120,7 @@ backported versions of other dependencies (e.g. `camo`, to fix a buggy
|
||||
possible by getting issues addressed in the upstream distributions.
|
||||
|
||||
We also rely on the `pgroonga` PPA for the `pgroonga` postgres
|
||||
extension, used by our [full-text search](full-text-search.html).
|
||||
extension, used by our [full-text search](full-text-search.md).
|
||||
|
||||
## Python packages
|
||||
|
||||
@@ -230,7 +230,7 @@ super fast internet. You can use tmux or screen to make sure that the
|
||||
[script keeps running even if you get disconnected][stack-overflow]
|
||||
from the SSH session.
|
||||
|
||||
[mypy-docs]: ../testing/mypy.html
|
||||
[mypy-docs]: ../testing/mypy.md
|
||||
[requirements-readme]: https://github.com/zulip/zulip/blob/master/requirements/README.md
|
||||
[stack-overflow]: https://askubuntu.com/questions/8653/how-to-keep-processes-running-after-ending-ssh-session
|
||||
[caching]: https://help.github.com/en/articles/caching-your-github-password-in-git
|
||||
@@ -254,7 +254,7 @@ reasoning here.
|
||||
dependencies in the `yarn.lock` file; `yarn install` updates the
|
||||
`yarn.lock` files.
|
||||
* `tools/update-prod-static`. This process is discussed in detail in
|
||||
the [static asset pipeline](../subsystems/front-end-build-process.html) article,
|
||||
the [static asset pipeline](../subsystems/front-end-build-process.md) article,
|
||||
but we don't use the `node_modules` directories directly in
|
||||
production. Instead, static assets are compiled using our static
|
||||
asset pipeline and it is the compiled assets that are served
|
||||
@@ -298,7 +298,7 @@ Zulip uses the [iamcal emoji data package][iamcal] for its emoji data
|
||||
and sprite sheets. We download this dependency using `npm`, and then
|
||||
have a tool, `tools/setup/build_emoji`, which reformats the emoji data
|
||||
into the files under `static/generated/emoji`. Those files are in
|
||||
turn used by our [markdown processor](../subsystems/markdown.html) and
|
||||
turn used by our [markdown processor](../subsystems/markdown.md) and
|
||||
`tools/update-prod-static` to make Zulip's emoji work in the various
|
||||
environments where they need to be displayed.
|
||||
|
||||
@@ -309,11 +309,11 @@ directories, with `scripts/lib/clean_emoji_cache.py` responsible for
|
||||
garbage-collection. This caching and garbage-collection is required
|
||||
because a correct emoji implementation involves over 1000 small image
|
||||
files and a few large ones. There is a more extended article on our
|
||||
[emoji infrastructure](emoji.html).
|
||||
[emoji infrastructure](emoji.md).
|
||||
|
||||
### Translations data
|
||||
|
||||
Zulip's [translations infrastructure](../translating/translating.html) generates
|
||||
Zulip's [translations infrastructure](../translating/translating.md) generates
|
||||
several files from the source data, which we manage similar to our
|
||||
emoji, but without the caching (and thus without the
|
||||
garbage-collection). New translations data is downloaded from
|
||||
|
Reference in New Issue
Block a user