docs: add schema.org structured-data matrix - #903
Merged
Conversation
Maps every JSON-LD schema type emitted across the docs site (from PR keploy#897) to its source file and the pages/components it applies to, as a single reference for adding, moving, or debugging structured data. Signed-off-by: dhananjay6561 <dhananjayaggarwal6561@gmail.com>
Signed-off-by: dhananjay6561 <dhananjayaggarwal6561@gmail.com>
dhananjay6561
force-pushed
the
docs/schema-matrix
branch
from
September 7, 2026 06:28
78d913f to
c968913
Compare
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.
What
Adds
SCHEMA_MATRIX.mdat the repo root — a single reference mapping every JSON-LDschema.orgtype emitted across the docs site to its source file and the pages/components it applies to.This documents the structured-data work merged in #897.
Why
PR #897 introduced structured data across many surfaces (site-wide graph, per-doc
DocItemschema, FAQ/HowTo, glossary DefinedTerms, and the bespoke React pages). There was no single place to see what emits what, which makes adding or debugging schema error-prone. This matrix is that reference.Coverage
Built by auditing the live source on
main(commit at #897), not from memory. Every@typeoccurrence insrc/+docusaurus.config.jswas reconciled against the table:Organization,WebSite,SoftwareApplication,ImageObject,SearchActionDocItem) —TechArticle/APIReference/BlogPosting/LearningResource,DefinedTerm,CollectionPage, and suppression rulesBreadcrumbList/ListItemFAQPage(remark plugin),HowTofamily (<HowTo>component)Includes a type → source quick-reference table.
Scope
Documentation only — one new file, no code or existing-file changes.