{"id":322450,"date":"2026-06-15T08:14:19","date_gmt":"2026-06-15T08:14:19","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/breadbugger\/"},"modified":"2026-06-15T11:40:46","modified_gmt":"2026-06-15T11:40:46","slug":"breadbugger","status":"publish","type":"plugin","link":"https:\/\/mg.wordpress.org\/plugins\/breadbugger\/","author":20190758,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"2.0.11","stable_tag":"2.0.11","tested":"7.0","requires":"5.6","requires_php":"7.4","requires_plugins":null,"header_name":"Breadbugger","header_author":"PaneStudio","header_description":"On-page bug tracker for pre-launch QA \u2014 baked fresh.","assets_banners_color":"121212","last_updated":"2026-06-15 11:40:46","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/wordpress.org\/plugins\/breadbugger","header_author_uri":"https:\/\/panestudio.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":44,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"2.0.10":{"tag":"2.0.10","author":"abiagio","date":"2026-06-15 11:40:46"},"2.0.11":{"tag":"2.0.11","author":"abiagio","date":"2026-06-15 11:40:46"}},"upgrade_notice":{"2.0.0":"<p>First public release. Per chi viene da PaneStudio Debug v1.x: migration data automatica all&#039;attivazione. Tutti i bug esistenti restano accessibili.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3573025,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3573025,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3572616,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3572616,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["2.0.10","2.0.11"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"On-page floating widget for creating bugs directly on the page","2":"Admin list with filters by status, priority, author","3":"Keyboard shortcut configuration with free-form capture","4":"Settings: reporter \/ manager roles, feedback, REST integration","5":"Pin selector cascade documentation"}},"plugin_section":[],"plugin_tags":[14783,94,108,39803,7615],"plugin_category":[42,59],"plugin_contributors":[267182],"plugin_business_model":[],"class_list":["post-322450","plugin","type-plugin","status-publish","hentry","plugin_tags-bug-tracker","plugin_tags-debug","plugin_tags-feedback","plugin_tags-pre-launch","plugin_tags-qa","plugin_category-contact-forms","plugin_category-utilities-and-tools","plugin_contributors-abiagio","plugin_committers-abiagio"],"banners":{"banner":"https:\/\/ps.w.org\/breadbugger\/assets\/banner-772x250.png?rev=3572616","banner_2x":"https:\/\/ps.w.org\/breadbugger\/assets\/banner-1544x500.png?rev=3572616","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/breadbugger\/assets\/icon-128x128.png?rev=3573025","icon_2x":"https:\/\/ps.w.org\/breadbugger\/assets\/icon-256x256.png?rev=3573025","generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p><strong>Breadbugger<\/strong> is a bug tracking tool built for the pre-launch phase of a WordPress site \u2014 the moment when designers, QA, developers and clients walk through the site looking for issues before go-live.<\/p>\n\n<p>Three complementary surfaces:<\/p>\n\n<ol>\n<li><strong>On-page floating widget<\/strong> \u2014 open the widget with a configurable keyboard shortcut, \"pin\" reports directly to the HTML element they refer to, attach screenshots captured on-the-fly from the browser.<\/li>\n<li><strong>Clean admin list<\/strong> \u2014 manage every report from a compact full-screen view: filter by status, priority, author; sort manually with drag &amp; drop; reply with inline notes.<\/li>\n<li><strong>REST API for external clients<\/strong> \u2014 app-password gated endpoints to integrate your bug tracker with CLIs, AI coding assistants, or custom scripts.<\/li>\n<\/ol>\n\n<h4>Key features<\/h4>\n\n<ul>\n<li><strong>Stable pin selectors<\/strong> \u2014 element selector built via a cascade: <code>data-breadbugger-name<\/code> (opt-in dev), then stable <code>id<\/code>, then semantic class, then positional CSS. Pins survive refactors.<\/li>\n<li><strong>Configurable hotkey<\/strong> \u2014 press the keys to set your preferred combo, with browser\/OS collision validation.<\/li>\n<li><strong>Reporter \/ manager role model<\/strong> \u2014 assign who can open reports (reporter) and who can manage them all (manager) via custom capabilities on any WordPress role.<\/li>\n<li><strong>Author filter + configurable visibility<\/strong> \u2014 managers can see and filter by author; reporters can optionally see only their own bugs.<\/li>\n<li><strong>In-browser screenshots<\/strong> \u2014 automatic capture via <code>getDisplayMedia<\/code> (HTML2Canvas-Pro as a fallback for modern CSS like <code>oklch<\/code> \/ <code>color-mix<\/code>).<\/li>\n<li><strong>Internationalized<\/strong> \u2014 Italian source, .po \/ .mo translations, .pot template ready for any language.<\/li>\n<li><strong>Built-in feedback channel<\/strong> \u2014 settings form to send bug reports \/ feature requests \/ questions to the author via <code>wp_mail<\/code>.<\/li>\n<li><strong>Branded email notifications<\/strong> \u2014 HTML emails for @mentions in notes and (optional) for new bugs and resolved bugs, with per-recipient frequency: all events, accorpate (timeout-based), daily digest, weekly digest, or none.<\/li>\n<\/ul>\n\n<h4>Use case<\/h4>\n\n<p>Client site pre-go-live: 5-10 people testing in parallel. Each one loads the site, opens the widget with a shortcut, pins the issue directly on the affected element. The PM \/ dev watches the admin list, sorts by priority, assigns fixes, marks resolved.<\/p>\n\n<p>Standalone. No external SaaS required. No data sent to third-party servers. Your bugs stay in your database.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the <code>breadbugger<\/code> folder to <code>\/wp-content\/plugins\/<\/code>, or install from WP Admin \u2192 Plugins \u2192 Add New \u2192 Upload Plugin.<\/li>\n<li>Activate the plugin via WP Admin \u2192 Plugins.<\/li>\n<li>Open <strong>Breadbugger \u2192 Settings<\/strong>.<\/li>\n<li>Enable \"Widget frontend\" to make the floating widget visible.<\/li>\n<li>Configure reporter \/ manager roles if you want to separate who can open vs. who can manage reports.<\/li>\n<li>(Optional) Customize the keyboard shortcut.<\/li>\n<li>Visit a public page of the site \u2192 press the shortcut (default <code>\u2318+E<\/code> \/ <code>Ctrl+E<\/code>) \u2192 create your first report.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"does%20the%20plugin%20send%20data%20to%20external%20servers%3F\"><h3>Does the plugin send data to external servers?<\/h3><\/dt>\n<dd><p>No. All data stays in your WordPress database. The only optional exception: the \"Feedback\" form in settings, when submitted, sends an email to the author through your site's mail system (<code>wp_mail<\/code>).<\/p><\/dd>\n<dt id=\"can%20i%20use%20it%20in%20production%2C%20not%20just%20pre-launch%3F\"><h3>Can I use it in production, not just pre-launch?<\/h3><\/dt>\n<dd><p>Yes, but it is designed for pre-launch. For end-user support tickets there are better solutions (Zendesk, Freshdesk, etc.).<\/p><\/dd>\n<dt id=\"do%20i%20have%20to%20add%20%60data-breadbugger-name%60%20everywhere%3F\"><h3>Do I have to add `data-breadbugger-name` everywhere?<\/h3><\/dt>\n<dd><p>No, it is opt-in. Without it the plugin cascades to id, class, positional CSS. It is useful only on 5-10 cornerstone blocks of the site to get extremely stable pins.<\/p><\/dd>\n<dt id=\"how%20do%20i%20integrate%20breadbugger%20with%20my%20ai%20coding%20assistant%3F\"><h3>How do I integrate Breadbugger with my AI coding assistant?<\/h3><\/dt>\n<dd><p>Settings \u2192 \"REST API for external clients\" \u2192 generate an app-password \u2192 use the header <code>Authorization: Basic &lt;user:app-password&gt;<\/code> in REST calls. Base endpoint: <code>\/wp-json\/breadbugger\/v1\/bugs<\/code>.<\/p><\/dd>\n<dt id=\"can%20i%20restrict%20reporters%20to%20see%20only%20their%20own%20bugs%3F\"><h3>Can I restrict reporters to see only their own bugs?<\/h3><\/dt>\n<dd><p>Yes, Settings \u2192 Visibility \u2192 \"Reporters see only their own reports\". Managers always see everything.<\/p><\/dd>\n<dt id=\"will%20uninstalling%20delete%20my%20data%3F\"><h3>Will uninstalling delete my data?<\/h3><\/dt>\n<dd><p>uninstall.php removes everything (bugs, settings, capabilities, attachments owned by the plugin, app-passwords containing \"Breadbugger\" in the name). If you want to keep your data, <strong>deactivate<\/strong> instead of uninstalling.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>2.0.11<\/h4>\n\n<ul>\n<li>New: refreshed plugin logo (the Breadbugger \"bread-bug\" mark) and matching WordPress.org icons.<\/li>\n<li>New: the front-end widget is now enabled by default on fresh installs.<\/li>\n<li>i18n: all admin list and front-end widget UI strings are now translatable (wrapped in wp.i18n) and the translation template (.pot) was regenerated.<\/li>\n<li>i18n: bundled translations for Italian plus 8 more locales \u2014 English (US), Spanish, French, German, Portuguese (Brazil), Russian, Japanese, and Simplified Chinese.<\/li>\n<\/ul>\n\n<h4>2.0.10<\/h4>\n\n<ul>\n<li>New: reporters can now open the admin <strong>Lista<\/strong> page (menu visible with the <code>breadbugger_report<\/code> capability), where they see only their own reports when \"reporters see own only\" is enabled. The Settings page remains manager-only.<\/li>\n<li>New: for reporter-only users the list renders as a clean read-only view \u2014 management controls (status, priority, notes, reorder, delete, attachments) are hidden in the UI and remain enforced server-side. Creating new reports is still available.<\/li>\n<\/ul>\n\n<h4>2.0.9<\/h4>\n\n<ul>\n<li>Security: GET \/bugs\/{id} now enforces the same per-author visibility as the list endpoint. A reporter restricted to \"see own only\" can no longer read another author's bug by requesting its ID directly (broken access control \/ IDOR fix). The frontend pin query applies the same restriction.<\/li>\n<\/ul>\n\n<h4>2.0.8<\/h4>\n\n<ul>\n<li>Security: escape the <code>categoria<\/code> value before rendering it in the admin list (prevents stored attribute-injection in the device chip).<\/li>\n<li>Updated: bundled SortableJS from 1.15.2 to 1.15.7 (latest stable).<\/li>\n<li>Updated Contributors metadata.<\/li>\n<\/ul>\n\n<h4>2.0.7<\/h4>\n\n<ul>\n<li>Changed: AI notes (created via REST API) are now ALWAYS hidden by default. The per-user preference no longer makes them appear inline.<\/li>\n<li>New: when the per-user preference is enabled, a small \"AI\" pill is rendered in the bottom-right corner of the notes box, showing the AI-note count. Clicking it reveals\/hides those notes for that bug only (session-scoped, not persisted).<\/li>\n<li>Settings label updated to \"Abilita pulsante note AI\" with refreshed description.<\/li>\n<li>Removed legacy inline \"N nota nascosta\" stub (replaced by the new AI pill).<\/li>\n<\/ul>\n\n<h4>2.0.6<\/h4>\n\n<ul>\n<li>New: distinct rendering for notes created via REST API (AI tools, agents) \u2014 green badge with AI icon instead of user initial, light tint, left border.<\/li>\n<li>New: per-user preference \"Show AI notes\" in Settings \u2192 Manutenzione (off by default). When off, API-sourced notes are replaced by a compact stub \"N nota nascosta\" so the count is still visible.<\/li>\n<li>REST: added <code>\/me\/preferences<\/code> (GET + POST) backed by <code>user_meta<\/code> for per-user UI preferences.<\/li>\n<\/ul>\n\n<h4>2.0.5<\/h4>\n\n<ul>\n<li>WP.org submission gate \u2014 passes Plugin Check.<\/li>\n<li>Header: Plugin Name simplified to \"Breadbugger\" (matches readme); tagline \"a PaneStudio tool\" moved to description.<\/li>\n<li>readme.txt: Description, Installation, FAQ and Screenshots rewritten in English (WP.org requires standard English).<\/li>\n<li>Bumped \"Tested up to\" to 7.0.<\/li>\n<li>Removed <code>load_plugin_textdomain<\/code> call \u2014 WordPress.org auto-loads translations since WP 4.6.<\/li>\n<li>Build script: added <code>.distignore<\/code> itself to its own exclude list (no longer leaks as a hidden file in the ZIP).<\/li>\n<li>Added targeted <code>phpcs:ignore<\/code> comments with rationale on legitimate direct DB queries (uninstall cleanup, migration UPDATEs, sequential bug numbering, queue dispatch enumeration) and on the file-scope variables in admin views (which are method-scoped via include, not global).<\/li>\n<\/ul>\n\n<h4>2.0.4<\/h4>\n\n<ul>\n<li>New: flusso email notifiche completo. Settings card \"Email &amp; Notifiche\" (ridotta a 6 colonne, bottom-right accanto a Feedback) con:\n\n<ul>\n<li>Sottoscrittori per evento (Nuovo bug + Risolto) per ogni utente con cap breadbugger_*<\/li>\n<li>Frequenza per utente: Tutte le mail \/ Accorpate (timeout) \/ Recap giornaliero \/ Recap settimanale \/ Nessuna<\/li>\n<li>Toggle \"Notifica reporter su risoluzione\" (default on)<\/li>\n<li>Input \"Finestra accorpate (min)\" \u2014 invia digest dopo X minuti di inattivit\u00e0<\/li>\n<li>Sezioni \"Mittente\" e \"Sottoscrizioni\" collapsibili per compattezza<\/li>\n<\/ul><\/li>\n<li>New: nuovo <code>Breadbugger_Notifications<\/code> con queue per-utente in user_meta + cron <code>breadbugger_5min<\/code> per dispatch batched. Daily a 8:00 UTC, weekly luned\u00ec 8:00 UTC.<\/li>\n<li>New: nuovi metodi <code>Breadbugger_Mailer::event_email()<\/code> (nuovo bug \/ risolto) + <code>digest_email()<\/code> (recap con elenco eventi cliccabili, etichette colorate, ordinati per timestamp).<\/li>\n<li>New: hook automatici su <code>create_bug<\/code> \u2192 dispatch 'new_bug' e su <code>update_bug<\/code> quando lo status passa a done\/done_by_ai\/closed \u2192 dispatch 'resolution'.<\/li>\n<li>Changed: snippet CLAUDE-DEBUG.md ora istruisce gli agent AI ad usare <code>done_by_ai<\/code> invece di <code>done<\/code> \u2014 il developer promuover\u00e0 manualmente a <code>done<\/code> dopo review.<\/li>\n<\/ul>\n\n<h4>2.0.3<\/h4>\n\n<ul>\n<li>New: deep-link <code>#bug-{id}<\/code> in URL (es. dal link nelle email) \u2014 il bug viene scrollato in vista e segnato con un accento cream a sinistra che pulsa 3 volte. Funziona anche su hashchange (clic su un altro link senza ricaricare).<\/li>\n<li>New: email HTML brandizzate Breadbugger. Nuovo <code>Breadbugger_Mailer<\/code> con template dark theme: pane logo + wordmark, blockquote nota su cream accent, CTA \"Vai al bug \u2192\", footer co-branded \"a PaneStudio tool\".<\/li>\n<li>New: settings card \"Email &amp; Notifiche\" \u2014 toggle \"Email su @menzione\" + campi \"Mittente (From)\" + \"Nome mittente\" con autosave (debounce 400ms su input).<\/li>\n<li>Changed: Subject email ora include il nome del sito \u2192 <code>[Breadbugger \u00b7 NomeSito] Autore ti ha menzionato su \"Bug\"<\/code>. Stesso pattern su feedback form.<\/li>\n<\/ul>\n\n<h4>2.0.2<\/h4>\n\n<ul>\n<li>Fix: @mention con display_name multi-word (es. \"Nome Cognome\") ora vengono pillati visualmente per intero e notificati via email. Server-side cerca prima i display_name con spazi via get_users + capability__in, poi fallback al lookup per user_login.<\/li>\n<li>Improved: user pool caricato eagerly al page load (insieme a \/bugs) \u2014 primo render gi\u00e0 con pill multi-word funzionanti.<\/li>\n<li>Internals: regenerated .pot template per le stringhe aggiunte nel 2.0.1 (mentions, copy bug-context, autosave indicator).<\/li>\n<\/ul>\n\n<h4>2.0.1<\/h4>\n\n<ul>\n<li>New: pagina Impostazioni completamente ridisegnata \u2014 dark theme branded PaneStudio, autosave on change, grid 12 colonne.<\/li>\n<li>New: status intermedio \"Done by AI\" tra in_progress e done.<\/li>\n<li>New: toggle \"Lista fullscreen\" per disabilitare la modalit\u00e0 full-bleed e mantenere la sidebar WP.<\/li>\n<li>New: editing inline delle note (doppio click \u2192 contenteditable). Empty content + blur = elimina nota.<\/li>\n<li>New: @mention utenti nelle note con autocomplete + notifica via wp_mail. Pesca da utenti con capability breadbugger_report o breadbugger_manage.<\/li>\n<li>New: pulsante \"Copia contesto AI\" per ogni bug \u2014 copia in clipboard titolo, status, priority, device, URL, pin selector, note (con autore) e screenshot URL in formato markdown.<\/li>\n<li>New: titolo bug truncato con \"...\" in lettura, scroll on hover, click per copiare titolo in clipboard.<\/li>\n<li>New: barra ricerca dopo \"Autore\" che cerca in titolo+note. Digitando sulla pagina senza click parte direttamente in modalit\u00e0 ricerca.<\/li>\n<li>New: filter chip device passa a click+dropdown (pattern coerente con priority\/status).<\/li>\n<li>New: tagline \"a PaneStudio tool\" sotto al wordmark BREADBUGGER (link discreto a panestudio.com).<\/li>\n<li>New: card pop-menu auto-flip verso il basso quando spazio sopra \u00e8 insufficiente o spazio sotto \u00e8 maggiore.<\/li>\n<li>Security: API request (HTTP Basic \/ app-password) distingue ora da sessione UI. API pu\u00f2 solo aggiungere note, modificare note create via API, e cambiare status. Update di altri campi e delete bug bloccati con 403.<\/li>\n<li>Security: notes ora taggate con source (\"ui\" o \"api\") nello shape.<\/li>\n<li>Fix: caratteri accentati (\u00e8\/\u00e0\/\u00f2\/\u00f9) nelle note non pi\u00f9 corrotti in <code>\\u00XX<\/code> (mancava wp_slash + JSON_UNESCAPED_UNICODE in set_array_meta).<\/li>\n<li>Fix: cache-bust filemtime su settings.css\/.js (era cappato a BREADBUGGER_VERSION).<\/li>\n<li>Fix: MENU_SLUG e SETTINGS_SLUG rinominati da 'panestudio-debug<em>' a 'breadbugger<\/em>' (rimasti dietro dal rebrand M2).<\/li>\n<li>Fix: hook detection in enqueue_assets ora cattura il return value di add_menu_page invece di costruire stringhe.<\/li>\n<li>Fix: classi CSS body via admin_body_class filter \u2014 body.breadbugger-list-page e body.breadbugger-settings-page (stabili a prescindere dal menu title).<\/li>\n<li>Fix: WP admin notice\/update-nag\/screen-meta nascoste nella modalit\u00e0 fullscreen della list.<\/li>\n<li>Fix: row con pop aperto sale a z-index:100 \u2014 il pop non viene pi\u00f9 coperto dalla card successiva.<\/li>\n<li>Fix: WP shell hide regole gate-ate su --fullscreen modifier.<\/li>\n<li>Fix: menu icon dashboard ora SVG dedicato 20\u00d720 (era pane.png 2:1 distorto).<\/li>\n<\/ul>\n\n<h4>2.0.0<\/h4>\n\n<ul>\n<li>Public release. Rebrand da \"PaneStudio Debug\" a \"Breadbugger \u2014 a PaneStudio tool\".<\/li>\n<li>New: hotkey configurabile (capture libero)<\/li>\n<li>New: modello ruoli reporter\/manager via capability custom<\/li>\n<li>New: filtro autore + opzione \"reporter vedono solo i propri\"<\/li>\n<li>New: feedback form integrato (wp_mail)<\/li>\n<li>New: pin selector cascade (data-breadbugger-name \u2192 id \u2192 class \u2192 finder \u2192 nth-of-type)<\/li>\n<li>New: i18n ready (text-domain breadbugger, IT\/EN)<\/li>\n<li>Changed: license GPLv2+<\/li>\n<li>Changed: tutti gli identifier rinominati da psdebug_* a breadbugger_*<\/li>\n<li>Changed: REST namespace da panestudio-debug\/v1 a breadbugger\/v1<\/li>\n<li>Migration: data esistente (bug, settings) migrata automaticamente all'attivazione<\/li>\n<\/ul>\n\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>Internal release \u2014 sviluppo M1 features.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Initial private release as PaneStudio Debug.<\/li>\n<\/ul>","raw_excerpt":"On-page bug tracker for pre-launch QA. Pin reports directly on the page, manage them in a clean admin list, integrate with external clients via REST.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/mg.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/322450","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mg.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/mg.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/mg.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=322450"}],"author":[{"embeddable":true,"href":"https:\/\/mg.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/abiagio"}],"wp:attachment":[{"href":"https:\/\/mg.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=322450"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/mg.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=322450"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/mg.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=322450"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/mg.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=322450"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/mg.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=322450"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/mg.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=322450"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}