https://v0-122-0--gohugoio.netlify.app/categories/fundamentals/Recent content in fundamentals on HugoHugo -- gohugo.ioenhttps://v0-122-0--gohugoio.netlify.app/content-management/organization/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/organization/Page bundles Hugo 0.32 announced page-relative images and other resources packaged into Page Bundles. These terms are connected, and you also need to read about Page Resources and Image Processing to get the full picture. The illustration shows three bundles. Note that the home page bundle cannot contain other content pages, although other files (images etc.) are allowed. The bundle documentation is a work in progress. We will publish more comprehensive docs about this soon.https://v0-122-0--gohugoio.netlify.app/templates/introduction/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/templates/introduction/The following is only a primer on Go Templates. For an in-depth look into Go Templates, check the official Go docs. Go Templates provide an extremely simple template language that adheres to the belief that only the most basic of logic belongs in the template or view layer. Basic syntax Go Templates are HTML files with the addition of variables and functions. Go Template variables and functions are accessible within {{ }}.https://v0-122-0--gohugoio.netlify.app/getting-started/directory-structure/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/getting-started/directory-structure/Site skeleton Hugo generates a project skeleton when you create a new site. For example, this command: hugo new site my-site Creates this directory structure: my-site/ ├── archetypes/ │ └── default.md ├── assets/ ├── content/ ├── data/ ├── i18n/ ├── layouts/ ├── static/ ├── themes/ └── hugo.toml <-- site configuration Depending on requirements, you may wish to organize your site configuration into subdirectories: my-site/ ├── archetypes/ │ └── default.md ├── assets/ ├── config/ <-- site configuration │ └── _default/ │ └── hugo.https://v0-122-0--gohugoio.netlify.app/templates/lookup-order/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/templates/lookup-order/Lookup rules Hugo takes the parameters listed below into consideration when choosing a template for a given page. The templates are ordered by specificity. This should feel natural, but look at the table below for concrete examples of the different parameter variations. Kind The page Kind (the home page is one). See the example tables below per kind. This also determines if it is a single page (i.e. a regular content page.https://v0-122-0--gohugoio.netlify.app/templates/base/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/templates/base/The block keyword allows you to define the outer shell of your pages’ one or more master template(s) and then fill in or override portions as necessary. Base template lookup order The base template lookup order closely follows that of the template it applies to (e.g. _default/list.html). See Template Lookup Order for details and examples. Define the base template The following defines a simple base template at _default/baseof.html. As a default template, it is the shell from which all your pages will be rendered unless you specify another *baseof.https://v0-122-0--gohugoio.netlify.app/getting-started/configuration/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/getting-started/configuration/Configuration file Create a site configuration file in the root of your project directory, naming it hugo.toml, hugo.yaml, or hugo.json, with that order of precedence. my-project/ └── hugo.toml With v0.109.0 and earlier the basename of the site configuration file was config instead of hugo. You can use either, but should transition to the new naming convention when practical. A simple example: hugo. yaml   toml   json   baseURL: https://example.org/ languageCode: en-us params: contact: email: info@example.https://v0-122-0--gohugoio.netlify.app/getting-started/configuration-markup/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/getting-started/configuration-markup/Default handler By default, Hugo uses Goldmark to render markdown to HTML. hugo. yaml   toml   json   markup: defaultMarkdownHandler: goldmark [markup] defaultMarkdownHandler = 'goldmark' { "markup": { "defaultMarkdownHandler": "goldmark" } } Files with the .md or .markdown extension are processed as markdown, provided that you have not specified a different content format using the markup field in front matter. To use a different renderer for markdown files, specify one of asciidocext, org, pandoc, or rst in your site configuration.https://v0-122-0--gohugoio.netlify.app/content-management/build-options/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/build-options/Build options are stored in a reserved front matter object named _build with these defaults: content/example/index.md yaml   toml   json   --- _build: list: always publishResources: true render: always --- +++ [_build] list = 'always' publishResources = true render = 'always' +++ { "_build": { "list": "always", "publishResources": true, "render": "always" } } list When to include the page within page collections. Specify one of: always Include the page in all page collections.https://v0-122-0--gohugoio.netlify.app/content-management/image-processing/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/image-processing/Image resources To process an image you must access the file as a page resource, global resource, or remote resource. Page resource A page resource is a file within a page bundle. A page bundle is a directory with an index.md or _index.md file at its root. content/ └── posts/ └── post-1/ <-- page bundle ├── index.md └── sunset.jpg <-- page resource To access an image as a page resource:https://v0-122-0--gohugoio.netlify.app/templates/output-formats/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/templates/output-formats/This page describes how to properly configure your site with the media types and output formats, as well as where to create your templates for your custom outputs. Media types A media type (formerly known as a MIME type) is a two-part identifier for file formats and format contents transmitted on the internet. This is the full set of built-in media types in Hugo: Type suffixes application/json [json] application/manifest+json [webmanifest] application/octet-stream [webmanifest] application/pdf [pdf] application/rss+xml [xml rss] application/toml [toml] application/wasm [wasm] application/xml [xml] application/yaml [yaml yml] font/otf [otf] font/ttf [ttf] image/bmp [bmp] image/gif [gif] image/jpeg [jpg jpeg jpe jif jfif] image/png [png] image/svg+xml [svg] image/tiff [tif tiff] image/webp [webp] text/calendar [ics] text/css [css] text/csv [csv] text/html [html] text/javascript [js jsm mjs] text/jsx [jsx] text/markdown [md markdown] text/plain [txt] text/tsx [tsx] text/typescript [ts] text/x-sass [sass] text/x-scss [scss] video/3gpp [3gpp 3gp] video/mp4 [mp4] video/mpeg [mpg mpeg] video/ogg [ogv] video/webm [webm] video/x-msvideo [avi] Note: