We still have go-toml as a transitive dependency, and it is the way to go eventually, but we care about speed, so let us wait that one out.
Note that the issue this fixes is about taxonomies, but I guess this is a general issue for sites with many pages that uses TOML as front matter.
```
benchmark old ns/op new ns/op delta
BenchmarkFrontmatterTags/TOML:1-4 23206 8543 -63.19%
BenchmarkFrontmatterTags/TOML:11-4 80117 18495 -76.92%
BenchmarkFrontmatterTags/TOML:21-4 140676 28727 -79.58%
benchmark old allocs new allocs delta
BenchmarkFrontmatterTags/TOML:1-4 173 60 -65.32%
BenchmarkFrontmatterTags/TOML:11-4 625 138 -77.92%
BenchmarkFrontmatterTags/TOML:21-4 1106 210 -81.01%
benchmark old bytes new bytes delta
BenchmarkFrontmatterTags/TOML:1-4 9231 2912 -68.45%
BenchmarkFrontmatterTags/TOML:11-4 19808 5184 -73.83%
BenchmarkFrontmatterTags/TOML:21-4 31200 7536 -75.85%
```
See #3541
Updates #3464
So you can do and get:
```
▶ ./benchSite.sh "YAML,num_pages=10"
Running with BenchmarkSiteBuilding/YAML,num_pages=10
BenchmarkSiteBuilding/YAML,num_pages=10-4 1000 1611261 ns/op 730749 B/op 6458 allocs/op
PASS
ok github.com/spf13/hugo/hugolib 8.168s
```
And change site benchmark separator to comma to make it Bash and regexp friendly, example:
./benchSite.sh "frontmatter=YAML,num_root_sections=1,num_pages=.*,tags_per_page=20,shortcodes=false,render=false"
To run a subset of these benchmark, one can do something like this:
```
go test -run="NONE" -bench="BenchmarkSiteBuilding/tags_per_page=0.*shortcodes=true.*render=false" -test.benchmem=true ./hugolib
```
Which will run without any tags, with shortcodes, but will skip rendering.
Fixes#3535
* Add news content
* Switch to new home page
* Move docs home page to a new page
* Switch to home page content
* Adjust global menu: remove showcase
* Remove unneeded portion of the front matter
* Remove old theme
* Update content for new theme
* Fix content to new theme
* Move layouts into theme
* Move classes to config
* [WIP] theme
* [WIP] inline critical CSS
* Add some notes on the [WIP] critical CSS feature
* Make theme changes for themes site
* Import theme updates from themes site
* [WIP] theme prev/next links
* Revert critical CSS tests
Didn't move the needle on a 20kb (gzipped) stylesheet.
First view speed index is 1008 without CSS.
* Not using docsnav data file
* Backdate these articles so we keep them but they don't show up on top
* Change Twitter handle to work with Hugo's internal templates
plus a few minor clean-ups
* Update theme (change Twitter handle in Follow link)
See PR rdwatters/hugo-docs-concept#120
Assets like screenshots are used in content files such as
tutorials. This commit moves these assets out of the theme
into the static folder in the root directory.
This way the theme and content files become independent from
each other.
See PR rdwatters/hugo-docs-concept#123
