refactor(docs): point people to docs on website instead of .md docs

The docs on the website are prettier. Point people there instead of the uglier
.md files.

Author: strager

.github/workflows/build-and-test-dev.yml

@@ -7,7 +7,7 @@ on:
   pull_request:
     types: [opened, synchronize]
 
-# Based on docs/BUILDING.md.
+# Based on website/public/contribute/build-from-source/.
 jobs:
   build:
     name: ${{ matrix.toolchain.name }}
@@ -36,7 +36,7 @@ jobs:
       - name: 1. Configure with CMake
         run: |
           mkdir build ; cd build ; ${{ matrix.toolchain.extra_environment }} cmake -G Ninja -DCMAKE_BUILD_TYPE=Debug .. ; cd "$OLDPWD"
-          if ! [ -f docs/BUILDING.md ]; then
+          if ! [ -f docs/FUZZING.md ]; then
             printf 'error: cwd changed unexpectedly\n' >&2
             exit 1
           fi

.github/workflows/simple-build.yml

@@ -29,7 +29,7 @@ jobs:
         uses: actions/checkout@v2
 
       - name: build
-        # Keep in sync with "quick build" in docs/BUILDING.md.
+        # Keep in sync with "single-command build" in website/public/contribute/build-from-source/.
         run: '"${CXX}" ${CXXFLAGS} -o quick-lint-js -std=gnu++17 -I src -I vendor/boost -I vendor/simdjson/include -I vendor/simdjson/src -D_LIBCPP_HIDE_FROM_ABI_PER_TU_BY_DEFAULT=1 -D_LIBCPP_INLINE_VISIBILITY="__attribute__((internal_linkage))" src/quick-lint-js/*.cpp src/quick-lint-js/*/*.cpp vendor/boost/libs/container/src/*.cpp vendor/boost/libs/container/src/alloc_lib.c vendor/simdjson/src/simdjson.cpp -pthread'
 
 # quick-lint-js finds bugs in JavaScript programs.

README.md

@@ -16,8 +16,10 @@ quick-lint-js finds many bugs, including:
 See [installation instructions](https://quick-lint-js.com/install/) for how
 to install quick-lint-js' CLI, LSP server, and editor plugins.
 
-See [build instructions](docs/BUILDING.md) for how to build quick-lint-js for
-development.
+## Contributing
+
+If you want to make quick-lint-js better, see our
+[contributing guides](https://quick-lint-js.com/contribute/).
 
 ## Contact
 
@@ -29,25 +31,6 @@ development.
 **Security bug reports (private disclosure)**: email
 [[email protected]](mailto:[email protected])
 
-## Values
-
-* **Performance**. You use quick-lint-js in text editors and IDEs to show bugs
-  as they are written. quick-lint-js must be *fast* to make feedback *responsive*.
-  * **Small design**. The less infrastructure and developer conveniences used
-    within quick-lint-js, the less time quick-lint-js wastes due to this bloat.
-  * **Few features**. Features add run-time costs. With fewer features,
-    quick-lint-js gives you feedback sooner.
-
-* **High signal**. quick-lint-js finds bugs, not nitpicks. You can use
-  quick-lint-js in *any* project, no matter the size or style.
-  * **No opinions**. quick-lint-js doesn't complain about style issues, like
-    using `'strings'` vs `"strings"`. It complains about real bugs which
-    everyone agrees are bugs.
-  * **No false positives**. If quick-lint-js complains, you know it's a bug in
-    your code.
-  * **No configuration**. quick-lint-js works out-of-the-box. You don't need
-    configuration files to tell quick-lint-js what buggy code looks like.
-
 [Libera.Chat]: https://libera.chat/
 [quick-lint-js-irc-web]: https://kiwiirc.com/nextclient/irc.libera.chat/#quick-lint-js
 [quick-lint-js]: https://quick-lint-js.com/

benchmark/benchmark-lsp/README.md

@@ -21,7 +21,7 @@ Install the LSP servers you want to benchmark:
 
 Install a compiler which supports C++20 coroutines (such as Clang version 12).
 [Configure quick-lint-js using CMake with
-`-DQUICK_LINT_JS_ENABLE_BENCHMARKS=YES`](../../docs/BUILDING.md). Build the
+`-DQUICK_LINT_JS_ENABLE_BENCHMARKS=YES`][build-from-source]. Build the
 `quick-lint-js-benchmark-lsp-servers` target. For example, on Linux:
 
     $ mkdir build
@@ -121,4 +121,5 @@ Work (timed):
 
 [Deno]: https://deno.land/
 [Stack]: https://haskellstack.org/
+[build-from-source]: https://quick-lint-js.com/contribute/build-from-source/
 [install-rslint]: https://rslint.org/guide/