@myissue/vue-website-page-builder 3.4.15 → 3.4.17

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -162,7 +162,7 @@ The Page Builder is packed with features:
162
162
  - **YouTube Videos**: Integrate video content smoothly.
163
163
  - **Download HTML**: Export the entire page as a standalone HTML file.
164
164
  - **Global Page Styling**: Instantly define, update, or clear global styles for the main page wrapper at initialization or dynamically at runtime. Gain full control over fonts, colors, backgrounds, and more for a dynamic user experience.
165
- - **Tailwind Support**: Fully compatible with Tailwind CSS (with automatic class prefixing to avoid conflicts).
165
+ - **Tailwind Support**: Fully compatible with Tailwind CSS (with automatic class prefixing to avoid conflicts). Tailwind installation is not required for the Page Builder to work.
166
166
  - **Scoped Styles**: To ensure clean and predictable styling, the builder uses scoped style isolation. There is no risk of style conflicts between the builder and your app.
167
167
  - **HTML Editor**: Access and edit raw HTML directly for full customization and developer-level control.
168
168
 
@@ -311,6 +311,8 @@ This prevents global styles from leaking into the builder and vice versa, which
311
311
 
312
312
  When a user adds a component into the page builder, all classes from that component are automatically prefixed with `pbx-` (e.g., `pbx-button`, `pbx-container`) to ensure style isolation and avoid conflicts.
313
313
 
314
+ Tailwind installation is not required. The page builder ships with prefixed utility classes to ensure there are no naming conflicts. If you wish to use Tailwind in your own application, you may install and configure it as usual without interfering with the page builder.
315
+
314
316
  > **Note:**
315
317
  > Simply import the builder’s CSS file once in your project. All builder styles are namespaced, so there is no risk of style conflicts.
316
318