| Prio | Original string | Translation | — |
|---|---|---|---|
| Returns a JSON Schema describing the data shape produced by each requested %s element's controls. A schema's top-level "description", when present, carries the element's usage notes. Schemas are only needed when configuring elements through edit-post; building static layout with html-to-page requires no schemas, so do not fetch them up front for that. Call this before adding CSS for layout, columns, or structural behaviour. Native design properties must be used when available instead of custom CSS classes. Responsive properties are objects keyed by breakpoint id (set any subset; see "breakpointKeys" in the schema's "$defs" or the get-breakpoints tool); non-responsive properties take a direct value. Properties that can be bound to dynamic data say so in their description and are paired with a "<property>_dynamic_meta" companion (a link control uses "dynamicMeta" inside the link value); when you write a [breakdance_dynamic ...] shortcode into a property, always write its companion too. Repeated subschemas are factored into "$defs" and referenced via "$ref". edit-post validates properties strictly against this schema: any key not present here is rejected, so use exactly the property names the schema lists. | You have to log in to add a translation. | Details | |
|
Returns a JSON Schema describing the data shape produced by each requested %s element's controls. A schema's top-level "description", when present, carries the element's usage notes. Schemas are only needed when configuring elements through edit-post; building static layout with html-to-page requires no schemas, so do not fetch them up front for that. Call this before adding CSS for layout, columns, or structural behaviour. Native design properties must be used when available instead of custom CSS classes. Responsive properties are objects keyed by breakpoint id (set any subset; see "breakpointKeys" in the schema's "$defs" or the get-breakpoints tool); non-responsive properties take a direct value. Properties that can be bound to dynamic data say so in their description and are paired with a "<property>_dynamic_meta" companion (a link control uses "dynamicMeta" inside the link value); when you write a [breakdance_dynamic ...] shortcode into a property, always write its companion too. Repeated subschemas are factored into "$defs" and referenced via "$ref". edit-post validates properties strictly against this schema: any key not present here is rejected, so use exactly the property names the schema lists.
You have to log in to edit this translation.
|
|||
Export as • Download Translation Package (Updated 3 weeks ago)