The Laravel framework
for WordPress.

01  Declare and sign

Say which sizes you use. Not how to make them.

The URL, the width, the height and the srcset are worked out from the image’s metadata, and rendering a page never touches the disk. The file name carries an HMAC of the original and of the size: change a size, the name changes, and no cache ever holds an old file.

ImageSize::add('card')->cover(600, 400)->webp(75);
ImageSize::add('hero')
    ->scale(width: 1920)->webp(70)
    ->widths([640, 1024, 1440]);
ImageSize::add('thumb')->cover(150, 150)->eager();

WebP by default, AVIF with ->avif(). GD and Imagick write WebP; AVIF depends on the server.

02  Store and serve

One disk. Made on first request, or by a service.

Local, S3, R2, Scaleway, MinIO: WordPress keeps using its own file functions, so Gutenberg, ACF and WooCommerce follow without any adaptation. A size is made the first time its URL is asked for, then served as a plain file for a year. For a huge library, let Bunny or imgproxy do it with signed URLs.

MEDIA_DISK=media
MEDIA_URL=https://media.client.fr

03  Control

Crop where it counts. Lock what is private. Move without fear.

Nine anchors for a cover. Private media get signed URLs that expire, on every size and every srcset source. Moving disks is a dry run until you say --execute.

ImageSize::add('portrait')
    ->cover(400, 500, Anchor::Top);

$ php artisan pollora:media:migrate \
    --from=uploads --to=media --execute

Media storage, in the docs → Without media.disk the module is off and WordPress keeps its own folder. It also runs in a classic theme, a plugin or Bedrock.

Registered abilities are published over the Model Context Protocol by the MCP Adapter plugin, and by core at /wp-json/wp-abilities/v1/abilities. Permission checks default to refusing: an ability that forgets one is inert, not open.

#[Ability(
    name: 'acme/create-post',
    description: 'Creates a post from a title and a status.',
    category: 'acme-content',
    behaviour: Behaviour::Creates,
)]
final class CreatePost implements AbilityHandler

Abilities → Not to be confused with Nectar: Nectar helps an AI write your code, abilities let an AI operate your site.

The same post type, written for WordPress and written for Pollora: sixteen lines against eight, imports included. Most of the WordPress version carries no decision. Pollora generates the labels from the class name and finds the class on its own: no function, no add_action. What stays is what you decided.

use Pollora\Attributes\PostType;
use Pollora\Attributes\PostType\{HasArchive, PublicPostType, ShowInRest, Supports};

#[PostType('book')]
#[PublicPostType]
#[HasArchive]
#[ShowInRest]
#[Supports(['title', 'editor', 'thumbnail'])]
class Book {}

A custom block usually means two renderings of the same markup: a React component for the editor, a PHP template for the page. They drift apart. Pollora renders dynamic blocks with Blade, and where the inner blocks go you write <InnerBlocks />, the tag ACF users already know.

<article {!! get_block_wrapper_attributes(['class' => 'card']) !!}>
    <h3 class="card__title">{{ $attributes['title'] ?? '' }}</h3>

    <InnerBlocks class="card__body" />
</article>

One command scaffolds it: php artisan pollora:make:block card --theme --inner-blocks. The editor view is one line, window.pollora.blocks.bladeEdit(metadata).

Build a block, step by step → Coming from ACF blocks? The tutorial ends with what changes, and what does not.

The handler runs after the request. Its arguments travel with the job: a WP_Post, a WP_User or an Eloquent model goes by ID and is reloaded when the handler runs. Remove the attribute and it is synchronous again.

#[Action('save_post_event', priority: 20)]
#[Async(tries: 3, unique: true)]
public function handle(int $postId, CrmClient $crm): void

The default driver, auto, uses the Laravel queue once a connection names a worker, then Action Scheduler, then WP-Cron. pollora:doctor flags what fails silently.

Asynchronous actions → Test it with Async::fake(), which records what would be queued, with assertDispatched() and runDispatched().