| 开发者 | alamgirwp1 |
|---|---|
| 更新时间 | 2026年11月21日 04:02 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
nexwordx/v1.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.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.
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.
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.
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.
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.
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.
"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.
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.
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.
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).
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.
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.
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.
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.
Yes. Settings, the global design, templates and the frontend connection are per site, so each site of a network connects its own frontend.
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.
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.