Revert "docs: Update .html links to .md."

This doesn't work without the CommonMark upgrade.

This reverts commit c87893f.

Author: timabbott

Diff for: docs/contributing/chat-zulip-org.md

@@ -32,7 +32,7 @@ minutes to a few hours, depending on the time of day.
   [gender-neutral language](https://en.wikipedia.org/wiki/Gender-neutral_language).
   For example, avoid using a pronoun like her or his in sentences like
   "Every developer should clean [their] keyboard at least once a week."
-* Follow the community [code of conduct](../code-of-conduct.md).
+* Follow the community [code of conduct](../code-of-conduct.html).
 * Participate!  Zulip is a friendly and welcoming community, and we
   love meeting new people, hearing about what brought them to Zulip,
   and getting their feedback.  If you're not sure where to start,

Diff for: docs/contributing/code-reviewing.md

@@ -78,7 +78,7 @@ this?". Good choices include
   up a page in the CI that has more details on why the job failed.
   For example [this](https://circleci.com/gh/zulip/zulip/16617)
   is the page of the `bionic-python-3.6` job. See our docs on
-  [continuous integration](../testing/continuous-integration.md)
+  [continuous integration](../testing/continuous-integration.html)
   to learn more.
 
 * *Technical design.* There are a lot of considerations here:
@@ -105,7 +105,7 @@ this?". Good choices include
   change being made.  Tests that exclude whole classes of potential
   bugs are preferred when possible (e.g., the common test suite
   `test_bugdown.py` between the Zulip server's [frontend and backend
-  Markdown processors](../subsystems/markdown.md), or the `GetEventsTest` test for
+  Markdown processors](../subsystems/markdown.html), or the `GetEventsTest` test for
   buggy race condition handling).
 
 * *Translation.* Make sure that the strings are marked for
@@ -194,11 +194,11 @@ We also strongly recommend reviewers to go through the following resources.
 * [Code Review - A consolidation of advice and stuff from the
    sinternet](https://gist.github.com/porterjamesj/002fb27dd70df003646df46f15e898de)
   article by James J. Porter
-* [Zulip Code of Conduct](../code-of-conduct.md)
-
-[code-style]: ../contributing/code-style.md
-[commit-messages]: ../contributing/version-control.md#commit-messages
-[test-writing]: ../testing/testing.md
-[mypy]: ../testing/mypy.md
-[git tool]: ../git/zulip-tools.md#fetch-a-pull-request-and-rebase
-[translation]: ../translating/translating.md
+* [Zulip Code of Conduct](../code-of-conduct.html)
+
+[code-style]: ../contributing/code-style.html
+[commit-messages]: ../contributing/version-control.html#commit-messages
+[test-writing]: ../testing/testing.html
+[mypy]: ../testing/mypy.html
+[git tool]: ../git/zulip-tools.html#fetch-a-pull-request-and-rebase
+[translation]: ../translating/translating.html

Diff for: docs/contributing/code-style.md

@@ -163,7 +163,7 @@ Don't use it:
 ### Translation tags
 
 Remember to
-[tag all user-facing strings for translation](../translating/translating.md), whether
+[tag all user-facing strings for translation](../translating/translating.html), whether
 they are in HTML templates or JavaScript editing the HTML (e.g. error
 messages).
 
@@ -292,5 +292,5 @@ All significant new features should come with tests. See testing.
 
 ### Third party code
 
-See [our docs on dependencies](../subsystems/dependencies.md) for discussion of
+See [our docs on dependencies](../subsystems/dependencies.html) for discussion of
 rules about integrating third-party projects.

Diff for: docs/development/overview.md

@@ -82,14 +82,14 @@ And if you've setup the Zulip development environment on a remote
 machine, take a look at our tips for
 [developing remotely][dev-remote].
 
-[dev-remote]: remote.md
-[install-direct]: ../development/setup-advanced.md#installing-directly-on-ubuntu-debian-centos-or-fedora
-[install-docker]: ../development/setup-advanced.md#using-docker-experimental
-[install-generic]: ../development/setup-advanced.md#installing-manually-on-linux
-[install-vagrant]: ../development/setup-vagrant.md
+[dev-remote]: remote.html
+[install-direct]: ../development/setup-advanced.html#installing-directly-on-ubuntu-debian-centos-or-fedora
+[install-docker]: ../development/setup-advanced.html#using-docker-experimental
+[install-generic]: ../development/setup-advanced.html#installing-manually-on-unix
+[install-vagrant]: ../development/setup-vagrant.html
 [self-install-remote]: #installing-remotely
 [self-slow-internet]: #slow-internet-connections
-[configure-proxy]: ../development/setup-vagrant.md#specifying-a-proxy
-[using-dev-env]: using.md
-[testing]: ../testing/testing.md
-[ci]: ../git/cloning.md#step-3-configure-continuous-integration-for-your-fork
+[configure-proxy]: ../development/setup-vagrant.html#specifying-a-proxy
+[using-dev-env]: using.html
+[testing]: ../testing/testing.html
+[ci]: ../git/cloning.html#step-3-configure-continuous-integration-for-your-fork

Diff for: docs/development/remote.md

@@ -129,7 +129,7 @@ don't have a favorite, here are some suggestions:
 * [spacemacs](https://github.com/syl20bnr/spacemacs)
 * [sublime](https://www.sublimetext.com/)
 
-Next, follow our [Git and GitHub Guide](../git/index.md) to clone and configure
+Next, follow our [Git and GitHub Guide](../git/index.html) to clone and configure
 your fork of zulip on your local computer.
 
 Once you have cloned your code locally, you can get to work.
@@ -214,12 +214,11 @@ Next, read the following to learn more about developing for Zulip:
 * [Using the Development Environment][rtd-using-dev-env]
 * [Testing][rtd-testing]
 
-[install-direct]: ../development/setup-advanced.md#installing-directly-on-ubuntu-debian-centos-or-fedora
-[install-generic]: ../development/setup-advanced.md#installing-manually-on-linux
-[install-vagrant]: ../development/setup-vagrant.md
-[rtd-git-guide]: ../git/index.md
-[rtd-using-dev-env]: using.md
-[rtd-testing]: ../testing/testing.md
+[install-direct]: ../development/setup-advanced.html#installing-directly-on-ubuntu-debian-centos-or-fedora
+[install-vagrant]: ../development/setup-vagrant.html
+[rtd-git-guide]: ../git/index.html
+[rtd-using-dev-env]: using.html
+[rtd-testing]: ../testing/testing.html
 [git-bash]: https://git-for-windows.github.io/
 [codeanywhere]: https://codeanywhere.com/
 [img-ca-settings]: ../images/codeanywhere-settings.png
@@ -237,7 +236,7 @@ that the user is `zulipdev`; edit accordingly if the situation is
 different.
 
 1. First, get an SSL certificate; you can use
-    [our certbot wrapper script used for production](../production/ssl-certificates.md#certbot-recommended)
+    [our certbot wrapper script used for production](../production/ssl-certificates.html#certbot-recommended)
     by running the following commands as root:
     ```
     # apt install -y crudini

Diff for: docs/development/request-remote.md

@@ -67,14 +67,14 @@ Once your remote dev instance is ready:
 
 Once you've confirmed you can connect to your remote server, take a look at:
 
-* [developing remotely](../development/remote.md) for tips on using the remote dev
+* [developing remotely](../development/remote.html) for tips on using the remote dev
   instance, and
-* our [Git & GitHub Guide](../git/index.md) to learn how to use Git with Zulip.
+* our [Git & GitHub Guide](../git/index.html) to learn how to use Git with Zulip.
 
 Next, read the following to learn more about developing for Zulip:
 
-* [Using the Development Environment](../development/using.md)
-* [Testing](../testing/testing.md)
+* [Using the Development Environment](../development/using.html)
+* [Testing](../testing/testing.html)
 
 [github-join]: https://github.com/join
 [github-help-add-ssh-key]: https://help.github.com/en/articles/adding-a-new-ssh-key-to-your-github-account

Diff for: docs/development/setup-advanced.md

@@ -21,9 +21,9 @@ that's running one of:
 You can just run the Zulip provision script on your machine.
 
 **Note**: you should not use the `root` user to run the installation.
-If you are using a [remote server](../development/remote.md), see
+If you are using a [remote server](../development/remote.html), see
 the
-[section on creating appropriate user accounts](../development/remote.md#setting-up-user-accounts).
+[section on creating appropriate user accounts](../development/remote.html#setting-up-user-accounts).
 
 **Warning**: there is no supported uninstallation process with this
 method.  If you want that, use the Vagrant environment, where you can
@@ -50,7 +50,7 @@ source /srv/zulip-py3-venv/bin/activate
 
 Once you've done the above setup, you can pick up the [documentation
 on using the Zulip development
-environment](../development/setup-vagrant.md#step-4-developing),
+environment](../development/setup-vagrant.html#step-4-developing),
 ignoring the parts about `vagrant` (since you're not using it).
 
 ## Installing manually on Unix
@@ -310,7 +310,7 @@ docker run -itv $(pwd):/srv/zulip -p 9991:9991 user/zulipdev:v2 \
 ```
 
 You'll want to
-[read the guide for Zulip development](../development/setup-vagrant.md#step-4-developing)
+[read the guide for Zulip development](../development/setup-vagrant.html#step-4-developing)
 to understand how to use the Zulip development.  Note that
 `start-dockers` automatically runs `tools/run-dev.py` inside the
 container; you can then visit http://localhost:9991 to connect to your
@@ -363,6 +363,6 @@ Currently, the Docker workflow is substantially less convenient than
 the Vagrant workflow and less documented; please contribute to this
 guide and the Docker tooling if you are using Docker to develop Zulip!
 
-[zulip-rtd-git-cloning]: ../git/cloning.md#step-1b-clone-to-your-machine
-[zulip-rtd-git-connect]: ../git/cloning.md#step-1c-connect-your-fork-to-zulip-upstream
-[port-forward-setup]: ../development/remote.md#running-the-development-server
+[zulip-rtd-git-cloning]: ../git/cloning.html#step-1b-clone-to-your-machine
+[zulip-rtd-git-connect]: ../git/cloning.html#step-1c-connect-your-fork-to-zulip-upstream
+[port-forward-setup]: ../development/remote.html#running-the-development-server

Diff for: docs/development/setup-vagrant.md

@@ -24,7 +24,7 @@ environment,** check
 [Troubleshooting and Common Errors](#troubleshooting-and-common-errors). If
 that doesn't help, please visit
 [#provision help](https://chat.zulip.org/#narrow/stream/21-provision-help)
-in the [Zulip development community server](../contributing/chat-zulip-org.md) for
+in the [Zulip development community server](../contributing/chat-zulip-org.html) for
 real-time help, send a note to the
 [Zulip-devel Google group](https://groups.google.com/forum/#!forum/zulip-devel)
 or [file an issue](https://github.com/zulip/zulip/issues).
@@ -285,8 +285,8 @@ projects and to instead follow these instructions exactly.)
 2. Open Terminal (macOS/Ubuntu) or Git BASH (Windows; must
    **run as an Administrator**).
 3. In Terminal/Git BASH,
-   [clone your fork of the Zulip repository](../git/cloning.md#step-1b-clone-to-your-machine) and
-   [connect the Zulip upstream repository](../git/cloning.md#step-1c-connect-your-fork-to-zulip-upstream):
+   [clone your fork of the Zulip repository](../git/cloning.html#step-1b-clone-to-your-machine) and
+   [connect the Zulip upstream repository](../git/cloning.html#step-1c-connect-your-fork-to-zulip-upstream):
 
 ```
 git clone --config pull.rebase [email protected]:YOURUSERNAME/zulip.git
@@ -340,7 +340,7 @@ does the following:
   downloads all required dependencies, sets up the python environment for
   the Zulip development server, and initializes a default test
   database.  We call this process "provisioning", and it is documented
-  in some detail in our [dependencies documentation](../subsystems/dependencies.md).
+  in some detail in our [dependencies documentation](../subsystems/dependencies.html).
 
 You will need an active internet connection during the entire
 process. (See [Specifying a proxy](#specifying-a-proxy) if you need a
@@ -352,7 +352,7 @@ documented in the
 [Troubleshooting and Common Errors](#troubleshooting-and-common-errors)
 section.  If that doesn't help, please visit
 [#provision help](https://chat.zulip.org/#narrow/stream/21-provision-help)
-in the [Zulip development community server](../contributing/chat-zulip-org.md) for
+in the [Zulip development community server](../contributing/chat-zulip-org.html) for
 real-time help.
 
 On Windows, you will see `The system cannot find the path specified.` message
@@ -489,7 +489,7 @@ It's good to have the terminal running `run-dev.py` up as you work since error
 messages including tracebacks along with every backend request will be printed
 there.
 
-See [Logging](../subsystems/logging.md) for further details on the run-dev.py console
+See [Logging](../subsystems/logging.html) for further details on the run-dev.py console
 output.
 
 #### Committing and pushing changes with git
@@ -518,7 +518,7 @@ After provisioning, you'll want to
 
 If you run into any trouble, the
 [#provision help](https://chat.zulip.org/#narrow/stream/21-provision-help)
-in the [Zulip development community server](../contributing/chat-zulip-org.md) for
+in the [Zulip development community server](../contributing/chat-zulip-org.html) for
 is a great place to ask for help.
 
 #### Rebuilding the development environment
@@ -615,7 +615,7 @@ If these solutions aren't working for you or you encounter an issue not
 documented below, there are a few ways to get further help:
 
 * Ask in [#provision help](https://chat.zulip.org/#narrow/stream/21-provision-help)
-  in the [Zulip development community server](../contributing/chat-zulip-org.md),
+  in the [Zulip development community server](../contributing/chat-zulip-org.html),
 * send a note to the [Zulip-devel Google
   group](https://groups.google.com/forum/#!forum/zulip-devel), or
 * [File an issue](https://github.com/zulip/zulip/issues).
@@ -883,7 +883,7 @@ Likely causes are:
 1. Networking issues
 2. Insufficient RAM. Check whether you've allotted at least two
 gigabytes of RAM, which is the minimum Zulip
-[requires](../development/setup-vagrant.md#requirements). If
+[requires](../development/setup-vagrant.html#requirements). If
 not, go to your VM settings and increase the RAM, then restart
 the VM.
 
@@ -967,7 +967,7 @@ Users who are unable to do "vagrant up" due to a VT-X unavailability error need
 
 #### Permissions errors when running the test suite in LXC
 
-See ["Possible testing issues"](../testing/testing.md#possible-testing-issues).
+See ["Possible testing issues"](../testing/testing.html#possible-testing-issues).
 
 #### Mounting NFS fails on macOS Mojave
 
@@ -1099,13 +1099,13 @@ for the IP address that means any IP address can connect to your development ser
 [vmware-fusion-dl]: http://www.vmware.com/products/fusion.html
 [vagrant-vmware-fusion-dl]: https://www.vagrantup.com/vmware/
 [avoiding-sudo]: https://github.com/fgrehm/vagrant-lxc#avoiding-sudo-passwords
-[install-advanced]: ../development/setup-advanced.md
+[install-advanced]: ../development/setup-advanced.html
 [lxc-sf]: https://github.com/fgrehm/vagrant-lxc/wiki/FAQ#help-my-shared-folders-have-the-wrong-owner
-[rtd-git-guide]: ../git/index.md
-[rtd-testing]: ../testing/testing.md
-[rtd-using-dev-env]: using.md
-[rtd-dev-remote]: remote.md
+[rtd-git-guide]: ../git/index.html
+[rtd-testing]: ../testing/testing.html
+[rtd-using-dev-env]: using.html
+[rtd-dev-remote]: remote.html
 [git-bash]: https://git-for-windows.github.io/
 [bash-admin-setup]: https://superuser.com/questions/1002262/run-applications-as-administrator-by-default-in-windows-10
-[set-up-git]: ../git/setup.md
-[ci]: ../git/cloning.md#step-3-configure-continuous-integration-for-your-fork
+[set-up-git]: ../git/setup.html
+[ci]: ../git/cloning.html#step-3-configure-continuous-integration-for-your-fork

Diff for: docs/development/using.md

@@ -51,5 +51,5 @@ restart if it crashes, and `upgrade-zulip` will take care of running
 migrations and then cleanly restaring the server for you).
 
 [django-runserver]: https://docs.djangoproject.com/en/1.8/ref/django-admin/#runserver-port-or-address-port
-[new-feature-tutorial]: ../tutorials/new-feature-tutorial.md
-[testing-docs]: ../testing/testing.md
+[new-feature-tutorial]: ../tutorials/new-feature-tutorial.html
+[testing-docs]: ../testing/testing.html

Diff for: docs/git/cheat-sheet.md

@@ -111,6 +111,6 @@ See also [fixing commits][fix-commit]
 - status
     - `git status`: show the working tree status, unstaged and staged files
 
-[fix-commit]: fixing-commits.md
-[git-config-clone]: cloning.md#step-1b-clone-to-your-machine
-[git-overview]: overview.md
+[fix-commit]: fixing-commits.html
+[git-config-clone]: cloning.html#step-1b-clone-to-your-machine
+[git-overview]: overview.html

Diff for: docs/git/cloning.md

@@ -152,6 +152,6 @@ Zulip.
 [travis-ci]: https://travis-ci.org/
 [circle-ci]:https://circleci.com/
 [travis-ci-profile]: https://travis-ci.org/profile
-[zulip-rtd-dev-first-time]: ../development/setup-vagrant.md
-[zulip-rtd-dev-overview]: ../development/overview.md
-[zulip-rtd-tools-setup]: ../git/zulip-tools.md#set-up-git-repo-script
+[zulip-rtd-dev-first-time]: ../development/setup-vagrant.html
+[zulip-rtd-dev-overview]: ../development/overview.html
+[zulip-rtd-tools-setup]: ../git/zulip-tools.html#set-up-git-repo-script

Diff for: docs/git/collaborate.md

@@ -54,4 +54,4 @@ tools/fetch-pull-request <PR-number>
 ```
 
 [github-help-co-pr-locally]: https://help.github.com/en/articles/checking-out-pull-requests-locally
-[tools-PR]: ../git/zulip-tools.md#fetch-a-pull-request-and-rebase
+[tools-PR]: ../git/zulip-tools.html#fetch-a-pull-request-and-rebase

Diff for: docs/git/overview.md

@@ -58,14 +58,14 @@ git workflow, or if you'd like a git refresher.
 [github-rebase-pr]: https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request
 [github-zulip]: https://github.com/zulip/
 [github-zulip-zulip]: https://github.com/zulip/zulip/
-[continuous-integration]: ../testing/continuous-integration.md
-[zulip-git-guide-fork-ci]: ../git/cloning.md#step-3-configure-continuous-integration-for-your-fork
-[zulip-rtd-code-style]: ../contributing/code-style.md
-[zulip-rtd-commit-discipline]: ../contributing/version-control.md#commit-discipline
-[zulip-rtd-commit-messages]: ../contributing/version-control.md#commit-messages
-[zulip-rtd-dev-overview]: ../development/overview.md
-[zulip-rtd-lint-tools]: ../contributing/code-style.md#lint-tools
-[zulip-rtd-mypy]: ../testing/mypy.md
-[zulip-rtd-testing]: ../testing/testing.md
-[zulip-rtd-zulip-tools]: ../git/zulip-tools.md
-[zulip-rtd-zulipbot-usage]: ../contributing/zulipbot-usage.md
+[continuous-integration]: ../testing/continuous-integration.html
+[zulip-git-guide-fork-ci]: ../git/cloning.html#step-3-configure-continuous-integration-for-your-fork
+[zulip-rtd-code-style]: ../contributing/code-style.html
+[zulip-rtd-commit-discipline]: ../contributing/version-control.html#commit-discipline
+[zulip-rtd-commit-messages]: ../contributing/version-control.html#commit-messages
+[zulip-rtd-dev-overview]: ../development/overview.html
+[zulip-rtd-lint-tools]: ../contributing/code-style.html#lint-tools
+[zulip-rtd-mypy]: ../testing/mypy.html
+[zulip-rtd-testing]: ../testing/testing.html
+[zulip-rtd-zulip-tools]: ../git/zulip-tools.html
+[zulip-rtd-zulipbot-usage]: ../contributing/zulipbot-usage.html

Diff for: docs/git/pull-requests.md

@@ -146,7 +146,7 @@ for another review.
 [github-help-about-pr]: https://help.github.com/en/articles/about-pull-requests
 [github-help-create-pr-fork]: https://help.github.com/en/articles/creating-a-pull-request-from-a-fork
 [images-create-pr]: ../images/zulip-open-pr.png
-[keep-up-to-date]: ../git/using.md#keep-your-fork-up-to-date
-[push-commits]: ../git/using.md#push-your-commits-to-github
-[screenshots-gifs]: ../tutorials/screenshot-and-gif-software.md
+[keep-up-to-date]: ../git/using.html#keep-your-fork-up-to-date
+[push-commits]: ../git/using.html#push-your-commits-to-github
+[screenshots-gifs]: ../tutorials/screenshot-and-gif-software.html
 [wip-prs]: #work-in-progress-pull-requests

Diff for: docs/git/reviewing.md

@@ -61,4 +61,4 @@ Display changes you've committed so far since creating a branch from upstream/ma
 $ git diff upstream/master...HEAD
 ```
 
-[zulip-rtd-review]: ../contributing/code-reviewing.md
+[zulip-rtd-review]: ../contributing/code-reviewing.html

Diff for: docs/git/setup.md

@@ -49,7 +49,7 @@ text-mode interface to Git.
 
 And, if none of the above are to your liking, try [one of these][gitbook-guis].
 
-[git-bash-admin]: ../development/setup-vagrant.md#running-git-bash-as-an-administrator
+[git-bash-admin]: ../development/setup-vagrant.html#running-git-bash-as-an-administrator
 [gitbook-aliases]: https://git-scm.com/book/en/v2/Git-Basics-Git-Aliases
 [gitbook-config]: https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration
 [gitbook-guis]: https://git-scm.com/downloads/guis