WP Manifestindependent plugin directory
manifest / editor / tunet-core

Tunet Core

Opt-in block effects, custom blocks and a lightweight effects runtime for the WordPress block editor. Engine of the Tunet theme ecosystem. GPL-2.0-or-later.

by TUNET Design · github.com/aitunet/tunet-core · 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/aitunet/tunet-core/archive/refs/heads/main.zip

Opt-in block effects, custom blocks and a lightweight effects runtime for the WordPress block editor. Nothing is hardcoded: every effect is enabled per block, and every value (color, easing, duration) is read from the active theme's design tokens (--tnt-*), with sensible defaults when a theme doesn't define them.

Tunet Core is the shared engine of the Tunet theme ecosystem, and it is useful on its own with any block theme. It is free software (GPL-2.0-or-later) and is being submitted to the WordPress.org plugin directory.

What it provides

  • *Effects on native blocks (`tf` attributes).* A Tunet Effects* panel on Group, Columns, Cover, Image, Heading, Paragraph and Buttons: entrance animations (fade-up, clip-reveal, mask-up, blur-in, scale-in, slide, text-stagger), hover effects (lift, glow, tilt, magnetic, image-zoom, underline-grow), scroll effects (parallax, sticky-pin, reveal, progress), blend modes and animated borders. A block with no effect attribute stays completely clean.
  • Custom blocks where the core falls short. Section (advanced backgrounds: image, video, gradient, mesh, overlay, shape dividers), Marquee, Counter, Before/After, Slider and Testimonials (Swiper-powered), Brand, Icon, Badge and Breadcrumbs.
  • A lightweight runtime. Effects are detected per page and their assets are enqueued only when a block on the page uses them. Reveals use the native IntersectionObserver; heavier libraries load on demand. prefers-reduced-motion is always respected.
  • Options + demo importer. Global settings, JSON import/export, content-layout (sidebar) controls, and a per-theme demo importer with a progress bar and one-click rollback. Themes opt in by shipping a manifest; without one there is nothing to import and nothing fails.
  • Extensible from outside. Themes and plugins can register extra icons and declare content types through documented filters.

Requirements

  • WordPress 6.6+ (tested up to 7.1)
  • PHP 7.4+

Installation

Download the latest release ZIP (or clone this repository into wp-content/plugins/tunet-core) and activate Tunet Core from Plugins. No build step is required to run the plugin: the shipped JavaScript and CSS are plain, unbundled files.

Development

npm install
npm run lint:js
npm run lint:css

Conventions: PHP prefix tunet_core_ / Tunet_Core_, CSS custom properties --tnt-, block namespace tunet/, data attributes data-tf-, text domain tunet-core. Every public capability must be additive and backward compatible; themes already built on the engine must keep working after any change.

Translations live in languages/ (tunet-core.pot + compiled .mo/.json per locale).

Design principles

  1. Nothing hardcoded. No effect is applied unless a block attribute activates it.
  2. Engine/design separation. Functionality lives here; presentation lives in each theme. Switching themes never breaks content.
  3. Degrades with dignity. The engine ships token defaults so effects and blocks look good under any theme.

Contributing

Issues and pull requests are welcome at https://github.com/aitunet/tunet-core. Please keep changes additive, respect the conventions above and run the linters before submitting.

License

GPL-2.0-or-later. See LICENSE.

Made by TUNET Designprofiles.wordpress.org/tunetdesign.