refactor: build site with Eleventy

Author: hegemonic

.editorconfig

@@ -0,0 +1,8 @@
+[*]
+charset = utf-8
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[{**/*.cjs, **/*.css,**/*.js,*.json,**/*.less,**/*.mjs,**/*.njk,**/*.scss,**/*.yaml}]
+indent_style = space
+indent_size = 2

.eslintrc.cjs renamed to .eslintrc.js

@@ -6,6 +6,7 @@ node_modules
 .coverage/
 .parcel-cache/
 .vscode/
+_site/
 coverage/
 
 # Dotfile detritus

.gitignore

@@ -1,6 +1,6 @@
 ---
 title: Block and inline tags
-description: Overview of block and inline JSDoc tags.
+tags: gettingStarted
 ---
 
 ## Overview
@@ -30,7 +30,7 @@ Most JSDoc tags are block tags. In general, when this site refers to "JSDoc tags
 
 In the following example, `@param` is a block tag, and `{@link}` is an inline tag:
 
-{% example "Block and inline tags in JSDoc comments" %}
+::: example "Block and inline tags in JSDoc comments"
 
 ```js
 /**
@@ -42,11 +42,11 @@ Shoe.prototype.setColor = function(color) {
     // ...
 };
 ```
-{% endexample %}
+:::
 
 You can use inline tags within a description, as shown above, or within a block tag, as shown below:
 
-{% example "Inline tag used within a block tag" %}
+::: example "Inline tag used within a block tag"
 
 ```js
 /**
@@ -59,11 +59,11 @@ Shoe.prototype.setColor = function(color) {
     // ...
 };
 ```
-{% endexample %}
+:::
 
 When you use multiple block tags in a JSDoc comment, they must be separated by line breaks:
 
-{% example "Multiple block tags separated by line breaks" %}
+::: example "Multiple block tags separated by line breaks"
 
 ```js
 /**
@@ -76,4 +76,4 @@ Shoe.prototype.setLaceType = function(color, type) {
     // ...
 };
 ```
-{% endexample %}
+:::

.prettierrc.cjs renamed to .prettierrc.js

@@ -1,8 +1,8 @@
 ---
 title: Command-line arguments to JSDoc
-description: About command-line arguments to JSDoc.
+tags: gettingStarted
 related:
-    - about-configuring-jsdoc.html
+    - /about-configuring-jsdoc
 ---
 
 At its most basic level, JSDoc is used like so:
@@ -43,30 +43,30 @@ Option|Description
 `-X`, `--explain`|Dump all doclets to the console in JSON format, then exit.
 
 
-[config-file]: about-configuring-jsdoc.html
-[including-readme]: about-including-readme.html
-[md-file]: http://daringfireball.net/projects/markdown/
-[private-tag]: tags-private.html
-[tutorials]: about-tutorials.html
+[config-file]: /about-configuring-jsdoc
+[including-readme]: /about-including-readme
+[md-file]: https://daringfireball.net/projects/markdown/
+[private-tag]: /tags-private
+[tutorials]: /about-tutorials
 
 
 ## Examples
 
 Generate documentation for files in the `./src` directory, using the configuration file
 `/path/to/my/conf.json`, and save the output in the `./docs` directory:
 
-{% example %}
+::: example
 
 ```
 /path/to/jsdoc src -r -c /path/to/my/conf.json -d docs
 ```
-{% endexample %}
+:::
 
 Run all JSDoc tests whose names include the word `tag`, and log information about each test:
 
-{% example %}
+::: example
 
 ```
 /path/to/jsdoc -T --match tag --verbose
 ```
-{% endexample %}
+:::

content/en/about-block-inline-tags.md renamed to content/about-block-inline-tags.md

@@ -1,8 +1,8 @@
 ---
 title: Configuring JSDoc's default template
-description: How to configure the output from JSDoc's default template.
+tags: gettingStarted
 related:
-    - about-configuring-jsdoc.html
+    - /about-configuring-jsdoc
 ---
 
 JSDoc's default template provides several options that you can use to customize the appearance and
@@ -11,7 +11,7 @@ content of generated documentation.
 To use these options, you must [create a configuration file][about-config] for JSDoc and set the
 appropriate options in the configuration file.
 
-[about-config]: about-configuring-jsdoc.html
+[about-config]: /about-configuring-jsdoc
 
 
 ## Generating pretty-printed source files
@@ -42,7 +42,7 @@ copy. If this property is not defined, all files will be copied.
 + `templates.default.staticFiles.excludePattern`: A regular expression indicating which files to
 skip. If this property is not defined, nothing will be skipped.
 
-{% example "Copying a directory of images to the output directory" %}
+::: example "Copying a directory of images to the output directory"
 
 To copy all of the static files in `./myproject/static` to the output directory:
 
@@ -63,7 +63,7 @@ To copy all of the static files in `./myproject/static` to the output directory:
 If your static files directory contains the file `./myproject/static/img/screen.png`, you can
 display the image in your docs by using the HTML tag `<img src="img/screen.png">`.
 
-{% endexample %}
+:::
 
 
 ## Showing the current date in the page footer