Harmonize capitalization between `pagination.md` and `configuration.md`.
Hugo normalizes site configuration keys to lowercase internally, so technically, capitalization doesn't really matter. But it's less confusing for newbies if the capitalization in the documentation is consistent.
The README.md states that the docs should "describe the current best practice" (as opposed to older ways).
This is the implementation of that principle.
* Clarify pagination documentation (#7609)
It is not necessary that the pages passed to .Paginate be a subset of .Pages.
Also, clarify that more than one call to .Paginator or .Paginate will give unexpected results.
* Correct a few statements based on review feedback
Closes#1161
I removed the paragraph related to Amazon S3 deployment from Wercker;
I was unable to find any documentation on the Wercker site. This is not
surprising. Wercker was acquired by Oracle in 2017, and I suspect Oracle
has little interest in promoting any of Amazon's services.
And we have taken great measures to limit potential site breakage:
* For `disableKinds` and `outputs` we try to map from old to new values if possible, if not we print an ERROR that can be toggled off if not relevant.
* The layout lookup is mostly compatible with more options for the new `term` kind.
That leaves:
* Where queries in site.Pages using taxonomy/taxonomyTerm Kind values as filter.
* Other places where these kind value are used in the templates (classes etc.)
Fixes#6911Fixes#7395
The document starts with "Hugo takes the parameters listed below into consideration when choosing a layout for a given page. They are listed in a priority order."
So it lists parameters from lower priority to higher priority.
But according to examples output format and language priority is higher than Layout priority.
It is quite confusing to read.
When `suffix = "<suffix>"` in the config.toml while adding or modifying
a media type, an error occurs: "MediaType.Suffix is removed. [...]".
I changed the code samples to use `suffixes` instead and adjusted the
surrounding descriptions to represent the change.
This commit adds the fast and CommonMark compliant Goldmark as the new default markdown handler in Hugo.
If you want to continue using BlackFriday as the default for md/markdown extensions, you can use this configuration:
```toml
[markup]
defaultMarkdownHandler="blackfriday"
```
Fixes#5963Fixes#1778Fixes#6355