remove .md

website/src/docs/contributing.md

@@ -86,16 +86,16 @@ by using `task website` (requires `nodejs` & `yarn`). All content is written in
 directory. All Markdown documents should have an 80 character line wrap limit
 (enforced by Prettier).
 
-When making a change, consider whether a change to the [Usage Guide](/usage.md)
+When making a change, consider whether a change to the [Usage Guide](/usage)
 is necessary. This document contains descriptions and examples of how to use
 Task features. If you're adding a new feature, try to find an appropriate place
 to add a new section. If you're updating an existing feature, ensure that the
 documentation and any examples are up-to-date. Ensure that any examples follow
-the [Taskfile Styleguide](/styleguide.md).
+the [Taskfile Styleguide](/styleguide).
 
 If you added a new command or flag, ensure that you add it to the
-[CLI Reference](/reference/cli.md). New fields also need to be added to the
-[Schema Reference](/reference/schema.md) and [JSON Schema][json-schema]. The
+[CLI Reference](/reference/cli). New fields also need to be added to the
+[Schema Reference](/reference/schema) and [JSON Schema][json-schema]. The
 descriptions for fields in the docs and the schema should match.
 
 ### Writing tests
@@ -148,7 +148,7 @@ contributions.
 
 All kinds of contributions are welcome, whether its a typo fix or a shiny new
 feature. You can also contribute by upvoting/commenting on issues, helping to
-answer questions or contributing to other [community projects](/community.md).
+answer questions or contributing to other [community projects](/community).
 
 > I'm stuck, where can I get help?
 

website/src/docs/faq.md

@@ -27,7 +27,7 @@ be patient and avoid asking for ETAs.
 
 The best way to speed things up is to contribute to the project yourself. We
 always appreciate new contributors. If you are interested in contributing, check
-out the [contributing guide](/contributing.md).
+out the [contributing guide](/contributing).
 
 ## Why won't my task update my shell environment?
 

website/src/docs/getting-started.md

@@ -9,7 +9,7 @@ outline: deep
 The following guide will help introduce you to the basics of Task. We'll cover
 how to create a Taskfile, how to write a basic task and how to call it. If you
 haven't installed Task yet, head over to our
-[installation guide](installation.md).
+[installation guide](installation).
 
 ## Creating your first Taskfile
 
@@ -72,7 +72,7 @@ task default
 
 Note that we don't have to specify the name of the Taskfile. Task will
 automatically look for a file called `Taskfile.yml` (or any of Task's
-[supported file names](usage.md#supported-file-names)) in the current directory.
+[supported file names](usage#supported-file-names)) in the current directory.
 Additionally, tasks with the name `default` are special. They can also be run
 without specifying the task name.
 
@@ -130,5 +130,5 @@ task build
 That's about it for the basics, but there's _so much_ more that you can do with
 Task. Check out the rest of the documentation to learn more about all the
 features Task has to offer! We recommend taking a look at the
-[usage guide](usage.md) next. Alternatively, you can check out our reference
-docs for the [Taskfile schema](reference/schema.md) and [CLI](reference/cli.md).
+[usage guide](usage) next. Alternatively, you can check out our reference
+docs for the [Taskfile schema](reference/schema) and [CLI](reference/cli).

website/src/docs/usage.md

@@ -902,7 +902,7 @@ You can use `--force` or `-f` if you want to force a task to run even when
 up-to-date.
 
 Also, `task --status [tasks]...` will exit with a non-zero
-[exit code](/reference/cli.md#exit-codes) if any of the tasks are not
+[exit code](/reference/cli#exit-codes) if any of the tasks are not
 up-to-date.
 
 `status` can be combined with the
@@ -2389,4 +2389,4 @@ to us.
 :::
 
 [gotemplate]: https://golang.org/pkg/text/template/
-[templating-reference]: /reference/templating.md
+[templating-reference]: /reference/templating