Опис
The plugin channels the wind of Tailwind CSS into a fast, predictable page builder for WordPress.
How it works
- Every page you build is compiled to a single static CSS file with a content hash, served from the uploads directory. No inline styles, no runtime style injection, no database queries for CSS.
- The editor offers closed-set, token-driven controls (spacing, colors, typography, effects) instead of an infinity field of arbitrary CSS classes. This keeps the design system coherent and the generated CSS small.
- Frontend output is plain markup: zero JavaScript is loaded for layout blocks. Interactive blocks (carousels, tabs, accordions, forms) ship tiny, code-split ES modules that load only when actually present on the page.
Highlights
- Visual editor: drag & drop, inline text editing, device preview, undo/redo, layers and pages tabs.
- 91 blocks out of the box: layout primitives, content widgets, full forms with private submission storage, overlays (popup, drawer, offcanvas, cookie banner), carousels, galleries, embeds, and dynamic WordPress parts.
- Theme system: design tokens (palette, type scale, spacing, radius) applied across every block, with light/dark variants.
- Entrance animations, sticky effects and scroll-driven motion, compiled to static CSS.
- Convert existing Gutenberg posts to builder pages with one click from the editor header.
- Built-in form submissions stored privately in WordPress.
- Fully translated interface: English, Italian, German, Spanish, French and Brazilian Portuguese.
- No Google Fonts by default — the system font stack or your local fonts only.
Who is it for?
Site builders and agencies who love Tailwind but need a visual editor their clients can use, and performance-minded developers who do not want a builder that ships megabytes of CSS and JS on every page.
Постављање
- In your WordPress admin, go to Plugins > Add New > Upload Plugin.
- Upload the ggally-page-builder zip file and activate it.
- Click the GG-Builder menu in the admin sidebar, or open any post or page and choose „Edit with GG“.
ЧПП
-
Do I need to know Tailwind CSS?
-
No. Tailwind is the engine under the hood; the interface uses plain-language, closed-set controls. Tailwind experts will feel at home because the vocabulary maps 1:1 to Tailwind utilities.
-
Why does my site not load any frontend JavaScript?
-
That is by design. Each page’s styling is compiled into one static, content-hashed CSS file served from the media uploads. Only interactive blocks load small JS modules, and only when they are actually on the page.
-
Can I use arbitrary custom CSS classes?
-
The normal control path intentionally prevents arbitrary classes to keep output maintainable. An expert „code mode“ channel exists for advanced use with a rebuild step.
-
How is the CSS compiled?
-
The Tailwind CSS compiler is bundled as JavaScript and runs inside your own browser tab while you save in the editor. Nothing is ever downloaded or executed on your server; the compiled result is stored as a static CSS file in your media library and linked from the page.
-
Does it work with any theme?
-
Yes. The plugin renders pages independently of the active theme, using its own block markup and compiled stylesheets.
-
Which languages are included?
-
English (source), Italian, German, Spanish, French, Brazilian Portuguese. The interface follows the user’s WordPress profile language.
-
Does the plugin call external services?
-
The plugin is fully self-contained at runtime: no third-party CDN, no tracking, and the frontend never requests anything from us. The one network operation is opt-in: after activation, the plugin shows a Setup screen that explains and asks the administrator to confirm the one-time download of the official, version-pinned
tailwindcsscommand-line compiler (v4.3.3). Until it is confirmed, the download never happens and the plugin keeps working with its bundled base stylesheet directly from its official GitHub releases, verifies its published SHA-256 checksum, and caches it locally inwp-content/blocky-engine/(outside the web-served uploads folder). The binary is used only as a local build tool while the administrator saves or builds, never for site visitors, and the download happens once per server. This is the same compiler Tailwind Labs ships for everyone; pinning plus checksum verification means the pinned compiler cannot be silently switched to different code.
Рецензије
Нема рецензија за овај додатак.
Сарадници и градитељи
„GG-Ally Page Builder“ је софтвер отвореног кода. Следећи људи су допринели овом додатку.
Сарадници
Преведите „GG-Ally Page Builder“ на свој језик.
Заинтересовани сте за развој?
Прегледајте кôд, погледајте SVN складиште или се претплатите на дневник развоја преко RSS-а.
Дневник измена
0.1.6
- Textual: Description, FAQ and screenshots now refer to „the plugin“/“the builder“ instead of GG-Ally, which is the author’s business name, not the plugin name. No functional changes.
0.1.5
- Security: rendered frontend HTML now passes through a final wp_kses() gate (output escaping is additionally applied per value during rendering).
- Security: the submissions view link nonce is sanitized before verification.
0.1.4
- Compliance: all per-block inline and tags removed; interactive block
behaviour (tabs, carousels, hotspots, countdown, before/after, animated headline,
theme toggle) now runs from a single script loaded through wp_enqueue_script, and the
marquee keyframes moved to the enqueued stylesheet. - Admin: the submissions detail view link carries a nonce and the view is only honoured
with a valid nonce check. - Prefixes: form-entry post type and API rate-limit transient renamed to a longer
prefix (one-time migration of existing entries on update); API keys keep accepting
previously issued prefixes.
0.1.3
- REST: library page creation/deletion now require edit_pages/delete_pages (previously only post-level capabilities were checked for page actions).
- REST: saved patterns read/write require manage_options (site-wide content).
- Hardening: third-party hook output in the hook-block renderer is filtered through wp_kses_post.
- i18n: removed the last runtime gettext call with a variable argument; dynamic strings are resolved through the core translation filter and exposed for translators via the literal catalog.
0.1.1
- Bundled pattern library: 5 starter patterns, save-your-own patterns, self-hosted storage.
- WooCommerce subset: product grid, featured product, product categories (active only when WooCommerce is enabled).
- Icon library with self-hosted SVG assets.
- Review fixes: activation/deactivation hooks against the main plugin file, literal gettext call sites, plugin_dir_url-based asset URLs.
0.1.0
- First public release.
- Visual editor with 91 blocks, theme tokens, device preview, undo/redo.
- Static CSS compiler (content-hashed files, no inline styles).
- Entrance animations, sticky/scroll effects.
- Gutenberg conversion, form submissions, i18n (EN/IT/DE/ES/FR/PT-BR).