=== Holographic Page Builder ===
Contributors: holographicplugins, holo-alan
Tags: page builder, visual editor, landing page, layout, editor
Requires at least: 6.4
Tested up to: 7.0
Requires PHP: 8.1
Stable tag: 0.1.117
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

A lightweight visual page builder for WordPress that focuses on clean front-end HTML and fast pages.

== Description ==

Holographic Page Builder adds HoloEdit, a visual editor for WordPress pages and posts. It is designed for site owners and developers who want the speed of clean server-rendered output without the deep wrapper markup, public editor scaffolding or heavy front-end assets often produced by larger visual builders.

Layouts are stored as structured JSON in post meta and rendered by PHP on the server. HoloEdit loads editor assets only in the admin editor and loads front-end assets only when the rendered page needs them.

A simple heading can render as a simple heading. Layout containers are only rendered when the layout requires them.

= Main benefits =

* Clean, minimal front-end HTML.
* Server-side rendering.
* Conditional front-end CSS and JavaScript.
* No public editor interface markup.
* No large front-end framework.
* Structured JSON layout storage.
* Visual editing without unnecessary nested builder wrappers.
* Safe Rich Text source editing for allowed HTML.
* Import, export, duplicate, preview and restore tools for HoloEdit layouts.
* Converter tool for supported builder layouts, shortcode layouts, block layouts and classic content.

= Included widgets =

* Heading.
* Rich Text.
* Image.
* Simple Gallery.
* Button.
* Video.
* Divider.
* Spacer.
* Icon List.
* Accordion.
* Tabs.
* Shortcode.
* Layout.

= How HoloEdit works =

After activation, supported post types show an Edit In HoloEdit action for users with the correct capability. When a page or post is edited with HoloEdit, the visual layout is saved to that item as HoloEdit layout data.

On the public page, HoloEdit replaces the normal content only for pages or posts that have HoloEdit enabled. Other content continues to use the normal WordPress output path.

= Converter =

The Converter screen can detect supported source layout data and create a HoloEdit layout for the selected page or post. The source layout data is left in place so you can review the result before deciding what to keep.

The converter is intended as a clean migration aid. Complex third-party builder designs may need manual checking after conversion because different builders store layouts and styling in different ways.

= Security and permissions =

HoloEdit uses WordPress capabilities and nonces for editor actions, layout saves, imports, exports, restores, duplicates and converter actions.

Rich Text accepts safe HTML. Script tags, style tags, PHP and executable code are not accepted by HoloEdit input fields.

= External services =

Holographic Page Builder does not send layout data to an external service. It does not require an account with a third-party service.

= Data stored =

HoloEdit stores layout data in post meta on the edited page or post. It also stores layout revision data used by the restore tools. The plugin does not create custom database tables.

= Uninstall =

When the plugin is uninstalled through WordPress, HoloEdit options and HoloEdit post meta are removed.

== Installation ==

1. Upload the plugin ZIP through Plugins > Add New > Upload Plugin.
2. Activate Holographic Page Builder.
3. Open a supported page or post in the WordPress admin area.
4. Choose Edit In HoloEdit.
5. Build the layout, save it, then preview the public page.

== Frequently Asked Questions ==

= Does HoloEdit replace the WordPress editor automatically? =

No. A page or post uses HoloEdit output after it has been opened and saved in HoloEdit.

= Does HoloEdit load editor code on public pages? =

No. Editor code is for the admin editor only. Public pages receive only the front-end assets needed by the widgets used on that page.

= Does HoloEdit output clean HTML? =

Yes. The renderer outputs the minimum structure needed for each widget and layout. A single heading does not get wrapped in builder scaffolding.

= Can I paste HTML into Rich Text? =

Yes. Rich Text accepts safe HTML in the source box. Script tags, style tags, PHP and executable code are removed.

= Can HoloEdit help migrate existing builder pages? =

Yes. The converter auto-detects supported source layouts, creates a HoloEdit layout on the same page or post, and leaves the source data in place for review.

= Does HoloEdit use external services? =

No. HoloEdit does not send layout data to external services and does not require an external account.

= What happens if I deactivate HoloEdit? =

The plugin stops replacing enabled content with HoloEdit output. The saved HoloEdit layout data remains in the database unless the plugin is uninstalled.

== Screenshots ==

1. HoloEdit visual editor with page title controls, live canvas, widget panel and settings panel.

== Changelog ==

= 0.1.117 =
* Rebuilt the WordPress.org submission package with the standard plugin root folder and slug-only ZIP filename.
* Expanded the readme with complete usage, data, permissions, converter, external-service and uninstall information.

= 0.1.116 =
* Split layout state, preview and revision helpers out of the main rendering trait for easier review.
* Kept renderer behaviour unchanged while reducing the large rendering file warning.

= 0.1.115 =
* Fixed additional nearby capability-context checks for converter and restore save paths.
* Adjusted preview output escaping so Plugin Check can identify the escaping call.

= 0.1.114 =
* Removed arbitrary styling and executable source insertion paths for WordPress.org review.
* Rich Text and legacy saved HTML now accept safe HTML only.
* Escaped HoloEdit preview title and rendered content at WordPress filter return boundaries.

= 0.1.112 =
* Completed a final review pass for layout editing, preview, restore, converter access and dashboard visibility checks.
* Tightened HoloEdit capability checks around layout editing actions without changing supported user roles.
* Made the front-end stylesheet load only when the rendered HoloEdit output needs it.

= 0.1.111 =
* Split the converter into smaller focused components for easier review.
* Kept source-builder conversion support while avoiding short-prefix third-party meta key false positives.
* Reduced the main plugin controller size by moving shared support helpers into a dedicated trait.

= 0.1.110 =
* Rebranded the migration tool as Converter.
* Added auto-detection for supported builder and shortcode-based layout sources.
* Kept existing conversion behaviour while expanding clean HoloEdit layout conversion paths.

== Upgrade Notice ==

= 0.1.117 =
This version updates the submission package and readme documentation without changing page output.
