ProfilePage builder
Creates a ProfilePage for a Person or Organization. The ProfilePage builder injects @type, validates synchronously, and
rejects unknown properties.
Import
Section titled “Import”// Astro — shown first when Astro is selectedimport { ProfilePage } from '@unschema-graph/astro';
// Svelte 5import { ProfilePage } from '@unschema-graph/svelte';
// Core / Node.jsimport { ProfilePage } from '@unschema-graph/core';import { ProfilePageSchema } from '@unschema-graph/core';The ProfilePageSchema Zod schema is also exported for composition and advanced validation.
TypeScript types
Section titled “TypeScript types”import { ProfilePageSchema, type SchemaInput, type SchemaOutput,} from '@unschema-graph/core';
type ProfilePageInput = SchemaInput<typeof ProfilePageSchema>;type ProfilePageOutput = SchemaOutput<typeof ProfilePageSchema, 'ProfilePage'>;Input properties
Section titled “Input properties”| Property | Input type | Required | Default / constraints |
|---|---|---|---|
@id |
string | No | non-empty |
mainEntity |
object | Yes | — |
name |
string | No | — |
url |
string | No | — |
description |
string | No | — |
dateCreated |
string | number | Date | No | non-empty |
dateModified |
string | number | Date | No | non-empty |
inLanguage |
string | No | — |
The aliases above remain the exact authority for nested object types. The builder also accepts a
validation configuration as its second argument and always returns @type: 'ProfilePage'.
Minimal example
Section titled “Minimal example”import { ProfilePage } from '@unschema-graph/core';
const entity = ProfilePage({ "mainEntity": { "name": "Ada Lovelace" }});Output
Section titled “Output”{ "@type": "ProfilePage", "mainEntity": { "name": "Ada Lovelace" }}Relationships and recipes
Section titled “Relationships and recipes”- Related builders:
Article,BlogPosting,NewsArticle,Recipe - Used by: no dedicated recipe
- External sources: Schema.org ProfilePage
Common errors
Section titled “Common errors”- Passing an unknown property to the strict builder.
- Using source data that is missing a required property.
- Assuming valid Schema.org guarantees a search appearance.
Validation
Section titled “Validation”Use ProfilePage.safeParse(input) for external data. If Schema.org supports a property that
is not modeled yet, validate the entity first and then use withAdditionalProperties(). Never
pass invented properties to the strict builder.