Unyson+Manual Extensions Blocks Demos Animation Engine The Theme Guides AI Dev Kit API Reference Design Decisions News

GitHub

All decisions

2026

Should the Site Converter tell a blog post from a page — and where do custom post types come from?
Why is the Elementor extension called just "Elementor" and not "Elementor Widgets"?
Where does a new page builder plug into the Site Converter — and what does it own?
Can Unyson+ colours and fonts stay in sync with Elementor's — both ways?
Why Short Links' API keys only open one door, and webhooks never fire inline
Why Short Links stores links in its own tables, defaults to 307, and counts uniques without trusting cookies
When is it right for the converter to throw away text the source shows?
Why the box-owner rule had to be enforced twice, in two languages, at the point where every path converges
Why the docs name the tools, plugins and AI products Unyson+ works with, but never the sites it converted
Why the measurement tools share one browser session instead of each launching their own
Why 'fix my site' and 'train the converter' became one protocol instead of two
Why retargeting a site to a new source replaces its pages — but only the ones you tick
Why the Security extension ships few measures, none of them on by default, and why the custom login URL lives there
Why the AI Assistant settings screen leads with one status, and what Reset does and does not touch
Why the AI Assistant's ideas come from rules, and its conversations are saved per user on the server
Why the AI Assistant's free local AI runs its loop in the browser, with JSON actions instead of tool calls
Why menu item styles split into a base treatment plus stackable modifiers
Why we silence Chrome's “unload” Permissions-Policy console violation on the editor screens
Why hiding a core affordance has to be scoped to wherever its replacement exists
Why a site's own conversion corrections live in wp-content, not framework-customizations
Why converting a multi-page site is one conversion, not one per page
Why a converted colour is stored as hex, and not as a Color Preset reference
Why an extension that ships 'on by default' is seeded once and never re-checked
Why the Image Box and Gallery stopped rounding their own corners
Why a dark admin skin deliberately leaves some panels white
Why form submissions get their own Entries table instead of going into the newsletter list
Why the newsletter preference centre reuses the unsubscribe token, and why saving it never unsubscribes anyone
Why the #page wrapper stays instead of moving its role onto <body>
Why the AI Dev Kit and Capture Service are non-commercial source-available while the plugin stays GPL
Why new Pages open in the builder while Blog Posts stay on the Classic editor
Why hover animations became one shared library for boxes and buttons (and where the tab sits)
Why the Site Converter will target other page builders (and how the roadmap labels them)
Why an element fills its parent instead of carrying its own width container
Why the Background Pro tab UI became a reusable `tabs` option type
Why glass (backdrop-blur) and flex-basis/min-width became native shortcode options + a theme token
"3D Gallery" → "Motion Gallery": rename what users see, keep the internal identifiers
Converting source motion: a deterministic Animation Engine effect-recognizer layer, not a frozen CSS shim
A new scroll-choreographed IMAGE element: where it lives, what we call it, and which builder tabs an invisible overlay should expose
Matching a licensed display font to a free lookalike: a curated deterministic map, not a per-conversion AI call
How a Tab holds rich, nested content: reuse Snippets, not query-posts, id-targeting, or a parallel builder
Matching an arbitrary licensed font to a free one: build a self-owned visual matcher, don't adopt an existing model
Decomposing a deep catalog into native elements: shallow band-sections, not a faithful recursive tree
Why a styled content card converts VERBATIM (Tailwind reproducer), not as a decomposed mirror
Media-Library SVG uploads: build a per-role setting on the sanitiser we already own, don't add a Safe-SVG-style plugin dependency (or a second system)
Why the tab content frame is one 'Content Frame' select (not separate border/padding toggles)
Why the tabs nav converts via a scoped-CSS pill translator, not new native options
Why catalog/menu sites get Catalog Mode — auto-detected AND a checkbox
Why a CSS-composed logo becomes an inline SVG, not a new logo mode
Why the Flexbox stays one shortcode, split only in the UI
Why image-tile grids (a caption pinned over each photo) convert to the Gallery, with a new always-visible overlay caption mode
Why the live editor wraps Flexbox/Grid/Block in a Section (when the backend doesn't)
Why a non-Google heading font is substituted with the closest FREE Google lookalike, never re-hosted
Why design-decision URLs keep the /decisions/ prefix
Should the Site Converter duplicate the source DOM, now that flexbox makes it possible?
One prefix (fw-) for everything, with a modernized utility vocabulary
Should a Section-tag Div be resizable, or always a full-width band?
Why not integrate Tailwind into UnysonPlus (even for the Site Converter)
How should authors pick the scroll % for a 3D choreography keyframe
Why author page JSON with native shortcode options instead of inline styles
Which converted regions become UnysonPlus blocks, and which stay core
Do we even need a Landing Page template, or can the per-page settings hide the chrome?
Why the Mega Menu builder stays in Appearance → Menus, not the Customizer
Why "Interactive Reveal" is its own element, not a mode of one mega-element
Should the page-wide WebGL/scene options be one selectable background effect instead of a raw toggle + code fields?
Why is the per-post SEO title empty by default — shouldn't it be pre-filled with the template?
Adding entrance animations on conversion — should the local AI drive it, or the deterministic converter?
Which container owns a card's box on conversion — the icon_box, or its column?
A converter option is “unmapped” — is that a bug to fix or a default to keep?
Should we document every PHP function — and how?
Testimonials extra stat lines — a repeatable label+value, a single pair, or freeform text?
How should the Site Converter derive Button Size presets from a source's buttons?
Should the converter use the local AI to pick a shortcode's style, or stay deterministic?
How should the spacing & gap scales handle modern mid-range and large gutters?
How should the converter map ALL shortcode/theme-settings options — a detector per option?
Future-proofing the Steps/Process shortcode — full Card Rows now, or a Box Preset first?
Where should the deep Site Converter docs live — in the extension, or moved to the AI Dev Kit?
When the converter derives a site's Box Presets, do we replace the built-in defaults or keep them?
Converting an inner page — does the user hand-uncheck options, or should the converter infer it from the URL?
Converting a store — should the converter auto-detect WooCommerce, or gate it behind a checkbox?
Why theme typography went fluid and accessibility-first
Why converted styles keep getting overruled — and why we re-assert the source instead of building an overrule detector
Why the typography overhaul is staged as "v3", then promoted to canonical
Why the group container gained a native title/desc instead of a leading html option
Why can't a header be transparent AND shrink its logo on scroll? Splitting header behavior into two composable states.
Why we keep the 'Enable' switch even though image-picker choices are now deselectable
A block's values never meet the validator that guards the page builder. Why leave it that way?
The combined script doesn't look minified — is that a bug?
Every public endpoint already checked a nonce. Why add rate limiting?
The React controls looked right and rendered right. Why test them against PHP at all?
Revision history was capped at 20 per page. Why did that turn into 150 MB?
Front-end memory was halved. Why did we stop instead of finishing the job?
The plan said the builder canvas rewrite needed a forcing reason. Why did we do it anyway?
Should a pasted CodePen become native shortcodes, and where should that live?
Deleting Mega Menu erased it from the Extensions manager — hand-maintain the catalog, or derive it?
The options modal shipped 6.7 MB — ship schemas instead of markup?
How should Unyson+ elements appear in Gutenberg — ported, or delegated?
Was it worth replacing WordPress's media frame to get Backbone out of the core?
Is the extension architecture itself legacy — should elements be rewritten block-native?
When the deterministic converter reads a source built in Tailwind, why not just copy the source's Tailwind classes into each shortcode's Advanced → Custom CSS Class field and be done — instead of mapping every element to native options?
Why the tooltip is called fw-tooltip and not floating-ui
Should we publish a public Technology & Roadmap page — and how do we frame the legacy?
Why shape dividers are their own library storing geometry only, with colour per-instance
Why Button Set is its own option type instead of a display mode on radio
The Section now routes Min Height, Container Width and vertical-align to stylesheets — should the background (color/gradient/image/overlay) move to the per-page page-{id}.css too, or stay an inline style?
When a source constrains its content to a max-width the theme has no preset for, should the converter snap to the nearest fixed preset, emit a per-section custom width, or tokenize container widths into a reusable library?
When the converter can't map a source class (like max-w-2xl) to a native shortcode option, where must that style go — and what's the rule between the child theme stylesheet, an element's Custom CSS, and Theme Settings → Miscellaneous → Custom CSS?
When a source element's styling classes can't all map to native options — like a text logo's font-serif / tracking-tight / hover:text-primary — how should the converter translate them, and does the rule apply to chrome as well as content?
The special-heading subtitle was almost never used by the converter — should we map a following paragraph into it, and should the field become a rich editor?
How should the Site Converter carry a source button's hover animation — reproduce its CSS verbatim, or classify it into the theme's named hover-effect vocabulary?
Where should newsletter subscribers live — a custom post type or custom tables — and how should lists, tags and segments be modelled?
Why section/column need a text_align option separate from content alignment (and why special_heading keeps its master alignment)
Where should the converter's element-mapping table live — the shortcode docs or the AI Dev Kit? And should it be generated?
Why the AI Dev Kit's fetched folders live under assembled/
Why the Live Editor's Sections panel becomes a nested Structure navigator
Why shortcode colour defaults now follow the site's Color Presets
Converter feedback: carry the agent's got-vs-expected, and how often may it ask to send?
How should an outside agent improve the converter — fork it, or build the full site + report a fix sketch?
Where should a new shortcode live — decide by reuse scope alone, or also ask distribution intent?
Exact spacing capture: arbitrary values (pt-[40px]) instead of renumbering the scale to Tailwind
Unmapped styles: carry the source CSS class, or synthesize Custom CSS?
Why an element's content layout is a “Card” but its skin is a “Box”
Container Width means CONTENT width, not the outer box (gutter lives outside)
One card model for wc_products: drop the Classic/Slot toggle + the presence switches, add a Box Preset
Naming the badge/pill primitive: rename announcement_pill → badge
Converter translation: computed styles first, or an exhaustive Tailwind class map?
Converting a site: fix the converter's algorithm, not the output
The converter-improvement loop: how to build a section the converter can't yet map
Copyright columns align by count, not by a per-column dropdown
Post Types ships a "Get PHP code" export — the extension argues for itself by making itself removable
Relationship fields drive the multi-select option type's population modes — we did not build a new control
Removing a post type row hides content rather than deleting it — so we made removal recoverable instead of forbidding it
The deferred rewrite flush belongs on wp_loaded, not inside our own init callback
Post Types validation reports what will not register — it never blocks the save
Smooth scroll belongs to the engine, and the scroll clock is a shared loop — not a ScrollTrigger port
The GSAP snippet generator mirrors the Custom Code contract — it is not a full GSAP playground
The builder's 'motion timeline' is fixed Start/Middle/End keyframes on an auto progress source — not an editor
A dozen uploads/unysonplus-* folders, or one uploads/unysonplus/ parent?
Where do the Animated Icons toggles live — a standalone extension Settings page, or Theme Settings → Icons?
Why cross-column drag-and-drop was a small opt-in, not a new post type
"Overlay on last section" as a Footer Layout toggle — positioning only, JS-gated
Why Icon Badges get their own preset type, not a fold into Box or Image Styles
Animated (Lottie) icons: ship JSON only — .lottie is a delivery optimization, not a render one
Per-batch scatter with synced text: one Stage of scenes, not five separate galleries
Animated hand-drawn accents: two-state APNG (in → idle) with a cache-bust restart, not SVG
Is the Animated Heading shortcode redundant now that the Animation Engine has text effects?
The cinematic "camera pan" is a moving backdrop, not a camera — so we made it a Stage option
Replicating a cinematic site: live, user-replaceable elements over baked-in fidelity
How far should the Animation Engine expose GSAP — and how do we teach it?
Securing author-written JS: gate execution, not the UI
One data repo for all content libraries; presets get a browse option, not a rewrite
How does a GSAP timeline become builder options a non-coder can drive?
Should Page Builder pages show the theme's page title?
3D Gallery Motion: a nested multi-picker (via a NEW key) plus CSS-sticky scroll pinning
Why gallery card links live ON the image (attachment meta), and post-driven galleries came free
Where does a new gallery design belong — the core Gallery or the 3D Gallery?
Why portfolio display settings live in Theme Settings, bridged by one filter
Why [portfolio] grew into a rich element instead of deferring to [posts]
Why cinematic scroll pages became a Scrollytelling layout, not a new module
Whether to invest in agentic-browsing readiness — and whether to build WebMCP now
Why image treatments became a Theme Settings preset, not more Card Styles
Why extra footer bars are a filter, not per-container option files
Why footer columns got an 'Auto Width' mode outside the 12-grid
Why the page-title H1 is theme-rendered with a toggle, not a per-page shortcode
Who edits the Site Converter — and how kit users feed it back
Why Theme Settings docs are one file per tab — with every choice listed
Why the default heading scale shrank — and why line-height was the real fix
Why option-type docs are one index + a dozen deep-dives, not 52 stubs
Why 'disable text selection' is an opt-in General → Base toggle, not a new Settings tab
Why the Mega Menu column width is an inline image-picker, not the Column shortcode's responsive popover
Why popover pickers deselect on click-again instead of needing a 'None' tile
Why we're adopting React incrementally, not rewriting UnysonPlus
Why footer section dividers are now opt-in, not a default border
Why the live editor re-renders from the model to nest a column instead of moving the DOM
Why nested columns render through fw_inner_row / fw_inner_column alias shortcodes
Why nested columns are columns-in-columns (one level), not an Inner Row element
Why the off-canvas panel takes elements, not a menu-or-snippet toggle
Why option-gating pickers use a new option id instead of migrating the old scalar
Why Posts gaps consume the shared Gap Scale presets
Why Posts loads card CSS per-design, auto-detected by filename
Why the Posts read-more reuses button presets instead of duplicating the Button shortcode
Preset colors: why we keep the reference picker instead of a frozen hex
Why a shortcode's designs are a registry, not hardcoded templates
Why the testimonial quote allows safe inline HTML, not a rich editor
Why testimonial ratings render as inline SVG, not Font Awesome
Why the color picker moved to Coloris, and why opacity is opt-in
Why typography-v2 became just typography (and an alias)

Authors

Jon-Michael Lastimosa
186
Senior Web Developer

Manual

Introduction
Extensions
Blocks

Project

GitHub Org
Plugin Repo
Theme Repo

More

News
Sitemap

Authors

Jon-Michael Lastimosa