diff --git a/content/about-hugo/benefits-of-static.md b/content/about-hugo/benefits-of-static.md index afe92db6a..46b8be366 100644 --- a/content/about-hugo/benefits-of-static.md +++ b/content/about-hugo/benefits-of-static.md @@ -28,9 +28,11 @@ Not running a website generator on your HTTP server has many benefits. The most * ["Static Site Generators", O-Reilly][] * [StaticGen: Top Open-Source Static Site Generators (GitHub Stars)][] * ["Top 10 Static Website Generators," Netlify blog][] +* ["Hugo vs. Wordpress page load speed comparison: Hugo leaves WordPress in its dust", GettingThingsTech][hugovwordpress] ["An Introduction to Static Site Generators", David Walsh]: https://davidwalsh.name/introduction-static-site-generators ["Static Site Generators", O-Reilly]: /documents/oreilly-static-site-generators.pdf ["Top 10 Static Website Generators," Netlify blog]: https://www.netlify.com/blog/2016/05/02/top-ten-static-website-generators/ +[hugovwordpress]: https://gettingthingstech.com/hugo-vs.-wordpress-page-load-speed-comparison-hugo-leaves-wordpress-in-its-dust/ [StaticGen: Top Open-Source Static Site Generators (GitHub Stars)]: https://www.staticgen.com/ diff --git a/content/about-hugo/license.md b/content/about-hugo/license.md index efb11bb9a..bfe695bb1 100644 --- a/content/about-hugo/license.md +++ b/content/about-hugo/license.md @@ -144,7 +144,7 @@ _END OF TERMS AND CONDITIONS_ To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets `[]` replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same “printed page” as the copyright notice for easier identification within third-party archives. -{{% input "apache-notice.txt" %}} +{{% input file="apache-notice.txt" %}} ``` Copyright [yyyy] [name of copyright owner] diff --git a/content/content-management/archetypes.md b/content/content-management/archetypes.md index b330a684e..cd2eb98e4 100644 --- a/content/content-management/archetypes.md +++ b/content/content-management/archetypes.md @@ -26,7 +26,7 @@ hugo new [content-section/file-name.md] We can use this pattern to create a new `.md` file in the `posts` section of the [example site][]: -{{% input "archetype-example.sh" %}} +{{% input file="archetype-example.sh" %}} ```bash hugo new posts/my-first-post.md ``` @@ -82,7 +82,7 @@ Default archetypes are convenient if your content's front matter stays consisten The [example site][] includes `tags` and `categories` as [taxonomies][]. If we assume that all content files will require these two key-values, we can create a `default.md` archetype that *extends* Hugo's base archetype. In this example, we are including "golang" and "hugo" as tags and "web development" as a category. -{{% input "archetypes/default.md" %}} +{{% input file="archetypes/default.md" %}} ```toml +++ tags = ["golang", "hugo"] @@ -99,7 +99,7 @@ If you get an `EOF error` when using `hugo new`, add a carriage return after the With an `archetypes/default.md` in place, we can use the CLI to create a new post in the `posts` content section: -{{% input "new-post-from-default.sh" %}} +{{% input file="new-post-from-default.sh" %}} ```bash $ hugo new posts/my-new-post.md ``` @@ -136,7 +136,7 @@ Suppose the example site's `posts` section requires more sophisticated front mat ### Creating a Custom Archetype -{{% input "archetypes/posts.md"%}} +{{% input file="archetypes/posts.md"%}} ```toml +++ description = "" @@ -150,7 +150,7 @@ categories = "" With an `archetypes/posts.md` in place, we can use the CLI to create a new posts with custom `posts` metadata in the `posts` content section: -{{% input "new-post-from-custom.sh" %}} +{{% input file="new-post-from-custom.sh" %}} ```bash $ hugo new posts/post-from-custom.md ``` diff --git a/content/content-management/comments.md b/content/content-management/comments.md index 831ef9008..962b378c1 100644 --- a/content/content-management/comments.md +++ b/content/content-management/comments.md @@ -56,7 +56,7 @@ You also have the option to set the following in the front matter for a given pi Users have noticed that enabling Disqus comments when running the Hugo web server on `localhost` (i.e. via `hugo server`) causes the creation of unwanted discussions on the associated Disqus account. In order to prevent this, a slightly tweaked partial template is required. So, rather than using the built-in `"_internal/disqus.html"` template referenced above, create a template in `layouts/partials` that looks like the following: -{{% input "layouts/partials/disqus.html" %}} +{{% input file="layouts/partials/disqus.html" %}} ```html