Vue 3 Click & Drop Page Builder. Power your vision and build impressive pages. The web builder for stunning pages. Enable users to design and publish modern pages at any scale. Build responsive pages like listings, jobs or blog posts and manage content easily.
pbx-
)A Vue 3 page builder component with drag-and-drop functionality for creating dynamic web pages.
Create and enhance digital experiences with Vue on any backend.
Experience the power and simplicity of the Vue Website Page Builder in action.
Try the live demo to explore real-time visual updates and smooth content management.
Play around with the Page Builder
If you’re a Vue 3 developer, this builder feels right at home. It installs quickly via npm and supports full customization through props and configuration objects. You can even set specific user settings like image, name, theme, language, company logo, and autosave preferences, making it a personalized experience for every user.
A lightweight and minimalist Page Builder with an elegant and intuitive design, focused on simplicity and speed.
Build responsive pages like listings, jobs, or blog posts and manage content easily.
Easy setup and instant productivity.
Follow the Quick Start guide to begin building with just a few simple steps.
The web builder for stunning pages. Enable users to design and publish modern pages at any scale.
npm install @myissue/vue-website-page-builder
A Page Builder designed for growth. Build your website pages with ready-made components that are fully customizable and always responsive, designed to fit every need. A powerful Page Builder for growing merchants, brands, and agencies. And it is totally free.
Includes:
The Page Builder is packed with features:
From solo freelancers to fast-growing startups and established enterprises, the Page Builder is trusted by teams everywhere. With its intuitive click-and-drop editor, real-time visual editing, and a rich library of reusable components, you can turn ideas into polished pages in minutes. Built for merchants, brands, and agencies, it empowers anyone to create high-impact content.
Find everything you need to get started, configure, and master the Vue Website Page Builder.
This section covers installation, requirements, quick start, advanced usage, and integration tips—so you can build and launch pages with confidence.
Please note that these instructions assume you have Node.js installed.
Make sure to install the dependencies:
# npm
npm install
# pnpm
pnpm install
# yarn
yarn install
# bun
bun install
Get up and running with the Vue Website Page Builder in just a few minutes.
This section walks you through the essential steps—from installation to rendering your first page—so you can start building beautiful, dynamic content right away.
To get started with the Page Builder, follow these steps:
main.ts
or main.js
). This sets up the shared builder instance for your entire app.getPageBuilder()
composable.main.js
, main.ts
, or root component to ensure proper styling and automatic icon loading.import { createApp } from 'vue'
import App from './App.vue'
import { pageBuilder } from '@myissue/vue-website-page-builder'
import '@myissue/vue-website-page-builder/style.css'
// Use the Page Builder plugin
const app = createApp(App)
app.use(pageBuilder)
app.mount('#app')
Note:
You only need to import the CSS file once. If you have already imported it in your app entry, you do not need to import it again in individual components.
Note
The Page Builder is implemented as a singleton service. This ensures that all page-building logic and state are managed by a single, shared instance throughout your application.
By always accessing the shared instance, you avoid creating multiple, isolated copies of the builder. This prevents data inconsistencies, synchronization issues, and unpredictable behavior. All components and modules interact with the same centralized service, ensuring that updates and state changes are reflected everywhere in your application.
Ensure the following configuration options are set:
formType
(required):
Indicates whether you are creating or updating a resource. This is used to retrieve the correct content from local storage.
formName
(required):
Specifies the resource type (for example, article
, jobPost
, store
, etc.).
<script setup>
import { PageBuilder, getPageBuilder } from '@myissue/vue-website-page-builder'
import '@myissue/vue-website-page-builder/style.css'
const configPageBuilder = {
updateOrCreate: {
formType: 'create',
formName: 'article',
},
}
const pageBuilderService = getPageBuilder()
const result = await pageBuilderService.startBuilder(configPageBuilder)
console.info('You may inspect this result for message, status, or error:', result)
</script>
<template>
<PageBuilder />
</template>
pbx-
)All CSS classes generated or processed by the Page Builder—including Tailwind utilities and your custom classes—are automatically prefixed with pbx-
. This ensures the builder’s styles never conflict with your app’s existing CSS or Tailwind setup.
This prevents global styles from leaking into the builder and vice versa, which is crucial for embedding the builder into larger apps or white-label environments.
How does this affect you?
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.
Note:
Simply import the builder’s CSS file once in your project. All builder styles are namespaced, so there is no risk of style conflicts.
You can use the Page Builder to generate HTML and render it in any frontend framework, such as React, Nuxt, or even server-side apps.
To ensure your content is styled correctly, simply install the Page Builder package in your target project and import its CSS file. All builder and Tailwind-prefixed styles will be applied automatically.
// Import the builder's CSS file once in your project
import '@myissue/vue-website-page-builder/style.css'
This will apply all necessary styles to any HTML output from the builder, even if you render it with dangerouslySetInnerHTML
, v-html
, or similar methods.
Example (React):
import '@myissue/vue-website-page-builder/style.css'
function MyPage({ html }) {
return <div dangerouslySetInnerHTML={{ __html: html }} />
}
Example (Nuxt/Vue):
<script setup>
import '@myissue/vue-website-page-builder/style.css'
</script>
Then use v-html
to render the HTML.
Note:
You do not need to import any Vue components if you only want to render the HTML. Just import the CSS file.
The example below demonstrates the setup to start building pages, with additional options available for customization and branding.
Your configPageBuilder
object can include:
formType
(required):formName
(required):article
, jobPost
, store
, etc.). This is especially useful for platforms supporting multiple resource types, allowing the builder to manage layouts and storage for each resource uniquely.resourceData
(optional):title
, id
).userForPageBuilder
(optional):name
and image
) to display the logged-in user’s details in the builder.pageBuilderLogo
(optional):userSettings
(optional):brandColor
(optional):settings
config).<script setup>
import { getPageBuilder } from '@myissue/vue-website-page-builder'
const configPageBuilder = {
updateOrCreate: {
formType: 'create', // Set to 'create' or 'update'
// Set the resource type for better local storage and multi-resource support
formName: 'article',
},
resourceData: {
title: 'Demo Article',
id: 1,
},
userForPageBuilder: { name: 'John Doe', image: '/jon_doe.jpg' },
pageBuilderLogo: {
src: '/logo/logo.svg',
},
userSettings: {
theme: 'light',
language: 'en',
autoSave: true,
},
settings: {
brandColor: '#DB93B0',
},
}
// Retrieve Page Builder service instance
const pageBuilderService = getPageBuilder()
const result = await pageBuilderService.startBuilder(configPageBuilder)
console.info('You may inspect this result for message, status, or error:', result)
</script>
<template>
<PageBuilder />
</template>
The Page Builder automatically saves all changes to the browser’s local storage. Every time you add, edit, or delete a component, your progress is preserved—even if you close the browser or navigate away.
The builder’s auto-save ensures that the data in local storage always reflects the latest state of your page. You can retrieve this data at any time for form submission, publishing, or preview.
To get the most up-to-date content, use the same resourceData
(such as formType
and formName
) that was used when saving. If these values do not match, the builder may not find the expected content.
Example:
const configPageBuilder = {
updateOrCreate: {
formType: 'create',
formName: 'article',
},
}
Call this logic when you need to submit or save the builder’s output—for example, when the user clicks “Save” or “Publish.” The code below safely retrieves and parses the latest data from local storage, handling errors and assigning the results to your form fields.
<script setup>
import { getPageBuilder } from '@myissue/vue-website-page-builder'
const configPageBuilder = {
updateOrCreate: {
formType: 'create',
formName: 'article',
},
}
// Retrieve Page Builder service instance
const pageBuilderService = getPageBuilder()
await pageBuilderService.startBuilder(configPageBuilder)
const storedComponents = pageBuilderService.getSavedPageHtml()
yourForm.content = storedComponents
</script>
After successfully creating or updating a resource (such as a post, article, or listing) using the Page Builder, it is important to clear the DOM and the builder’s draft state, as well as remove the corresponding local storage entry. This ensures that old drafts do not appear the next time the builder is opened for a new or existing resource.
You can reset the Page Builder’s live DOM, builder state, and clear the draft with:
await pageBuilderService.handleFormSubmission()
Always call this method after a successful post or resource update to ensure users start with a fresh builder the next time they create or edit a resource.
The Page Builder makes it simple to load previously published content—including both your page’s global styles and all components—from any backend source, such as your database or API.
If you have previously saved or published HTML content (for example, from your database), you can easily restore both the global page styles (classes, inline styles) and all builder components for seamless editing.
Recommended Workflow:
Parse your saved HTML using the builder’s helper method to extract both the components and the global page settings:
// yourPageHTML: the full HTML string previously saved from the builder
const { components, pageSettings } = pageBuilderService.parsePageBuilderHTML(yourPageHTML)
Pass pageSettings
directly in your config object, and pass the components
array as the second argument to startBuilder
:
<script setup>
import { getPageBuilder } from '@myissue/vue-website-page-builder'
// Retrieve the Page Builder service instance
const pageBuilderService = getPageBuilder()
// Parse your saved HTML to extract both components and global page settings
const { components, pageSettings } = pageBuilderService.parsePageBuilderHTML(yourPageHTML)
// Prepare the config, passing pageSettings directly
const configPageBuilder = {
updateOrCreate: {
formType: 'update', // important: set to update
formName: 'article',
},
// pass directly, not nested
pageSettings: pageSettings,
}
// Start the builder with both config and components
const result = await pageBuilderService.startBuilder(configPageBuilder, components)
console.info('You may inspect this result for message, status, or error:', result)
</script>
<template>
<PageBuilder />
</template>
Note:
- Each component’s
html_code
must be wrapped in a<section>...</section>
tag. This is how the Page Builder defines and separates individual components.- Always pass
pageSettings
directly in the config object (not as{ pageSettings: { pageSettings } }
).- Set
formType: 'update'
to ensure the builder loads your provided content for editing.
This approach ensures your users can seamlessly restore and edit previously published content—including all global styles and layout—providing a smooth and reliable editing experience for existing pages.
The Page Builder automatically checks for unsaved drafts in local storage for the current resource.
If a draft is found, users are prompted to either continue where they left off or use the version loaded from your backend.
formType
(required):create
or update
in the updateOrCreate
config, depending on your use case.formName
(required):article
, jobPost
, store
, etc.) in the updateOrCreate
config. This is especially important if your platform supports multiple resource types. By providing a unique name, the Page Builder can correctly manage layouts and drafts for each resource, allowing users to pick up where they left off.<script setup>
import { getPageBuilder } from '@myissue/vue-website-page-builder'
const configPageBuilder = {
updateOrCreate: {
formType: 'update',
formName: 'article',
},
}
const result = await pageBuilderService.startBuilder(configPageBuilder)
console.info('You may inspect this result for message, status, or error:', result)
</script>
<template>
<PageBuilder />
</template>
You can easily use the Page Builder inside a modal or dialog.
To allow users to close the modal from inside the builder, use the showCloseButton
prop and listen for the @handleClosePageBuilder
event:
<script setup>
import { ref } from 'vue'
import { PageBuilder } from '@myissue/vue-website-page-builder'
const showModal = ref(true)
function closePageBuilder() {
showModal.value = false
}
</script>
<template>
<Modal v-if="showModal" @close="showModal = false">
<PageBuilder :showCloseButton="true" @handleClosePageBuilder="closePageBuilder" />
</Modal>
</template>
To allow users to use the Publish button from inside the builder, use the showPublishButton
prop and listen for the @handlePublishPageBuilder
event.
Note:
When the Publish button is clicked, the Page Builder will automatically save the latest changes to local storage before emitting the@handlePublishPageBuilder
event. This ensures you always receive the most up-to-date content.
<script setup>
import { getPageBuilder, PageBuilder } from '@myissue/vue-website-page-builder'
const pageBuilderService = getPageBuilder()
const handlePublish = () => {
// Retrieve the latest HTML content (saved by the builder)
const latestHtml = pageBuilderService.getSavedPageHtml()
// Submit, publish, or process the content as needed
// e.g., send latestHtml to your API or update your form
}
</script>
<template>
<PageBuilder :showPublishButton="true" @handlePublishPageBuilder="handlePublish" />
</template>
:showPublishButton="true"
— shows a publish button in the Page Builder toolbar.@handlePublishPageBuilder="handlePublish"
— emits after the builder auto-saves, so you always get the latest content.Tip:
You can name your handler function anything you like. This pattern makes it easy to embed the builder in modals, dialogs, or overlays in any Vue app.
:showPublishButton="true"
— shows a publish button in the Page Builder toolbar.@handlePublishPageBuilder="yourMethod"
— emits when the close button is clicked, so you can close your modal.Tip:
You can name your handler function anything you like.
This pattern makes it easy to embed the builder in modals, dialogs, or overlays in any Vue app.
The Page Builder allows you to define and update global styles for the main wrapper (#pagebuilder
) at any time. These settings control the overall appearance, including font family, text color, background color, and more. Whether you set them initially in your config or update them dynamically at runtime, your changes are instantly reflected across all sections.
Use the pageSettings
config to apply custom CSS classes and inline styles to the Page Builder’s main wrapper.
The Page Builder renders all components wrapped inside a single parent container, <div id="pagebuilder">
.
You can pass global CSS classes
and style
to this wrapper by adding a pageSettings
object in your config:
const configPageBuilder = {
// other config options...
pageSettings: {
classes: 'max-w-screen-lg mx-auto px-4 bg-white',
style: {
backgroundColor: 'red',
border: '6px solid yellow',
},
},
} as const
You have full control over the page’s appearance at any time—instantly override or clear global styles for the entire page, ensuring a seamless and dynamic user experience.
Export the entire page as a standalone HTML file. This includes all sections, content, and applied styles, making the file ready for use or integration elsewhere.
To ensure images render properly after export, you must specify a URL prefix in your Page Builder configuration. This prefix will be prepended to all relative image URLs during the export process.
const configPageBuilder = {
imageUrlPrefix: 'https://your-domain.com/uploads/',
// other config options...
} as const
If you want to use your own components—whether custom-designed or tailored to your application’s needs—you can inject them directly into the builder.
By default, the Page Builder does not include a built-in media library.
This is intentional—without a custom media library, layout components that rely on images (such as Image Blocks, Hero Sections, and similar) are disabled by default. Only helper components like containers, headings, text, and buttons are available in this state.
You may extend the Page Builder by adding your own media library.
Inject your media library component easily to tailor the builder to your application’s needs.
📚 Custom Components Setup Guide
Learn how to create and integrate your own components step by step.
Easily add Unsplash image search to your media library modal—just like in the demo!
A code example is provided so you can copy-paste to get started.
See the full step-by-step guide and working demo code here:
📚 Unsplash Integration Guide
The Page Builder comes with a growing collection of built-in components, including both layout and helper components. These defaults are continuously improved and expanded.
📚 Custom Components Setup Guide
Learn how to create and integrate your own components step by step.
If fonts or Material Icons are not displaying correctly, verify that:
CSS Import: You are importing the CSS file:
import '@myissue/vue-website-page-builder/style.css'
The Page Builder is designed as a modular, state-driven editor for dynamic page content. Its architecture separates configuration, state management, and DOM interaction, ensuring flexibility and maintainability.
The Page Builder is designed to be easy to use and flexible for any web project. Here’s how it works behind the scenes:
Configuration First:
When you start the builder, you pass in your configuration (such as what type of page you’re building, user info, branding, and any existing content).
The builder saves this configuration immediately—even if the editing interface (DOM) isn’t loaded yet. This means you can safely set up the builder in advance, and it will be ready as soon as the editor appears on the page.
Loading Content:
If you have existing content (like a published page), the builder loads it so you can keep editing. If not, you start with a blank page.
Editing Experience:
As you add, move, or edit components (like text, images, or sections), the builder keeps everything in sync—both in the app’s memory and in your browser’s local storage. This means your work is always saved, even if you close the browser.
In short:
The Page Builder handles all the technical details of editing, saving, and loading pages, so your users can focus on creating great content—without worrying about losing their work or dealing with complicated setup.
If you discover a security vulnerability, please send us a message.
If you have any questions or if you’re looking for customization, feel free to connect with our developer.
Suggestions or any issues you encounter while using this app. Feel free to reach out.
We would greatly appreciate it if you could star the GitHub repository. Starring the project helps to boost its visibility.