There are 2 different kind of resource, one that is attached
to the page, matching all non-rendered files, and the global
one matching all files in `/assets`. Although they have similar
behaviour, the way to access both of them are slightly different.
Explicitly express differences between both and clarify when a page
is attached resources and when not.
The phrase "Instead of set field on all pages, you can set field on required pages only." seems to be grammatically incorrect.
I have changed it to: "Instead of setting a field on all pages, you can set that field on required pages only."
**Digital.gov** helps people in government deliver better, more accessible digital services through publishing essential guidance, resources, tools, and online events that make it easier for people to design, build, and deliver essential services for the public.
Add a new pipe called TranspileJS which uses the Babel cli. This makes it possible for users to write ES6 JavaScript code and transpile it to ES5 during website generation so that the code still works with older browser versions.
Fixes#5764
* Mentioning a range is equivelant to foreach
I’m new to Go and really struggled to find this. I added this sentence so it would be searchable for other people to find. At the moment, searching for a foreach doesn’t return range and IMHO it should.
* Fixed a spelling error for equivalent
Additional build options for listing pages were introduced in v0.68. Original commit (99958f9) added a note to docs mentioning version 0.58. This change corrects the version.
The link "[wherefunction]" was not defined, so the square brackets where visible on the rendered page.
It seems that this link would have just gone back to the top of the page, so I removed it instead of fixing it.
