[jpurnell]

Summary

Adds a new StructuredData head element that renders JSON-LD <script type="application/ld+json"> tags for Schema.org structured data.

• Generic initializer — any schema type with a properties dictionary
• Raw JSON-LD — pass a pre-formatted JSON string for full control
• Convenience factories — Organization, WebSite, Event, Article, and BreadcrumbList with typed parameters
• Article and BreadcrumbList auto-populate from the publishing context (article metadata, page URL, site URL)
• Conforms to HeadElement and Sendable; 51 tests; DocC catalog entry

Usage

StructuredData is a HeadElement, so you use it inside a Head { } block in your Layout — the same place you'd put a MetaTag, MetaLink, or Script:

struct MyLayout: Layout {
    var body: some Document {
        Head {
            // Generic schema — any Schema.org type
            StructuredData("LocalBusiness", properties: [
                "name": "Joe's Pizza",
                "telephone": "555-0123"
            ])

            // Convenience methods
            StructuredData.organization(name: "Acme Corp", url: "https://acme.com")
            StructuredData.webSite(name: "Acme Corp", url: "https://acme.com")
            StructuredData.breadcrumbs()
            StructuredData.article(publisher: "Acme Corp", publisherURL: "https://acme.com")
            StructuredData.event(
                name: "Annual Conference",
                startDate: "2026-06-01",
                endDate: "2026-06-03",
                locationName: "Convention Center",
                locality: "Springfield",
                region: "IL",
                postalCode: "62701"
            )

            // Raw JSON-LD for schemas without a convenience method
            StructuredData(json: customJSONString)
        }

        Body {
            content
        }
    }
}

No site-level configuration is needed. Each StructuredData element renders an independent <script type="application/ld+json"> tag in the page's <head>, and you can include as many as you need per page. Context-aware schemas like Article and BreadcrumbList automatically emit nothing when they don't apply (e.g., breadcrumbs on the homepage, article schema on non-article pages).

Test plan

• 51 tests covering all schema types, edge cases, unicode, invalid input, stress tests, and documentation examples
• Builds clean on Swift 6.3 with strict concurrency (Sendable conformance, no @MainActor)
• Tests use the .publishingContext() trait (current upstream pattern)
• JSON-LD output validates at https://validator.schema.org on a live site

[MrSkwiggs]

I like the work done here, but I'm a bit torn with adding this and supporting this directly from within Ignite.

I'm starting to think it might actually make more sense to vend this as a separate plugin. That way we could make the plugin exhaustive and offer full parity with Schema.org without overloading Ignite directly?

Something akin to how Vapor registers additional functionality might be interesting to look into, but yeah... that'd require quite a significant rework to properly support.

[MrSkwiggs]

Since this is specifically about JSON-LD which stands for Linked Data, maybe this makes more sense here?

Suggested change

	public struct StructuredData: HeadElement, Sendable {
	public struct LinkedData: HeadElement, Sendable {

or even

Suggested change

	public struct StructuredData: HeadElement, Sendable {
	public struct SchemaData: HeadElement, Sendable {

[MrSkwiggs]

Since we're providing a few convenience constructors here, would it make sense to provide full parity from the get-go? IMHO if we introduce this feature with limited support, it wouldn't be quite user-friendly.

Now with that said, peeking at the amount of different types there are, maybe we could support most top-level constructors at least?

[jpurnell]

Closing this. The work has moved to a fork (jpurnell/Ignite) that is now maintained separately and has diverged from upstream, so this branch no longer represents a change intended for Ignite. The pushes to this branch over the past few days were fork-internal and were not meant for this pull request — apologies for the noise. Thank you for Ignite.