chore: update README

Author: hegemonic

README.md

@@ -1,56 +1,55 @@
-This repository contains the user documentation for [JSDoc 3][jsdoc]. Use this repository to report
+This repository contains the user documentation for [JSDoc][jsdoc]. Use this repository to report
 documentation bugs, and to submit pull requests for improving the docs.
 
 If you just want to read the documentation, please visit [Use JSDoc][use-jsdoc].
 
-
 ## Contributing to the documentation
 
-The HTML docs are generated with [Metalsmith][] and [Gulp][]. If you'd like to contribute to the
-docs, make sure Node.js and npm are installed, then follow these steps:
-
-1. Clone this repository:
-
-        git@github.com:jsdoc3/jsdoc3.github.com.git
+The HTML docs are generated with [Eleventy][eleventy]. If you'd like to contribute to the docs, make
+sure Node.js and npm are installed, then follow these steps:
 
-2. Install Bower and Gulp globally:
+1.  Clone this repository:
 
-        npm install -g gulp
-        npm install -g bower
+    ```
+    git clone https://github.com/jsdoc/jsdoc.github.io
+    ```
 
-3. Install the dependencies:
+2.  Install dependencies:
 
-        npm install
-        bower install
+    ```
+    npm install
+    ```
 
-4. Make your changes in the `content` directory, which contains the source files for the docs.
+3.  Make your changes in the `content` directory, which contains the source files for the docs.
 
     The first few lines of each source file contain [YAML][] front matter, which is metadata in
     [YAML][] format. If you need to use the character `@` or `[` at the start of a YAML value, you
     can escape it with a backslash. For example, write `title: @class` as `title: \@class`.
 
-5. Rebuild the HTML files:
+4.  Rebuild the HTML files, and run a local server so that you can review them:
 
-        gulp
+    ```
+    npm run serve
+    ```
 
-6. Review the updated HTML files, and make sure your changes look okay. In particular, if you edited
-the YAML front matter, make sure your changes are reflected in the generated HTML files.
 
-7. Submit a pull request with your changes.
+5.  Review the updated HTML files on the local server, and make sure your changes look okay. In
+    particular, if you edited the YAML front matter, make sure your changes are reflected in the
+    generated HTML files.
 
+6.  Send a pull request with your changes.
 
 ## Legal stuff
 
-Copyright (c) 2011-2014 by Michael Mathews and the JSDoc 3 documentation [contributors][].
+Copyright 2011 by the [contributors][] to the JSDoc documentation.
 
 This repository is licensed under the [Creative Commons Attribution-ShareAlike 3.0 Unported][cc]
 license. A copy of the license is included in the [`LICENSE` file][license].
 
 [cc]: https://creativecommons.org/licenses/by-sa/3.0/legalcode
 [contributors]: https://github.com/jsdoc/jsdoc.github.io/graphs/contributors
-[Gulp]: https://gulpjs.com/
+[eleventy]: https://www.11ty.dev/
 [jsdoc]: https://github.com/jsdoc/jsdoc
 [license]: https://github.com/jsdoc/jsdoc.github.io/LICENSE
-[Metalsmith]: https://www.metalsmith.io/
 [use-jsdoc]: https://jsdoc.app/
-[YAML]: https://www.yaml.org/spec/1.2/spec.html
+[YAML]: https://yaml.org/spec/1.2.2/