WP Manifestindependent plugin directory
manifest / builders / olobuild

Olobuild

Builder professionale per Wordpress

by Claudio Vinco · github.com/claudiovinco/olobuild · website

0stars
0forks

Install

No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:

wp plugin install https://github.com/claudiovinco/olobuild/archive/refs/heads/main.zip

Professional holonic page builder for WordPress with a drag & drop tile grid system.

Description

Olobuild is a professional page builder that lets you design pages, headers and footers visually on a grid, by dragging and dropping ready-made "tiles" (sections, sliders, cards, charts, maps, galleries, forms and more). It ships with a global style system (colors, typography, spacing) so every tile stays part of one consistent design family.

Key features

  • Visual drag & drop builder on a responsive grid
  • 50+ content tiles (hero, slider, gallery, cards, pricing, timeline, accordion, charts, maps, forms, mega menu…)
  • Global design tokens: colors, self-hosted web fonts, spacing scale, border & radius system
  • Reusable headers, footers and global widgets with display conditions
  • Entrance/scroll animations, hover effects and parallax
  • Built-in stock media search (optional, see External services below)
  • Newsletter manager, contact form handler and SEO tools

All processing happens on your own site. Olobuild does not phone home and does not collect any usage data or analytics about you.

External services

Olobuild can connect to a number of optional third-party services. None of them is contacted unless you explicitly enable the related feature or enter the corresponding API key. The following list documents what is sent, when, and to whom.

Stock media search (WordPress admin only, when you open the Media Search panel or a tile media picker, and only if you configured the provider's API key):

AI assistant (WordPress admin only, only if you enter the provider's API key):

Theme library previews (WordPress admin only — Theme Importer / setup wizard):

  • olotheme.com — the preview thumbnails of the starter themes are loaded from https://olotheme.com/olobuild-library/ so they don't have to be bundled in the plugin (keeps it lightweight). Only an image request for the theme you are viewing is made; no personal data is sent. The base URL is filterable via the olobuild_library_url hook. The template content itself ships inside the plugin, so importing a theme works even without this service. Terms & Privacy: https://olotheme.com/

Front-end services (only on pages where you use the related tile/feature):

Marketing & SEO integrations (only if you configure them):

  • Mailchimp, HubSpot, ActiveCampaign, ConvertKit, Brevo — form submissions are forwarded to the list/CRM you configure. Data sent is the form data submitted by the visitor.
  • Bing IndexNow — if enabled, notifies search engines of new/updated URLs. Sends the URL of the changed content. More info: https://www.indexnow.org/

API keys for stock media providers can also be defined as constants in wp-config.php: OLO_UNSPLASH_API_KEY, OLO_PEXELS_API_KEY, OLO_PIXABAY_API_KEY.

Third-party libraries

Olobuild bundles the following open-source libraries (all GPL-compatible), shipped locally under assets/vendor/ — no library is loaded from a CDN:

  • UIkit 3 (MIT)
  • Leaflet + Leaflet.markercluster (BSD-2-Clause / MIT)
  • Chart.js (MIT)
  • lottie-web (MIT)
  • html2canvas (MIT)
  • PDF.js (Apache-2.0)
  • Pannellum (MIT)
  • StPageFlip (MIT)

Development

The Olobuild admin builder is a single-page application written in Vue 3 and bundled with Vite. The shipped file assets/js/builder.js (and the chunks under assets/js/chunks/) is a compiled, minified production bundle. The complete, human-readable source code and the build tooling are published in the plugin's public repository:

  • Source repository: https://github.com/claudiovinco/olobuild
  • The src/ directory contains the Vue/SCSS sources; package.json and the vite.config*.js files define the build.
  • To rebuild from source: run npm install, then build with Vite (node node_modules/vite/bin/vite.js build). The admin-settings and theme-picker bundles use their own Vite configs — see the repository README for the exact commands.

Nothing is obfuscated: the minification is standard production bundling, fully reproducible from the sources above.

Installation

  1. Upload the olobuild folder to /wp-content/plugins/, or install the ZIP from Plugins → Add New → Upload.
  2. Activate the plugin through the Plugins menu in WordPress.
  3. Open Olobuild in the admin menu to run the setup wizard and start building.

Frequently Asked Questions

Does Olobuild send my data anywhere?

No. Olobuild does not track you and does not phone home. It only contacts the optional third-party services listed under External services, and only when you enable the related feature or enter an API key.

Are Google Fonts GDPR-friendly?

Yes. Google Fonts are self-hosted: the font files are downloaded once by your server and then served from your own site, so visitors never connect to Google's servers.

Can I use my own stock media API keys?

Yes. Enter them in Olobuild settings, or define them as constants in wp-config.php (OLO_UNSPLASH_API_KEY, OLO_PEXELS_API_KEY, OLO_PIXABAY_API_KEY).

Changelog

1.4.385

  • Hero unification: the Hero tile gains a full scene system (media background, gradient veil, radial glow, arch mask, photo frame, ghost watermark), an optional sub-fold module (media strip, search bar, product mockup, chat window) and 5 blueprint presets; Hero Split gains selectable right panels (showcase cards, media with corner badge, cover with audio player).
  • The tile palette now offers 2 hero tiles instead of 19: 12 legacy heroes were absorbed (saved templates keep rendering unchanged) and 5 signature heroes moved to the Blocks library.
  • New explicit "Convert to Hero" action in the inspector maps a legacy hero tile to the canonical one (per tile, undoable, never automatic).
  • Fix: added the missing str_ends_with() polyfill — PHP 7.4 on WordPress < 6.0 could fatal on the Button tile and on stock-media downloads.
  • Build chain upgraded to Vite 8 (Rolldown) and Pinia 3; removed unused dependencies; Sass moved from @import to @use; repository hygiene.
  • Full commit-level changelog: https://github.com/claudiovinco/olobuild/commits/main

1.4.172

  • Security/compliance: output-escaping hardening campaign across all PHP renderers (246 files). User-supplied values are escaped or whitelisted at the point of output (esc_html/esc_attr/esc_url/int casts); internally-built CSS/JS blocks are documented with specific phpcs annotations after per-variable upstream-sanitization review.
  • Security: closed raw-value CSS injection vectors in nav, subnav, textmask, blendtext, floatingpanel, headline, button and the Woo gallery slider (values now pass through the color/slug whitelists; valid values render byte-identical).
  • Security: analytics tracking IDs (GA4/GTM/Meta Pixel/Clarity) are now restricted to a strict alphanumeric charset before being printed in the tag snippets.

1.4.103

  • Set "Requires at least" to WordPress 5.9 (str_contains / str_starts_with / str_ends_with are provided by core since 5.9).

1.4.102

  • Compliance: the admin builder now loads Leaflet, lottie-web and PDF.js from the local assets/vendor/ folder instead of unpkg/cdnjs — no library is loaded from a CDN, front-end or admin.
  • Disclosure: documented all front-end web-analytics tags (GA4/GTM, Meta Pixel, Microsoft Clarity, Hotjar) and the additional map providers (Esri/ArcGIS, OpenTopoMap, OSM France, Nominatim) under External services.
  • i18n: fixed 7 strings using the wrong text domain ('olobuilder' → 'olobuild').

1.4.101

  • Compliance: all bundled JavaScript/CSS libraries (Chart.js, lottie-web, Leaflet) now load locally from assets/vendor/ instead of a CDN.
  • Privacy: Google Fonts are now self-hosted (downloaded once, served from /uploads); no visitor request to Google. Removed Google Fonts preconnect/dns-prefetch hints.
  • Security: removed all hard-coded stock media API keys; keys must be configured by the user (settings or wp-config constants).
  • Security: saving custom head/body/footer code now requires the unfiltered_html capability.
  • Added readme.txt, LICENSE (GPLv2) and License headers.

Upgrade Notice

1.4.101

After upgrading, re-enter your Unsplash/Pexels/Pixabay API keys (or define them in wp-config.php) to keep stock media search working.