Rename layout fragment to include _td- prefix and move file

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.

Problem

Any page that uses the /layouts/_default/content.html template is unable to render recent code changes, specifically related to the recent date: frontmatter addition in MR !272 (merged).

Root Cause

Docsy and Hugo were recently updated to new versions. Per Docsy issue 2243 tasks we need to add the _td- prefix to the default content.html layout template. This file also needs to be moved out of _default and into the root layouts directory.

Solution

The content.html template was renamed to _td-content.html and moved into the root layouts directory.

Testing and Validation

Changes were made locally and validated against live theme.

Validation

Before (live theme)

After (locally)

With date: Frontmatter Addition

---
title: Underperformance
description: We want team members to be successful and should offer every opportunity for them to work effectively.
date: 2025-10-08
---

• Rename layout fragment to include _td- prefix and move file

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Handbook: For changes that affect handbook users, but does not need company-wide attention, post in the #handbook Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

---