Flexa Block – Blocks & Page Builder

Flexa Block is a growing collection of modern Gutenberg blocks designed to help you build beautiful WordPress websites faster.

Instead of installing multiple block plugins, Flexa Block focuses on providing carefully crafted, lightweight, and highly customizable blocks that integrate naturally with the WordPress Block Editor.

📌 DEMO

Features

• Lightweight and performance-focused
• Native Gutenberg experience
• Front-end inline editing — click text on the live page and edit it in place
• Responsive by default
• Clean and modern design
• Highly customizable
• No unnecessary bloat
• Regular updates

Front-end inline editing

Fixing a typo no longer means opening the Block Editor. On the live page, logged-in users who can edit the post simply click the text, type, and save — the change is written straight back to the block, so your layout, styling and generated CSS stay exactly as they were. Every edit is recorded as a note on the post, and you decide from the settings page whether inline editing is on, which roles may use it, and which blocks it applies to.

Whether you’re building landing pages, business websites, blogs, or eCommerce stores, Flexa Block helps you create professional layouts with less effort.

More blocks and advanced features will be added in future releases.

Source code for compiled JavaScript and CSS

The plugin ships with minified/compiled JavaScript and CSS in build/. The human-readable source code (src/), together with the build tooling used to generate those assets, is publicly available and maintained at:

https://github.com/flexatech/flexa-block

The assets are built with npm and @wordpress/scripts (webpack). To build them yourself:

1. Install dependencies: npm install
2. Build production assets: npm run build (or npm start for a watched dev build)

This regenerates everything in build/ from the source in src/.

External services

This plugin can connect to the third-party services listed below. Each is optional and is only contacted for the specific block that uses it; if you do not use that block, no request is made.

Facebook Graph API (Facebook Feed block)

The Facebook Feed block displays posts from a Facebook Page. When the block is present on a page (and in the editor while you configure it), the plugin sends a request from your server to the Facebook Graph API (https://graph.facebook.com/) containing the Page ID and the Page access token you enter in the plugin settings, in order to retrieve the Page’s recent posts, images and engagement counts. Responses are cached to reduce the number of requests. The access token is stored on your server and is never exposed to visitors’ browsers. This service is provided by Meta Platforms, Inc.
Terms of Service: https://developers.facebook.com/terms/
Privacy Policy: https://www.facebook.com/privacy/policy/

Instagram Graph / Basic Display API (Instagram Feed block)

The Instagram Feed block displays media from an Instagram account. When the block is present on a page (and in the editor while you configure it), the plugin sends a request from your server to the Instagram API (https://graph.instagram.com/) containing the access token you enter in the plugin settings, in order to retrieve the account’s recent media. Responses are cached to reduce the number of requests. The access token is stored on your server and is never exposed to visitors’ browsers. This service is provided by Meta Platforms, Inc.
Terms of Service: https://www.instagram.com/about/legal/terms/
Privacy Policy: https://privacycenter.instagram.com/policy/

Google Maps (Google Map block)

The Google Map block embeds an interactive map for a location you specify. When a page containing the block is viewed, the visitor’s browser loads a Google Maps embed (https://www.google.com/maps/embed/ when you supply a Google Maps Embed API key, otherwise https://maps.google.com/maps) with the location and zoom level configured on the block. This means the visitor’s browser connects to Google to display the map. This service is provided by Google LLC.
Terms of Service: https://cloud.google.com/maps-platform/terms
Privacy Policy: https://policies.google.com/privacy

YouTube (Video Popup block)

When the Video Popup block is set to a YouTube video, the visitor’s browser loads a preview thumbnail from YouTube (https://img.youtube.com/) when the page is viewed, and — after the visitor clicks play — an embedded player from YouTube (https://www.youtube.com/embed/). Only the video ID you configure on the block is sent; no personal data is transmitted by the plugin. This means the visitor’s browser connects to YouTube to display the thumbnail and player. This service is provided by Google LLC.
Terms of Service: https://www.youtube.com/t/terms
Privacy Policy: https://policies.google.com/privacy

Vimeo (Video Popup block)

When the Video Popup block is set to a Vimeo video, the visitor’s browser loads an embedded player from Vimeo (https://player.vimeo.com/) after the visitor clicks play. Only the video ID you configure on the block is sent; no personal data is transmitted by the plugin. This means the visitor’s browser connects to Vimeo to display the player. This service is provided by Vimeo, Inc.
Terms of Service: https://vimeo.com/terms
Privacy Policy: https://vimeo.com/privacy

User-supplied RSS feed (RSS Feed block)

The RSS Feed block fetches and displays entries from an RSS/Atom URL that you enter into the block. No fixed third-party service is involved — the plugin only requests the exact feed URL you configure — but be aware that this causes your server to make an outgoing request to that URL.

Deactivation feedback (Flexa Product Intelligence)

When you go to deactivate Flexa Block on the Plugins screen, a short optional survey asks why. It is served by Flexa’s product intelligence service at https://product-intelligence.flexacommerce.com. It runs only in the admin, on wp-admin/plugins.php, never on the front end, and never blocks or delays deactivation. What is sent, and when:

• On opening the Plugins screen: a request to /api/v1/config (product slug and tier) to load the survey configuration. The response is cached for 6 hours.
• When you deactivate or interact with the survey: the reason you pick and any optional message you type, sent to /api/v1/deactivations, /api/v1/events, /api/v1/feedback, /api/v1/feature-requests and /api/v1/recovery-events.

Every request includes an anonymous per-site identifier (a random UUID), the plugin version and tier, and by default your WordPress version, PHP version and locale. No email, site domain, user identity or raw IP is collected. To stop sending environment data, use add_filter( 'flexa-block/deactivation_survey/config', function ( $c ) { return array( 'collect_environment' => false ) + $c; } );. To disable the survey entirely, use add_filter( 'flexa-block/deactivation_survey/enabled', '__return_false' );.
Terms of Service: https://flexacommerce.com/pages/terms
Privacy Policy: https://flexacommerce.com/pages/privacy