Skip to content

Standardize Jobuary layout #668

Description

@AJaccP

As a maintainer, I want a single reusable Jobuary layout so that adding a new Jobuary year only requires a new content file, not a new layout file.


🧠 Context

Currently, each Jobuary year has its own layout file (jobuary-2025.html, jobuary-2026.html) that are identical except for the hard-coded taxonomy key used to fetch events (e.g. .Site.Taxonomies.tags.jobuary2026). This means someone has to duplicate the layout file every January just to change one word.

The fix is a single shared jobuary.html layout that reads the taxonomy key from a frontmatter param, using Hugo's index function for dynamic key lookup. Event files and tag format (jobuary202X + week1week4) stay exactly as they are.

jobuary-2024.html uses a different tag structure (categories instead of weeks) and should be left as-is.


🛠️ Implementation Plan

  1. Create layouts/_default/jobuary.html

    Copy jobuary-2026.html as the starting point. In each week's range, replace .Site.Taxonomies.tags.jobuary2026 with index .Site.Taxonomies.tags .Params.jobuary_tag so the layout reads the tag name from frontmatter rather than having it hard-coded. Add an {{ else }} clause to each week's range displaying a "Coming Soon" message for weeks that have no events yet.

  2. Update content/jobuary_2025/_index.md and content/jobuary_2026/_index.md

    Set layout: jobuary and add a params.jobuary_tag field with the appropriate tag name for each year (e.g. jobuary2026).

  3. Update URLs for old Jobuary pages

    In content/jobuary_2024/_index.md and content/jobuary_2025/_index.md, change the url field from /jobuary/2024 / /jobuary/2025 to /jobuary2024 / /jobuary2025 to be consistent with the WoA URL convention.

  4. Delete the now-unused layouts

    • layouts/_default/jobuary-2025.html
    • layouts/_default/jobuary-2026.html
  5. Verify /jobuary, /jobuary2025, and /jobuary2024 all render correctly with hugo server


✅ Acceptance Criteria

  • A single layouts/_default/jobuary.html exists and works for both 2025 and 2026
  • /jobuary, /jobuary2025, and /jobuary2024 all render the correct events
  • Old URLs (/jobuary/2024, /jobuary/2025) are no longer used
  • jobuary-2025.html and jobuary-2026.html are deleted
  • jobuary-2024.html and its content file are untouched
  • Weeks with no events display a "Coming soon" message instead of an empty section
  • No changes needed to any event markdown files

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions