| Prio | Original string | Translation | — |
|---|---|---|---|
| Item %d on the design library site has no builder data, or access was denied (the set may require a password). | You have to log in to add a translation. | Details | |
|
Item %d on the design library site has no builder data, or access was denied (the set may require a password).
You have to log in to edit this translation.
|
|||
| The design library site returned an unreadable response. It may not have the Design Library enabled. | You have to log in to add a translation. | Details | |
|
The design library site returned an unreadable response. It may not have the Design Library enabled.
You have to log in to edit this translation.
|
|||
| Could not reach the design library site: %s | You have to log in to add a translation. | Details | |
| library_url is not a valid URL. Use a url returned by list-design-libraries. | You have to log in to add a translation. | Details | |
|
library_url is not a valid URL. Use a url returned by list-design-libraries.
You have to log in to edit this translation.
|
|||
| Post %1$d has no %2$s data. | You have to log in to add a translation. | Details | |
| No post with ID %d exists on this site. | You have to log in to add a translation. | Details | |
| Could not import %1$s %2$s from the design library site. Elements referencing them will render empty - rebuild them locally or remove them. | You have to log in to add a translation. | Details | |
|
Could not import %1$s %2$s from the design library site. Elements referencing them will render empty - rebuild them locally or remove them.
You have to log in to edit this translation.
|
|||
| The same skills ship as an installable agent plugin that loads them automatically. Offer it once: on confirmation run `npx skills add %1$s -y` (installs the skills for whichever agents are in use; add `-g` for the user's home directory), or the client's own plugin commands, in Claude Code `claude plugin marketplace add %1$s` then `claude plugin install builder-kit@soflyy`, in Codex `codex plugin marketplace add %1$s` then install "builder-kit" from the plugins directory, and tell the user the skills load in the next session. Clients that cannot run commands (ChatGPT) keep using get-skill. | You have to log in to add a translation. | Details | |
|
The same skills ship as an installable agent plugin that loads them automatically. Offer it once: on confirmation run `npx skills add %1$s -y` (installs the skills for whichever agents are in use; add `-g` for the user's home directory), or the client's own plugin commands, in Claude Code `claude plugin marketplace add %1$s` then `claude plugin install builder-kit@soflyy`, in Codex `codex plugin marketplace add %1$s` then install "builder-kit" from the plugins directory, and tell the user the skills load in the next session. Clients that cannot run commands (ChatGPT) keep using get-skill.
You have to log in to edit this translation.
|
|||
| The same skills ship as an installable agent plugin that loads them automatically; if the user wants that, ask them for its install source or point them to the builder documentation. | You have to log in to add a translation. | Details | |
|
The same skills ship as an installable agent plugin that loads them automatically; if the user wants that, ask them for its install source or point them to the builder documentation.
You have to log in to edit this translation.
|
|||
| %s also has skills: step-by-step guidance for building whole sites and WooCommerce stores, templates, mega menus and a library of copy-ready layout patterns. You MUST load the skill covering the work before you build it, exactly as you must call get-instructions: woocommerce-store before any store work, design-first-build before a new site or a batch of pages, building-templates before anything reused across many URLs, patterns whenever you need a layout. Use them from your context when they are already loaded as plugin skills; otherwise this server serves them through get-skill (no arguments for the index, then a name such as woocommerce-store, design-first-build, patterns or mega-menus). get-instructions repeats the full list with the trigger for each. | You have to log in to add a translation. | Details | |
|
%s also has skills: step-by-step guidance for building whole sites and WooCommerce stores, templates, mega menus and a library of copy-ready layout patterns. You MUST load the skill covering the work before you build it, exactly as you must call get-instructions: woocommerce-store before any store work, design-first-build before a new site or a batch of pages, building-templates before anything reused across many URLs, patterns whenever you need a layout. Use them from your context when they are already loaded as plugin skills; otherwise this server serves them through get-skill (no arguments for the index, then a name such as woocommerce-store, design-first-build, patterns or mega-menus). get-instructions repeats the full list with the trigger for each.
You have to log in to edit this 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.
|
|||
| Returns guidance for working with the %s builder via this MCP server. You MUST call this before any build or edit tool. | You have to log in to add a translation. | Details | |
|
Returns guidance for working with the %s builder via this MCP server. You MUST call this before any build or edit tool.
You have to log in to edit this translation.
|
|||
| Unknown condition "%s". Use a slug from get-template-conditions or get-element-conditions. | You have to log in to add a translation. | Details | |
|
Unknown condition "%s". Use a slug from get-template-conditions or get-element-conditions.
You have to log in to edit this translation.
|
|||
| The matching value options, in the same shape the condition's values take in get-template-conditions: usually a list of { label, items } groups whose items are { text, value }. Empty groups mean nothing matched. | You have to log in to add a translation. | Details | |
|
The matching value options, in the same shape the condition's values take in get-template-conditions: usually a list of { label, items } groups whose items are { text, value }. Empty groups mean nothing matched.
You have to log in to edit this translation.
|
|||
| The condition that was searched. | You have to log in to add a translation. | Details | |
Export as • Download Translation Package (Updated 3 weeks ago)