01 / Why Active Tags

Back to top

Browser behavior needs one control path.

Events, forms, requests, DOM changes, and history are easy to start. The hard part is keeping the work sequenced, inspectable, recoverable, and attached to the page lifecycle.

Active Tags' answer

Centralize the workflow, not the application.

Active Tags compiles declared behavior into jobs and runs each execution as a ticket through one protocol for sequencing, waiting, errors, targets, data movement, and cleanup.

02 / Use cases

Back to top

Use it where the page needs a workflow.

The strongest fits keep the current HTML and backend, then give browser behavior a shared execution boundary.

01 Progressive enhancement

Server-rendered forms and mixed stacks

Add structured behavior to the page you already have.

Compile contact, signup, validation, request, alert, and DOM-update steps into named jobs while the server continues to own the HTML.

Product fit
Forms and bounded interactions that need sequencing, waiting, recovery, and explicit error paths.
Required boundary
The application still owns rendering, backend validation, authorization, and domain behavior.
Discuss progressive enhancement
02 Application panels

CRUD lists, modals, and dynamic page regions

Coordinate panel-heavy application workflows.

Use discovery and disposal, form collection, API operations, list transforms, alerts, and target handling through one ticket lifecycle.

Product fit
Administrative and product interfaces with repeated panel, modal, list, and network patterns.
Required boundary
Authentication, access policy, API contracts, and application-specific operations remain product-owned.
Discuss an application workflow
03 Navigation and recovery

Multi-step requests, session gates, and history state

Make waits, recovery, and navigation explicit.

Run readiness gates, protected-session recovery, page replacement, request chains, history restoration, and error phases as inspectable jobs and tickets.

Product fit
Browser workflows whose next step depends on asynchronous application or navigation state.
Required boundary
Active Tags makes the execution protocol explicit; networks, browser timing, DOM changes, and custom operations remain variable.
Discuss a recovery workflow