event 

Resource Organization

This theme expects resources like images as local files. We need to place them in page bundles and register them in the front-matter of the Markdown file. Resource files from parent sections or taxonomies can be re-used conveniently.

Hugo allows to handle resources in different ways and this theme has chosen the one which has a lot of support by Hugo out of the box, offers a lot of flexibility and doesn’t rely on external services.

Hugo’s general options

There are three ways to store and retrieve resource files (like images):

Page specific
We can save them in the folder of a page bundle and access them with a short relative path. We can register the resources in the front-matter and add additional meta-data. This Hugo feature has one big advantage: Every content page is self-sufficient and may be re-used in other sites simply by cloning its folder.
Site specific
We can save them in the assets folder and can use them for every page of our project. The favorite icon is a typical case. Hugo doesn’t offer a native data structure to add meta-data to assets, but its possible to build them.
Remote
Resources may also be retrieved via URL or API. This powerful feature has been introduced recently.

Resources for this theme

Perplex relies exclusively on page bundles to store page specific resources.

resources:
  - src: original_image_filename.jpg
    name: image

A resource needs to be registered as usual by providing its source path and adding a short name as an identifier label. We can add as many files we like to the list under the resources key. Its also possible to add arbitrary meta-data under an additional params key. This theme can process a bunch of them for the CommonMark image element.

Resources from other page bundles

There may be also a downside of this approach depending on the specific content structure. In case we want to include a resource more than once, we need to store and register it repeatedly. To overcome this problem at least partially, this theme is also looking for resources in taxonomy and parent pages, when they are not found in the current page. This also allows to use resources in simple pages, which aren’t bundles themselves.

Lookup order

In case a resource is not found in a given page, the theme tries the next related page and so on in the following order:

  1. Page
  2. First tag of the page
  3. First category of the page
  4. Parent of the page
  5. Parents parent
  6. Next parent and so on …