Shortcodes on Emet CMS

Block shortcodes

Mon, 01 Jan 0001 00:00:00 +0000

A block shortcode is one you’ve described in site.yaml: its name, the parameters it takes and, optionally, what it should look like in the preview. In the visual editor it shows up as a card with a form, so whoever is writing doesn’t need to remember the parameter names or the quoting rules. In the file it’s the same {{< name >}} text Hugo has always read.

Configuration#

Define them under shortcodes:

Inline shortcodes

Mon, 01 Jan 0001 00:00:00 +0000

Hugo’s inline shortcodes let you write a shortcode’s template inside the content file that uses it, instead of in layouts/shortcodes/. They’re handy for one-off formatting that doesn’t deserve a layout file, and Emet supports them without any configuration, because everything it needs is in the page. (Hugo needs enableInlineShortcodes = true in its config before it will render them.)

How Hugo writes them#

An inline shortcode has a name ending in .inline. The first time it appears it carries its template between opening and closing tags; after that you can reuse it by name:

Preview templates

Mon, 01 Jan 0001 00:00:00 +0000

A shortcode card in the editor tells you what the parameters are, not what the result looks like. The preview pane is where that happens, and the preview property on a block shortcode is the HTML it uses. Emet can’t run your Hugo templates in the browser, so you give it a simplified stand-in with the field values dropped in.

This mostly affects the preview pane. A block card in the visual editor never renders it; the one place it shows up in the editor is the label on a chip for a shortcode sitting inside a sentence.