Commit e5e34b7
schema: make Organization node resolvable on Article/TechArticle pages (#20524)
BlogPosting, FAQPage, and TechArticle nodes emit publisher (and related
fields) as a bare {"@id": "https://www.pulumi.com/#organization"}
reference. That @id only resolves to concrete data (name, logo) when the
same page's JSON-LD @graph also defines the Organization node — but only
the homepage does. Structured-data parsers evaluate each URL's JSON-LD
independently and do not dereference @id links across pages, so
publisher.name (required by schema.org/Article) and publisher.logo
(recommended for rich results) have been undefined on every blog post and
docs page.
This adds a minimal, resolvable Organization node (name, url, logo) to
the @graph on every non-home page, with values copied verbatim from the
homepage's node so the entity stays consistent site-wide. The homepage
keeps its existing full corporate entity (founders, address, sameAs,
etc.) unchanged and does not get a duplicate node.
Verified via local Hugo build: publisher @id now resolves to a concrete
Organization node with name + logo on both a blog post
(/blog/infrastructure-as-code-tools/) and a docs page
(/docs/iac/concepts/), while the homepage still emits exactly one
Organization node.
Co-authored-by: workprentice <257153108+workprentice@users.noreply.github.com>1 parent 520c89b commit e5e34b7
1 file changed
Lines changed: 28 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
241 | 241 | | |
242 | 242 | | |
243 | 243 | | |
| 244 | + | |
| 245 | + | |
| 246 | + | |
| 247 | + | |
| 248 | + | |
| 249 | + | |
| 250 | + | |
| 251 | + | |
| 252 | + | |
| 253 | + | |
| 254 | + | |
| 255 | + | |
| 256 | + | |
| 257 | + | |
| 258 | + | |
| 259 | + | |
| 260 | + | |
| 261 | + | |
| 262 | + | |
| 263 | + | |
| 264 | + | |
| 265 | + | |
| 266 | + | |
| 267 | + | |
| 268 | + | |
| 269 | + | |
| 270 | + | |
| 271 | + | |
244 | 272 | | |
245 | 273 | | |
246 | 274 | | |
| |||
0 commit comments