https://v0-122-0--gohugoio.netlify.app/categories/content-management/Recent content in content management 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/content-management/page-bundles/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/page-bundles/Page Bundles are a way to group Page Resources. A Page Bundle can be one of: Leaf Bundle (leaf means it has no children) Branch Bundle (home page, section, taxonomy terms, taxonomy list) Leaf Bundle Branch Bundle Usage Collection of content and attachments for single pages Collection of attachments for section pages (home page, section, taxonomy terms, taxonomy list) Index file name index.md 1 _index.md 1 Allowed Resources Page and non-page (like images, PDF, etc.https://v0-122-0--gohugoio.netlify.app/content-management/formats/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/formats/You can put any file type into your /content directories, but Hugo uses the markup front matter value if set or the file extension (see Markup identifiers in the table below) to determine if the markup needs to be processed, e.g.: Markdown converted to HTML Shortcodes processed Layout applied List of content formats The current list of content formats in Hugo: Name Markup identifiers Comment Goldmark markdown, goldmark Note that you can set the default handler of md and markdown to something else, see Configure Markup.https://v0-122-0--gohugoio.netlify.app/content-management/diagrams/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/diagrams/New in v0.93.0 GoAT diagrams (ASCII) Hugo supports GoAT natively. This means that this code block: ```goat . . . .--- 1 .-- 1 / 1 / \ | | .---+ .-+ + / \ .---+---. .--+--. | '--- 2 | '-- 2 / \ 2 + + | | | | ---+ ---+ + / \ / \ .-+-. .-+-. .+. .+. | .--- 3 | .-- 3 \ / 3 / \ / \ | | | | | | | | '---+ '-+ + 1 2 3 4 1 2 3 4 1 2 3 4 '--- 4 '-- 4 \ 4 ``` Will be rendered as:https://v0-122-0--gohugoio.netlify.app/content-management/front-matter/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/front-matter/Front matter allows you to keep metadata attached to an instance of a content type—i.e., embedded inside a content file—and is one of the many features that gives Hugo its strength. Front matter formats Hugo supports four formats for front matter, each with their own identifying tokens. TOML identified by opening and closing +++. YAML identified by opening and closing ---. JSON a single JSON object surrounded by ‘{’ and ‘}’, followed by a new line.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/page-resources/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/page-resources/Page resources are only accessible from page bundles, those directories with index.md or _index.md files at their root. Page resources are only available to the page with which they are bundled. In this example, first-post is a page bundle with access to 10 page resources including audio, data, documents, images, and video. Although second-post is also a page bundle, it has no page resources and is unable to directly access the page resources associated with first-post.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/content-management/shortcodes/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/shortcodes/What a shortcode is Hugo loves Markdown because of its simple content format, but there are times when Markdown falls short. Often, content authors are forced to add raw HTML (e.g., video <iframe>’s) to Markdown content. We think this contradicts the beautiful simplicity of Markdown’s syntax. Hugo created shortcodes to circumvent these limitations. A shortcode is a simple snippet inside a content file that Hugo will render using a predefined template.https://v0-122-0--gohugoio.netlify.app/content-management/related/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/related/Hugo uses a set of factors to identify a page’s related content based on front matter parameters. This can be tuned to the desired set of indices and parameters or left to Hugo’s default Related Content configuration. List related content To list up to 5 related pages (which share the same date or keyword parameters) is as simple as including something similar to this partial in your single page template:https://v0-122-0--gohugoio.netlify.app/content-management/sections/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/sections/Overview A section is a top-level content directory, or any content directory with an _index.md file. A content directory with an _index.md file is also known as a branch bundle. Section templates receive one or more page collections in context. Although top-level directories without _index.md files are sections, we recommend creating _index.md files in all sections. A typical site consists of one or more sections. For example: content/ ├── articles/ <-- section (top-level directory) │ ├── 2022/ │ │ ├── article-1/ │ │ │ ├── cover.https://v0-122-0--gohugoio.netlify.app/content-management/types/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/types/A content type is a way to organize your content. Hugo resolves the content type from either the type in front matter or, if not set, the first directory in the file path. E.g. content/blog/my-first-event.md will be of type blog if no type is set. A content type is used to Determine how the content is rendered. See Template Lookup Order and Content Views for more. Determine which archetype template to use for new content.https://v0-122-0--gohugoio.netlify.app/content-management/archetypes/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/archetypes/Overview A content file consists of front matter and markup. The markup is typically markdown, but Hugo also supports other content formats. Front matter can be TOML, YAML, or JSON. The hugo new content command creates a new file in the content directory, using an archetype as a template. This is the default archetype: archetypes/default.md yaml   toml   json   --- date: '{{ .Date }}' draft: true title: '{{ replace .https://v0-122-0--gohugoio.netlify.app/content-management/taxonomies/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/taxonomies/What is a taxonomy? Hugo includes support for user-defined groupings of content called taxonomies. Taxonomies are classifications of logical relationships between content. Definitions Taxonomy a categorization that can be used to classify content Term a key within the taxonomy Value a piece of content assigned to a term Example taxonomy: movie website Let’s assume you are making a website about movies. You may want to include the following taxonomies: Actors Directors Studios Genre Year Awards Then, in each of the movies, you would specify terms for each of these taxonomies (i.https://v0-122-0--gohugoio.netlify.app/content-management/summaries/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/summaries/https://v0-122-0--gohugoio.netlify.app/content-management/cross-references/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/cross-references/The ref and relref shortcodes display the absolute and relative permalinks to a document, respectively. Use of ref and relref The ref and relref shortcodes require a single parameter: the path to a content document, with or without a file extension, with or without an anchor. Paths without a leading / are first resolved relative to the current page, then to the remainder of the site. . └── content ├── about | ├── _index.https://v0-122-0--gohugoio.netlify.app/content-management/urls/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/urls/Overview By default, when Hugo renders a page, the resulting URL matches the file path within the content directory. For example: content/posts/post-1.md → https://example.org/posts/post-1/ You can change the structure and appearance of URLs with front matter values and site configuration options. Front matter slug Set the slug in front matter to override the last segment of the path. The slug value does not affect section pages. content/posts/post-1.md yaml   toml   json   --- slug: my-first-post title: My First Post --- +++ slug = 'my-first-post' title = 'My First Post' +++ { "slug": "my-first-post", "title": "My First Post" } The resulting URL will be:https://v0-122-0--gohugoio.netlify.app/content-management/menus/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/menus/Overview To create a menu for your site: Define the menu entries Localize each entry Render the menu with a template Create multiple menus, either flat or nested. For example, create a main menu for the header, and a separate menu for the footer. There are three ways to define menu entries: Automatically In front matter In site configuration Although you can use these methods in combination when defining a menu, the menu will be easier to conceptualize and maintain if you use one method throughout the site.https://v0-122-0--gohugoio.netlify.app/content-management/static-files/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/static-files/By default, the static/ directory in the site project is used for all static files (e.g. stylesheets, JavaScript, images). The static files are served on the site root path (eg. if you have the file static/image.png you can access it using http://{server-url}/image.png, to include it in a document you can use  ). Hugo can be configured to look into a different directory, or even multiple directories for such static files by configuring the staticDir parameter in the site configuration.https://v0-122-0--gohugoio.netlify.app/content-management/toc/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/toc/Previously, there was no out-of-the-box way to specify which heading levels you want the TOC to render. See the related GitHub discussion (#1778). As such, the resulting <nav id="TableOfContents"><ul></ul></nav> was going to start at <h1> when pulling from {{ .Content }}. Hugo v0.60.0 made a switch to Goldmark as the default library for Markdown which has improved and configurable implementation of TOC. Take a look at how to configure TOC for Goldmark renderer.https://v0-122-0--gohugoio.netlify.app/content-management/comments/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/comments/Hugo ships with support for Disqus, a third-party service that provides comment and community capabilities to websites via JavaScript. Your theme may already support Disqus, but if not, it is easy to add to your templates via Hugo’s built-in Disqus partial. Add Disqus Hugo comes with all the code you need to load Disqus into your templates. Before adding Disqus to your site, you’ll need to set up an account.https://v0-122-0--gohugoio.netlify.app/content-management/multilingual/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/multilingual/You should define the available languages in a languages section in your site configuration. Also See Hugo Multilingual Part 1: Content translation. Configure languages This is the default language configuration: hugo. yaml   toml   json   languages: en: disabled: false languageCode: "" languageDirection: "" languageName: "" title: "" weight: 0 [languages] [languages.en] disabled = false languageCode = '' languageDirection = '' languageName = '' title = '' weight = 0 { "languages": { "en": { "disabled": false, "languageCode": "", "languageDirection": "", "languageName": "", "title": "", "weight": 0 } } } This is an example of a site configuration for a multilingual project.https://v0-122-0--gohugoio.netlify.app/content-management/syntax-highlighting/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/syntax-highlighting/Hugo uses Chroma as its code highlighter; it is built in Go and is really, really fast. Configure syntax highlighter See Configure Highlight. Generate syntax highlighter CSS If you run with markup.highlight.noClasses=false in your site configuration, you need a style sheet. You can generate one with Hugo: hugo gen chromastyles --style=monokai > syntax.css Run hugo gen chromastyles -h for more options. See https://xyproto.github.io/splash/docs/ for a gallery of available styles. Highlight shortcode Highlighting is carried out via the built-in highlight shortcode.https://v0-122-0--gohugoio.netlify.app/content-management/mathematics/Mon, 01 Jan 0001 00:00:00 +0000https://v0-122-0--gohugoio.netlify.app/content-management/mathematics/New in v0.122.0 \[ \begin{aligned} KL(\hat{y} || y) &= \sum_{c=1}^{M}\hat{y}_c \log{\frac{\hat{y}_c}{y_c}} \\ JS(\hat{y} || y) &= \frac{1}{2}(KL(y||\frac{y+\hat{y}}{2}) + KL(\hat{y}||\frac{y+\hat{y}}{2})) \end{aligned} \] Overview Mathematical equations and expressions authored in LaTeX or TeX are common in academic and scientific publications. Your browser typically renders this mathematical markup using an open-source JavaScript display engine such as MathJax or KaTeX. For example, this is the mathematical markup for the equations displayed at the top of this page: