Title: NexWordX Author: SoftVoltAI Published: October 27, 2026 Last modified: October 27, 2026 --- Search plugins ![](https://ps.w.org/nexwordx/assets/banner-772x250.png?rev=3769169) ![](https://ps.w.org/nexwordx/assets/icon-256x256.png?rev=3769169) # NexWordX By [SoftVoltAI](https://profiles.wordpress.org/alamgirwp1/) [Download](https://downloads.wordpress.org/plugin/nexwordx.1.0.1.zip) * [Details](https://wordpress.org/plugins/nexwordx/#description) * [Reviews](https://wordpress.org/plugins/nexwordx/#reviews) * [Installation](https://wordpress.org/plugins/nexwordx/#installation) * [Development](https://wordpress.org/plugins/nexwordx/#developers) [Support](https://wordpress.org/support/plugin/nexwordx/) ## Description **NexWordX is a visual page builder for WordPress with a headless twist.** You design pages in WordPress with a familiar drag-and-drop editor: containers, widgets, drag and drop, responsive controls, global colours and fonts, templates, undo and redo. WordPress stays your CMS. The pages themselves are rendered by a Next.js site that you deploy anywhere, so your visitors get static, cached HTML with no theme, no PHP rendering and no page-builder scripts. #### A builder you already know * Flex and grid containers with structure presets, boxed or full width. * Widgets: heading, image, text editor, video, button, divider, spacer, Google Maps, icon, image box, icon box, star rating, image carousel, image gallery, icon list, counter, progress bar, testimonial, tabs, accordion, toggle, social icons, alert, HTML, shortcode, menu anchor, sidebar and a 3D model viewer. * Content, Style and Advanced tabs for every element: typography, backgrounds, borders, shadows, margins, padding, positioning (sticky included), hover states, responsive visibility, custom attributes. * Entrance animations and hover animations for every element. * Desktop, tablet and mobile editing with a real viewport canvas. * Global design settings (the kit): system colours and fonts, body, heading, link and button defaults, layout widths and breakpoints. * Templates: save a page or a section, insert it anywhere, import and export JSON. * A library of ready-made sections (heroes, features, about, services, numbers, pricing, testimonials, FAQ, calls to action, team, logos) to insert in one click. * Inline text editing, navigator, history, keyboard shortcuts, copy and paste between pages, paste style. * Revisions, autosave and post locking through WordPress’s own systems. #### A clear admin The **NexWordX** menu: Home, Editor, Theme Builder, Submissions, Connect Account and Upgrade (Theme Builder and Submissions show what NexWordX Pro adds there). * **Home**: the frontend connection at a glance, “Let’s start building” shortcuts( filter them by Create, Optimize and Manage), your latest NexWordX pages and a few numbers. * **Editor** opens a flyout with the screens that shape the editor: Quick Start, Settings, Tools, Templates, Role Manager, Custom Elements and System. * **Editor > Quick Start**: three steps from an empty site to pages served by Next. js, and how the parts fit together. * **Editor > Settings**: General (post types), Frontend (download, connect and test the Next.js project), Integrations (a Google Maps key), Advanced (Google Fonts, font display, data on uninstall) and Performance (Next.js image optimisation, font preconnect). * **Editor > Tools**: clear the caches and rebuild the frontend, regenerate the widget definitions, Replace URL after a move, Version Control (reinstall an earlier release from WordPress.org once NexWordX is published there), and Maintenance Mode (a “Coming soon” or “Maintenance” page for the frontend, with a bypass link for you). * **Editor > Templates**: your saved pages and sections, with Add New Template, Duplicate, categories, import and export. * **Editor > Role Manager**: per role, full access, content editing only (text, images and links of existing pages; layout and styles stay) or no access. * **Editor > Custom Elements**: what NexWordX Pro adds there (custom fonts, icon sets and code). * **Editor > System**: server, WordPress, theme, plugin and NexWordX details, to copy or download when you ask for help. Secrets are never included. * **Theme Builder** and **Submissions**: what NexWordX Pro adds there. * **Connect Account**: connect the frontend, or deploy it to Vercel from WordPress. * **Upgrade**: what NexWordX Pro adds. Nothing in this plugin is locked, limited or nagged about. #### NexWordX Pro NexWordX Pro is an optional add-on, sold separately, that works on top of this plugin. It adds the Theme Builder (header, footer, single, archive, search results and 404 templates with display conditions), a WooCommerce Builder (product, shop, cart, checkout and account templates with shop widgets), popups, the Form widget and its submissions, Pro widgets (slides, price tables, flip boxes, countdowns, animated headlines, loop grids and more), 3D and motion widgets and motion effects (scrolling and mouse effects), custom fonts, icons and code, and a premium library of designed sections and pages. Everything in this plugin works without it. #### A frontend built for speed * WordPress stores each page as structured JSON; it never generates the page HTML. * The bundled Next.js project (Settings > Frontend > Download) renders every page with React components, generates static pages, a sitemap and robots rules, and revalidates a page the moment you publish it. * SEO fields per page: title, description, canonical, robots, Open Graph image and texts. * Optional: send visitors of the WordPress site straight to the frontend. * Images are served through Next.js image optimisation from your WordPress uploads( switchable under Settings > Performance). #### Extensible * Widgets are plain PHP classes with a declarative controls API, plus a React component in the frontend. * Hooks for registering widgets and categories, and a documented REST API under` nexwordx/v1`. #### Source code The editor is a compiled JavaScript application (admin/app/build/). Its source ( TypeScript, React, Vite) ships with the plugin in source/: the editor in source/ editor/ and the renderer it shares with the frontend in source/renderer/, with the build steps in source/README.md. The Next.js frontend is included as source in frontend- template/. ### External services The plugin connects to outside services only as described here. No data is sent to SoftVoltAI. #### Your own Next.js frontend Only after you enter a frontend URL under Settings > Frontend (or deploy one from Connect Account). The frontend is your own deployment of the Next.js project that ships with this plugin; its hosting provider’s terms and privacy policy apply (for example [Vercel](https://vercel.com/legal/terms), [privacy](https://vercel.com/legal/privacy-policy), or [Netlify](https://www.netlify.com/legal/terms-of-use/), [privacy](https://www.netlify.com/privacy/)). * When you publish, update, unpublish or delete a page or post, change a menu, the global design, a theme template, the maintenance page or the settings, the plugin sends one request to `{frontend URL}/api/nexwordx/revalidate/` with the paths of the changed pages (for example `/about/`; never their content) and a shared secret in the `X-Nexwordx-Secret` header, so the frontend refreshes its cached pages. The last twenty calls are listed under Settings > Frontend. Tools > Clear caches sends the same request for every page. * When you press “Test connection”, the plugin requests `{frontend URL}/api/nexwordx/ health/`, sends an empty revalidate call to check the secret, and asks the frontend’s image optimiser for one image of your media library (its URL is sent). * When you press “Refresh frontend”, one revalidate request asks the frontend to rebuild every page. * When “Redirect visitors” is on, visitors of the WordPress site are redirected to the same address on the frontend. The frontend then reads the page data from your WordPress REST API (`/wp-json/nexwordx/ v1/`). #### Vercel Only if you enter a Vercel access token under NexWordX > Connect Account. The plugin then calls Vercel’s API (api.vercel.com) to check the token, find or create the project you name, store the frontend’s environment variables there (this site’s address, the frontend’s address and the shared secret, which Vercel keeps encrypted), upload the files of the bundled Next.js project, start deployments and read their status. “Disconnect” forgets the token; your Vercel project is never deleted. [Terms](https://vercel.com/legal/terms), [privacy](https://vercel.com/legal/privacy-policy). Vercel’s free Hobby plan is for non-commercial use. #### Your own server (install command) Only if you create an install command under NexWordX > Connect Account > Your own server and run it on your server. The plugin itself contacts no outside service for this: your server downloads the installer and the bundled Next.js project from this site, receives the frontend’s settings (this site’s address, the frontend’s address and the shared secret) with the one-time token in the command, and reports its progress back. While it installs, your server downloads Node.js from NodeSource’s package repository (deb.nodesource.com, [project](https://github.com/nodesource/distributions)), the frontend’s npm packages from the npm registry (registry.npmjs.org, [terms](https://docs.npmjs.com/policies/terms), [privacy](https://docs.npmjs.com/policies/privacy)) and, when you enter a domain, the Caddy web server from its package repository (dl.cloudsmith.io, [install guide](https://caddyserver.com/docs/install)); Caddy then requests an HTTPS certificate for your domain from Let’s Encrypt ([terms](https://letsencrypt.org/repository/), [privacy](https://letsencrypt.org/privacy/)). #### Google Fonts Only if you switch on “Google Fonts” under Settings > Advanced. The editor and the frontend then load the font families used on your pages from fonts.googleapis.com and fonts.gstatic.com, which receive the font family names and the visitor’s IP address (“Preconnect” under Settings > Performance only opens that connection earlier). [Terms](https://developers.google.com/fonts/terms), [privacy](https://policies.google.com/privacy). The plugin itself never contacts Google; the bundled list of family names is static. #### Google Maps Only if you add a Google Maps widget to a page. The frontend then embeds a map iframe from google.com/maps for the address you entered (with the API key from Settings > Integrations when you set one). [Terms](https://www.google.com/intl/en/help/terms_maps/), [privacy](https://policies.google.com/privacy). #### Video providers Only if you add a Video widget with a YouTube or Vimeo link. The frontend embeds the player from that provider, under its terms and privacy policy. #### Gravatar Only when “Show Avatars” is on under Settings > Discussion. The page data the frontend reads includes each post author’s avatar address as WordPress builds it (by default an image on secure.gravatar.com, which receives a hash of the author’s email address, and the visitor’s IP address when the image loads). [Terms](https://automattic.com/tos/), [privacy](https://automattic.com/privacy/). #### WordPress.org Only when you open NexWordX > Editor > Tools > Version Control. WordPress asks api. wordpress.org which NexWordX releases exist (the plugin’s slug is sent, at most every twelve hours), and “Reinstall” downloads the chosen release from downloads. wordpress.org. [Privacy](https://wordpress.org/about/privacy/). ### Third-party libraries The plugin ships no third-party script files of its own. The compiled editor includes its npm dependencies (React, Radix UI, Tiptap, dnd kit, Zustand and others, listed in source/editor/package.json), all under GPL-compatible licences such as MIT. The bundled Next.js project lists its npm dependencies in frontend-template/package. json; they are installed when you build the frontend. ## Screenshots [⌊The editor: widgets on the left, the page in a real viewport, the navigator on the right.⌉⌊The editor: widgets on the left, the page in a real viewport, the navigator on the right.⌉[ The editor: widgets on the left, the page in a real viewport, the navigator on the right. [⌊Content, Style and Advanced tabs with Normal and Hover states.⌉⌊Content, Style and Advanced tabs with Normal and Hover states.⌉[ Content, Style and Advanced tabs with Normal and Hover states. [⌊Global design settings: colours, fonts, body, headings, buttons and layout.⌉⌊Global design settings: colours, fonts, body, headings, buttons and layout.⌉[ Global design settings: colours, fonts, body, headings, buttons and layout. [⌊Home with the setup steps, the frontend connection status and "Let's start building".⌉⌊ Home with the setup steps, the frontend connection status and "Let's start building" .⌉[ Home with the setup steps, the frontend connection status and “Let’s start building”. [⌊Settings > Frontend: download the Next.js project, connect it and see the revalidation log.⌉⌊Settings > Frontend: download the Next.js project, connect it and see the revalidation log.⌉[ Settings > Frontend: download the Next.js project, connect it and see the revalidation log. [⌊A page served by the Next.js frontend.⌉⌊A page served by the Next.js frontend.⌉[ A page served by the Next.js frontend. ## Installation 1. Install and activate the plugin. 2. Open **NexWordX > Editor > Quick Start** for the three first steps, or **NexWordX > Home** and press **Create new page**. 3. Or edit any page or post and press **Edit with NexWordX** (in the list, in the box beside the editor, or in the admin bar). Save a draft or publish as usual. 4. To serve the pages with Next.js: open **NexWordX > Editor > Settings > Frontend**, press **Download Next.js frontend**, and deploy the project on Vercel, Netlify, Docker or any Node server with the three environment variables shown there (`NEXWORDX_WP_URL`,` NEXWORDX_SECRET`, `NEXWORDX_SITE_URL`). **NexWordX > Connect Account** can deploy it to Vercel for you, or give you one command that installs it on your own Ubuntu or Debian server. 5. Enter the frontend URL, save, and press **Test connection**. 6. Optionally switch on **Redirect visitors** so people who open the WordPress site are sent to the same page on the frontend. The frontend needs pretty permalinks (any structure except “Plain”) and must be able to reach your WordPress site. Until a frontend is connected the editor works as normal; on the WordPress site itself a NexWordX page shows a short notice to editors instead of its design. ## FAQ ### Do I need the Next.js frontend? Not to build pages. The editor, templates and settings all work inside WordPress. The frontend is what turns the pages into a fast static site; connect it when you are ready. ### Does installing the plugin install Next.js? No. WordPress runs PHP, not Node.js, so the frontend runs on a host of your choice.** NexWordX > Connect Account** sets it up for you: deploy to Vercel with an access token, or paste one command into your own server (see the next question). You can also download the project and deploy it anywhere Node.js 20 runs. ### Can I put the frontend on my own server (VPS)? Yes. Under **NexWordX > Connect Account > Your own server**, enter the domain for the frontend (point its DNS A record at the server first) and press **Create install command**. Paste the command into an Ubuntu (22.04 or newer) or Debian (12 or newer) server as root or with sudo. It installs Node.js and Caddy, builds the frontend, runs it as a system service with HTTPS for your domain, and connects this site to it; the screen follows each step. The command works once and for two hours. Without a domain the frontend runs on port 3000 of the server’s IP address over plain HTTP, for testing. ### Can I use it for a business or client site? Yes. NexWordX is GPL software with no limits on commercial use. Your hosting plan has its own terms: Vercel’s free Hobby plan, for example, is for non-commercial projects only, so a business site there needs a paid plan, or use your own server or another host. ### Does it work with my theme? The editor is independent of the theme. On the WordPress site a NexWordX page is shown by your theme with a short notice for editors (visitors get a link to the page on the frontend once one is connected); the designed page is rendered by the frontend. ### What happens to a page that already has content? Pressing “Edit with NexWordX” opens the editor with the existing content in a text widget. Nothing changes for visitors until you save in the editor; from then on the page is a NexWordX page. ### How do previews work? “Preview” in the editor opens the page on your frontend with a signed link that is valid for one hour, and updates live while you edit. WordPress’s own Preview button on a NexWordX page leads to the same frontend preview. Without a frontend the WordPress preview is used. ### Can I let some people edit only the text of pages? Yes. Under NexWordX > Editor > Role Manager, give a role “Edit content only”: its users can change the text, images and links of existing NexWordX pages, while the layout, styles, page settings, site settings and templates stay as they are. “No access” removes the editor for a role altogether. Administrators always have full access. ### How do I show a “Coming soon” page? Design a page template (Templates, or “Create a maintenance page” under NexWordX > Editor > Tools > Maintenance Mode), publish it, choose a mode and save. Every visitor of the frontend then sees that page; open the bypass link shown there to see the real site yourself. ### I moved my site to a new address. Why do images still point at the old one? Designs store the addresses of their images and links. Use NexWordX > Editor > Tools > Replace URL to replace the old address with the new one in every design (back up your database first). ### My theme has no menus. How do I build one for the navigation widget? NexWordX registers two menu locations of its own (“NexWordX frontend: header” and“ NexWordX frontend: footer”), so **Appearance > Menus** is available with every theme, block themes included (the Nav Menu widget that shows them comes with NexWordX Pro). Developers can switch this off with the `nexwordx_register_menu_locations` filter. ### Does the plugin load Google Fonts? No. Google Fonts are off by default. If you switch them on under Settings > Advanced, the editor and the frontend load the font families you use from Google’s servers. ### Can other plugins add widgets? Yes. Register a class that extends `Nexwordx_Widget_Base` on the `nexwordx_widgets_register` action, or call `nexwordx_register_widget()` with an array definition, and ship the matching React component in the frontend. ### Why is my HTML widget filtered? The HTML widget keeps the HTML WordPress allows in posts, for every user: scripts, iframes, styles and form fields are removed when you save and again when the page is built. For videos and maps use the Video and Google Maps widgets. The plugin has no field for custom CSS or JavaScript. ### Does it work on multisite? Yes. Settings, the global design, templates and the frontend connection are per site, so each site of a network connects its own frontend. ### What happens to the WordPress sitemap? While a frontend is connected, the plugin switches off WordPress’s own sitemap ( wp-sitemap.xml), because the frontend serves the sitemap of your site at its own address ({frontend URL}/sitemap.xml). Clear the frontend URL and the WordPress sitemap comes back. ### Where is the data stored? In your own database: each page keeps its design as JSON in post meta (revisioned), templates are a private post type, and global settings are options. Keys and secrets are stored encrypted. Nothing leaves your site except as described under External services. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “NexWordX” is open source software. The following people have contributed to this plugin. Contributors * [ SoftVoltAI ](https://profiles.wordpress.org/alamgirwp1/) [Translate “NexWordX” into your language.](https://translate.wordpress.org/projects/wp-plugins/nexwordx) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/nexwordx/), check out the [SVN repository](https://plugins.svn.wordpress.org/nexwordx/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/nexwordx/) by [RSS](https://plugins.trac.wordpress.org/log/nexwordx/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.1 * Security: the bundled Next.js frontend now requires Next.js 16.4.3, React 19.3.1 and sharp 0.35.5 or newer. These versions fix remote code execution and denial- of-service issues reported in Next.js and in the image libraries sharp uses. If your frontend is already deployed, download it again (NexWordX > Editor > Settings > Frontend) or update next, react, react-dom and sharp in your copy and redeploy. #### 1.0.0 * First release. ## Meta * Version **1.0.1** * Last updated **2 days ago** * Active installations **Fewer than 10** * WordPress version ** 6.4 or higher ** * Tested up to **7.1.4** * PHP version ** 7.4 or higher ** * Tags * [drag-and-drop](https://wordpress.org/plugins/tags/drag-and-drop/)[headless](https://wordpress.org/plugins/tags/headless/) [next.js](https://wordpress.org/plugins/tags/next-js/)[page builder](https://wordpress.org/plugins/tags/page-builder/) [visual editor](https://wordpress.org/plugins/tags/visual-editor/) * [Advanced View](https://wordpress.org/plugins/nexwordx/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/nexwordx/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/nexwordx/reviews/) ## Contributors * [ SoftVoltAI ](https://profiles.wordpress.org/alamgirwp1/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/nexwordx/)