matcornic/hugo-theme-learn

Enhance #184 to allow per-page enable/disable of breadcrumbs & previous/next page buttons

Open

#189 opened on Nov 1, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)HTML (1,575 stars) (1,427 forks)batch import
enhancementhelp wanted

Description

PR #184 added sitewide config flags for disabling breadcrumbs in the title bar and for disabling the previous/next page buttons beside the content.

Extend the functionality so that the features can also be overridden on per-page basis.

Contributor guide

Tech stack
htmlcssjavascript
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Hugo template syntaxHugo front matterPR #184 context
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
First, review the changes in PR #184 (https://github.com/matcornic/hugo theme learn/pull/184) to understand how sitewide breadcrumb and prev/next flags are implemented. Then, locate the relevant template files, likely in layouts/partials/ (e.g., header.html or similar). The goal is to add per page front matter parameters (e.g., disableBreadcrumbs, disablePrevNext) that override the sitewide config. Modify the templates to check for these per page values using the Hugo page variable (e.g., $.Params.disableBreadcrumbs). Ensure that when not set, the sitewide config is used as default. Test with a sample Hugo site using the theme.