Docs / Clautron / Features

Features

A Feature is persistent WordPress functionality that reacts to events on your site. Examples: a custom metabox, a completeness score that updates on save, a publish gate that blocks incomplete posts.

Feature lifecycle

Every feature goes through these statuses:

StatusMeaning
DraftSaved but not running. Edit freely.
ActiveRunning on your site. WordPress hooks are registered.
PausedTemporarily disabled. Structural elements (metaboxes, columns) are still visible but the trigger logic does not run.
ArchivedInactive and hidden from the main list. Not deleted.

How a feature works

A feature has two phases:

Compile phase — "what to register"

Structural elements WordPress needs to know about on every page load: custom post types, taxonomies, metaboxes, admin columns, admin filters, REST routes, head injection, and more.

These run once when you Activate a feature and again on every WordPress load while the feature is active.

Runtime phase — "what to do when triggered"

Logic that runs in response to an event:

TriggerWhen it fires
save_postWhen a post is saved or updated
hookOn any WordPress action or filter you specify
scheduleOn a time-based schedule (uses WP-Cron)
rest_apiWhen a specific REST endpoint is called
noneNo runtime trigger — compile phase only

Managing features

Go to Clautron → Features to see all features with their status, source (AI-generated or manually imported), and creation date.

Actions available on each feature:

Example — content completeness checker

This feature:

  1. Adds a metabox to the post editor showing a checklist (title, content, excerpt, featured image)
  2. On save_post, calculates a completeness score (0–100) and saves it to _clautron_completeness_score
  3. Shows a percentage bar column in the posts list
  4. Adds a dropdown filter to filter posts by completeness

All of this is configured as a single blueprint with no code. The AI Assistant generates it from a one-line prompt: "Add a content completeness checker to posts."