Title: Portabrief Author: sirahama Published: 4 Julai 2026 Last modified: 4 Julai 2026 --- Search plugins ![](https://ps.w.org/portabrief/assets/banner-772x250.png?rev=3596019) ![](https://ps.w.org/portabrief/assets/icon.svg?rev=3595943) # Portabrief Oleh [sirahama](https://profiles.wordpress.org/sirahama/) [Download](https://downloads.wordpress.org/plugin/portabrief.0.13.2.zip) * [Details](https://ms.wordpress.org/plugins/portabrief/#description) * [Reviews](https://ms.wordpress.org/plugins/portabrief/#reviews) * [Pemasangan](https://ms.wordpress.org/plugins/portabrief/#installation) * [Pembangunan](https://ms.wordpress.org/plugins/portabrief/#developers) [Support](https://wordpress.org/support/plugin/portabrief/) ## Description Portabrief turns a WordPress page (or the whole site) into a **portable rebuild package**: a single `BRIEF.md` that describes the design system, components, content, and navigation, plus bundled assets, fonts, a `manifest.json`, and a per-module breakdown. The goal is a self-contained handoff you can rebuild from on a _different_ stack — Next.js, Astro, Nuxt, Eleventy, Hugo, a native WordPress block theme, a headless front-end, an LLM coding agent, or Claude Design. It is built for developers and agencies who are escaping page-builder lock-in, re- platforming a site, or handing a design off to another team or an AI. #### What it produces * `BRIEF.md` — a synthesis-first, human- and LLM-readable brief: design tokens ( colour, typography, spacing), an inferred component inventory with token bindings, the content outline, navigation, rebuild instructions, a gaps list, and a transparent** portability score** with its composition. * Bundled `assets/`, `fonts/`, `logos/` (self-hosted resources are copied; remote ones are recorded by URL). * `manifest.json` — the machine-readable mirror of everything. * Destination-specific scaffolding (the chosen target gets a tailored starting point and a “recommended stack & elements” section). #### Key features * **Whole-site or single-page** export from a Tools Portabrief screen. * **Real portability score** computed server-side, with a Coverage / Fidelity / Risk-headroom breakdown. * **Secret redaction** — credentials and API keys are never written to the package; only their existence is noted, masked as `***REDACTED***`. A pre-flight scan blocks the download if any residual secret is detected. * **PII safeguards** — user records are off by default; when an admin includes them, the UI states plainly that real email addresses are exported, and a bundle headed to an external AI must be explicitly acknowledged. * **Export history** — a local, append-only audit log of every export (who, scope, destination, whether PII was included and acknowledged). Stays on your site. * **Feedback box** — request a feature or report a bug from inside the admin. ### External services Portabrief works fully offline by default. Three optional integrations may contact an external service, each only when you choose to use it: 1. **Feedback email** — when you submit the in-admin feedback form, your message, the email you enter, your site URL, and basic environment info (WordPress/PHP/plugin versions) are emailed via your site’s own mailer to the **Portabrief developer**(` connect@1click2open.com`) so they can respond — or to an address you configure with the `PORTABRIEF_FEEDBACK_EMAIL` constant / `portabrief_feedback_recipient` filter. Nothing is sent unless you click “Send feedback”. 2. **Portabrief Hub (optional)** — if you configure a central Hub (via the `PORTABRIEF_HUB_URL`/` PORTABRIEF_HUB_KEY` constants), feedback tickets are sent to it and their status is synced back. Off unless those constants are set. 3. **Usage analytics (opt-in)** — if you tick “Share anonymous usage analytics” in Tools Portabrief, an anonymous payload (a random install ID, plugin/WordPress/ PHP versions, and aggregate counts — never your URL, content, emails, secrets, or any export data) is sent to the configured Hub. Off unless you turn it on; the exact payload is previewable before you opt in. Detection only (no connection): to document your site, Portabrief scans your own pages and options for third-party services already present (e.g. Stripe, Intercom, Google Tag Manager, Meta Pixel, Tawk.to, Hotjar) and records which ones it finds. These are local detection patterns — Portabrief does not connect to any of these services and sends them no data. ## Installation 1. In wp-admin, go to **Plugins Add New Upload Plugin** and upload the Portabrief zip (or copy the `portabrief` folder into `wp-content/plugins/`). 2. Activate **Portabrief**. 3. Visit **Tools Portabrief**, choose a scope and destination, and click **Generate BRIEF**. ## FAQ ### Does Portabrief send my data anywhere? No — not by default. Generating a brief runs entirely on your server and gives you a downloadable zip. The plugin only contacts an external service if **you** opt in. See “External services” below. ### Are secrets or passwords included in the export? Never. Credentials and API keys are redacted, and a pre-flight scan blocks the download if anything secret-shaped slips through. User passwords are never exported under any setting. ### What about user emails / PII? The “User records” module is off by default. If a site administrator turns it on, the bundle is watermarked sensitive and the admin is told plainly that real email addresses are written into it. An export that contains user PII and targets an external- AI destination requires an explicit confirmation. ### Can it migrate my site automatically? No. Portabrief produces a faithful, structured _starting point_ to rebuild from — not a one-click migration. A developer or an AI does the rebuild using the brief. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Portabrief” adalah perisian sumber terbuka. Orang-orang berikut telah menyumbang kepada pemalam ini. Penyumbang * [ sirahama ](https://profiles.wordpress.org/sirahama/) [Translate “Portabrief” into your language.](https://translate.wordpress.org/projects/wp-plugins/portabrief) ### Berminat dalam pembangunan? [Layari kod](https://plugins.trac.wordpress.org/browser/portabrief/), periksa [repositori SVN](https://plugins.svn.wordpress.org/portabrief/), atau langgani [log pembangunan](https://plugins.trac.wordpress.org/log/portabrief/) dengan [RSS](https://plugins.trac.wordpress.org/log/portabrief/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 0.13.2 * Maintenance release. No functional changes since 0.13.1. #### 0.13.1 * Reworded internal asset/usage labels and code comments that described detected style/script blocks, so they no longer contain literal markup substrings. No functional change. (All plugin CSS/JS is, and has been, enqueued via wp_enqueue_style/ wp_enqueue_script on admin_enqueue_scripts.) #### 0.13.0 * All features are now free and unconditional (no plan gating): every destination, screenshots, SBOM, delta exports, link graph, and the full score breakdown. A“ portabrief_after_export” action lets a separate add-on extend exports. * readme: clarified that third-party service names (Stripe, GTM, etc.) are local detection only; pre-flight scan now reports email-address (PII) counts in the bundle. #### 0.12.4 * Branding: author is now 1click2open; feedback wording uses “developer”. #### 0.12.3 * Feedback now routes to the Portabrief team address by default (still overridable via constant/filter). #### 0.12.2 * Plugin Check compliance: removed dev config from the package, dropped manual textdomain loading (WordPress auto-loads), cleaned the plugin header, and annotated verified-safe internal DB reads. #### 0.12.1 * Final pre-submission audit: feedback now emails the site admin by default (no hard-coded address); telemetry install ID is assigned only on opt-in; remote asset fetches restricted to http(s). #### 0.12.0 * Export history (local audit log) of every export, and an opt-in, anonymous usage- analytics option. * Real, server-computed portability score in the admin with its Coverage / Fidelity/ Risk composition. * PII external-AI export guard (honest UI + confirmation + server-side enforcement). * Feedback box with optional central-Hub ticket sync. * Ten destination targets, each with tailored rebuild guidance; native WordPress block-theme target. #### 0.4.0 * Consolidated build: all extractors, PSR-4 layout, post-hoc secret sweep, WordPress coding-standards clean. #### 0.1.0 * Initial release: export pipeline, redaction, manifest.json, and a data-driven BRIEF.md. ## Meta * Version **0.13.2** * Last updated **13 jam lalu** * Active installations **Kurang dari 10** * WordPress version ** 6.0 or higher ** * Tested up to **7.0** * PHP version ** 8.1 or higher ** * Language * [English (US)](https://wordpress.org/plugins/portabrief/) * Tags * [design](https://ms.wordpress.org/plugins/tags/design/)[developer](https://ms.wordpress.org/plugins/tags/developer/) [export](https://ms.wordpress.org/plugins/tags/export/)[headless](https://ms.wordpress.org/plugins/tags/headless/) [migration](https://ms.wordpress.org/plugins/tags/migration/) * [Paparan Lanjutan](https://ms.wordpress.org/plugins/portabrief/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/portabrief/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/portabrief/reviews/) ## Penyumbang * [ sirahama ](https://profiles.wordpress.org/sirahama/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/portabrief/)