the pinebank vault




massive hugo guide for me or someone like me

sections/lists/bundles

sections are “top-level content directory” containing an _index.md (under the content folder). sections are subfolders with their own shit going on. an example would be a /blog/ branch with its leaves being individual posts. i’m using branches and leaves bc that’s what the hugo docs use.

themes > layouts > section_name can have:

  1. list.html
  2. page.html

the list.html is how you would format and display the “leaves” in a group/section/list. <– using those words to mean the same thing in this instance.

page.html is where you would structure what a single leaf would look like.

currently, my blog’s list page has the individual posts displayed with the title, a summary, and a link attached.

the page.html for the individual posts had the title, the content of the associated .md file of the post, and a list of tags at the bottom.

sometimes the individual pages have their own resources within the post. an example would be an image. in this case, that page becomes a leaf bundle.

content > section_name > page_name > index.md content > section_name > page_name > includedimage.jpg

index.md, as i understand it, is a markdown representation of a single page. it needs to exist so hugo can build its corresponding html file.

for example, content > about > index.md

it has minimal front matter (a title and a draft = false) and the contents are empty. i created it so i would have an about page. the actual html file for the about page is in:

themes > layouts > about > single.html

that’s where i customized the about page with all those post-its and graphics.

pagination

  1. how do i get the previous and next buttons on the individual pages of a section?

.HasNext and its sister page, .HasPrev

  1. what if the section/list page has way too many items? how can i split that page into multiple pages?
tags: coding hugo