| Prio | Original string | Translation | — |
|---|---|---|---|
| Use these tools to build and edit pages, templates, headers and footers with %s, the WordPress website builder. You MUST call get-instructions before any build or edit tool (html-to-page, edit-post, insert-stylesheet, set-element-*); do not create or modify anything until you have called it. PREFERRED BUILD PATH: author new pages and sections as semantic HTML with a <style> block and pass them to html-to-page, and manage design-system CSS (classes, variables) with insert-stylesheet; do NOT assemble static layouts element-by-element, and do not fetch element schemas just to build static markup. Repeating collections (blog grids, category tiles, custom product cards) are HTML too: mark the container bd-loop="products|posts|terms" and bind the item's values with bd-bind / bd-href / bd-src (see "Loops" in get-instructions); the shop grid itself is WooCommerce's native loop, an empty bd-woo="shop" element (see get-ecommerce-instructions). Use edit-post and the set-element-* tools as escape hatches for fine-grained edits and for the few things html-to-page cannot express (forms, dynamic widgets). Discover with get-element-slugs, get-breakpoints, get-css-selectors, search-posts and get-post-tree. If you prefix your CSS classes, use the site's "css_prefix" (returned by get-css-selectors and site-info) rather than inventing your own. Verify builds by rendering the frontend HTML with preview-post (whole post) or preview-element (one element). When setting element properties with edit-post, always call get-element-schemas first, edit-post rejects properties that do not match. The builder's Modern Normalize stylesheet (margin/padding reset included) is off by default, leaving browser default margins on headings, paragraphs and lists: enable it with set-settings (advanced.modern_normalize_enabled) before styling pages (see the "Margins and padding" section of get-instructions). For WooCommerce work (shop, product templates, product pages, cart, checkout) you MUST also call get-ecommerce-instructions before building. | You have to log in to add a translation. | Details | |
|
Use these tools to build and edit pages, templates, headers and footers with %s, the WordPress website builder. You MUST call get-instructions before any build or edit tool (html-to-page, edit-post, insert-stylesheet, set-element-*); do not create or modify anything until you have called it. PREFERRED BUILD PATH: author new pages and sections as semantic HTML with a <style> block and pass them to html-to-page, and manage design-system CSS (classes, variables) with insert-stylesheet; do NOT assemble static layouts element-by-element, and do not fetch element schemas just to build static markup. Repeating collections (blog grids, category tiles, custom product cards) are HTML too: mark the container bd-loop="products|posts|terms" and bind the item's values with bd-bind / bd-href / bd-src (see "Loops" in get-instructions); the shop grid itself is WooCommerce's native loop, an empty bd-woo="shop" element (see get-ecommerce-instructions). Use edit-post and the set-element-* tools as escape hatches for fine-grained edits and for the few things html-to-page cannot express (forms, dynamic widgets). Discover with get-element-slugs, get-breakpoints, get-css-selectors, search-posts and get-post-tree. If you prefix your CSS classes, use the site's "css_prefix" (returned by get-css-selectors and site-info) rather than inventing your own. Verify builds by rendering the frontend HTML with preview-post (whole post) or preview-element (one element). When setting element properties with edit-post, always call get-element-schemas first, edit-post rejects properties that do not match. The builder's Modern Normalize stylesheet (margin/padding reset included) is off by default, leaving browser default margins on headings, paragraphs and lists: enable it with set-settings (advanced.modern_normalize_enabled) before styling pages (see the "Margins and padding" section of get-instructions). For WooCommerce work (shop, product templates, product pages, cart, checkout) you MUST also call get-ecommerce-instructions before building.
You have to log in to edit this translation.
|
|||
Export as • Download Translation Package (Updated 3 weeks ago)