Content - Tag - arleo.euhttps://www.arleo.eu/en/tags/content/Content - Tag - arleo.euHugo -- gohugo.ioenSat, 09 May 2026 13:09:37 +0200Roadmap: should we migrate the 16 articles to content/posts/?https://www.arleo.eu/en/posts/roadmap-migration-content-posts/Sat, 09 May 2026 13:09:37 +0200Jmrhttps://www.arleo.eu/en/posts/roadmap-migration-content-posts/

Status: thinking, decision pending

This page documents a Hugo content architecture question I have not yet decided.

Context

The LoveIt theme used by arleo.eu follows the recommended Hugo convention: blog articles go in content/posts/. The home filters where Site.RegularPages Type posts.

But due to Grav migration history, my 16 editorial articles are at the root of content/, not in content/posts/. Hugo by default treats all these folders as Type page, not Type posts. So the LoveIt home filter does not see them, and I have to either override layouts/index.html or filter manually.

The question

Should I migrate the 16 articles to content/posts/ to follow LoveIt convention, or leave them at the root?

Option A: Migrate to content/posts/

Pros:

  • Theme conformity, no layout override needed
  • Repo readability, instantly see which folders are articles vs reference pages
  • Future-proof, if LoveIt evolves with new features on Type posts they apply for free
  • Standard mental model for any Hugo dev discovering the repo

Cons:

  • URL change. /csp-nonce/ would become /posts/csp-nonce/ by default. Breaks all inbound links.
  • Possible mitigation via explicit url in front matter to preserve URLs
  • Migration friction, 16 folders to move, 16 files to edit
  • Internal links: many articles cite each other, must audit

Option B: Keep the root

Pros:

  • Identical URLs without doing anything
  • No migration, 0 files touched
  • Internal links intact by definition
  • layouts/home.html override already in place, 1 line diff

Cons:

  • Custom override to maintain if LoveIt evolves
  • Repo readability: reference pages and articles mixed at root
  • Weird convention, a Hugo dev wonders why no posts folder

SEO considerations

SEO fears URL change. With url override on Option A, no URL change. But then what is the migration’s purpose? Just internal repo readability. Cost vs benefit, probably not worth it.

Hugo MCP considerations

The MCP tools accept a route parameter. With url override, MCP workflow is unchanged for the user.

The provisional decision

]]>