Blog entries have no <title>, but the mdx has a maintained meta section

[nijaba]

Received the following comment on LinkedIn. My .IDX file does have a title, bug must be in the page generation?

There is no title in your Title tag, so my bookmarking tool was angry ;-)

Error: Element title must not be empty.
From line 1, column 1845; to line 1, column 1852
et="true"></title><
https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.operate-first.cloud%2Fblog%2Foperate-first-operate-open-governance-and-hybrid%2F

https://www.linkedin.com/feed/update/urn:li:activity:6965948762112364544?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A6965948762112364544%2C6967331057578778625%29

[schwesig]

Title

@nijaba, thanks for letting us know.
react/gatsby seems to ignore the title information in the index.mdx in general.
All entries are missing the HTML title, although it is maintained in the .mdx file:
https://github.com/operate-first/operate-first.github.io/blob/main/content/posts/operate-first-defined-4-words/index.mdx

---
title: Operate First - Operate, Open, Governance and Hybrid
date: 2022-08-11
author: Nick Barcet
description: Operate First - 4 key concepts
tags:
  - OperateFirst
  - Operate
  - Open
  - Governance
  - Hybrid
  - Software
  - Principles
---

vs.
https://www.operate-first.cloud/blog/operate-first-operate-open-governance-and-hybrid

<style data-emotion="mantine "></style>
<title data-react-helmet="true"></title>

[schwesig]

other checks

validator.w3.org/nu/?doc=https%3A%2F%2Fwww.operate-first.cloud%2Fblog%2Foperate-first-operate-open-governance-and-hybrid%2F

maybe should be checked too

[schwesig]

• MUST: check gatsby/ react settings for title tag creation
• SHOULD: check other validator error messages for correct settings

[schwesig]

/kind bug
/kind website
/priority important-soon

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[nijaba]

/remove-lifecycle

On Sun, Jan 8, 2023 at 21:30 Thoth Bot ***@***.***> wrote: Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. /lifecycle stale — Reply to this email directly, view it on GitHub <#185 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIJSLSOADAP5O2SATUULY3WRNZ4RANCNFSM57G6QWHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Nicolas Barcet ***@***.***> a.k.a. nijaba, nick

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[schwesig]

/reopen

[sesheta]

@schwesig: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close