docs: merge the hand-written JSON-LD into Mintlify's node - #98
Merged
Merged
Conversation
Every page carried two Article nodes for one URL. Mintlify generates a full @graph with @id ".../slug#article"; the hand-written block in each MDX used ".../slug/#article", one slash apart, so nothing merged them. Deleting the hand-written block was the obvious fix and the wrong one. It is the only source of datePublished and author, which Mintlify does not emit. Aligning the @id merges the two instead, but naively doing that would have introduced two conflicts on the merged node, so all three changes go together: - @id: drop the slash before #article, so the nodes merge (30 pages) - dateModified: removed. It was a static date, while Mintlify emits a live build-time value that now also renders as the visible "Last modified on" stamp. Two values for one property on one node is a conflict, not detail. - isPartOf: removed. It pointed at https://rendobar.com/#website, the APEX WebSite node, which does not exist on a docs page. Mintlify's node already carries the correct isPartOf -> /docs#website. (31 pages, including the FAQ.) Net: one Article node per page instead of two, now carrying datePublished and author as well. support/faq.mdx is the odd one out, an FAQPage rather than an Article. Its @id had the same trailing slash and the node was floating unconnected, so it now matches the canonical form and points at Mintlify's WebPage node. snippets/org-jsonld.mdx is deleted. Nothing has ever imported it, and it declared a third Organization plus a fourth WebSite that would have conflicted with both graphs had anything used it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every page carried two Article nodes for one URL. Mintlify generates a full
@graphwith@id.../slug#article; the hand-written block in each MDX used.../slug/#article— one slash apart, so nothing merged them.Deleting them was the obvious fix and the wrong one
The hand-written block is the only source of
datePublishedandauthor; Mintlify emits neither. Aligning the@idmerges the nodes instead — but doing only that would introduce two conflicts on the merged node, so all three changes go together:@id: drop the slash before#articledateModifiedisPartOfhttps://rendobar.com/#website— the apex WebSite node, which does not exist on a docs page. Mintlify already carries the correctisPartOf → /docs#website. (31 pages)Net: one Article node per page instead of two, now carrying
datePublishedandauthoras well.Two others
support/faq.mdxis an FAQPage, not an Article. Same trailing-slash@id, and the node was floating unconnected. Now matches the canonical form and points at Mintlify's WebPage node.snippets/org-jsonld.mdxdeleted. Nothing has ever imported it (grep finds it only in.git/index), and it declared a third Organization plus a fourth WebSite that would have conflicted with both graphs had anything used it.Test plan
After merge, confirm one Article node per page in the rendered DOM.