Put browser tasks in order.

Jobs and tickets for browser work

Active Tags turns declared behavior into jobs: named pieces of browser work. When a job runs, it gets a ticket that tracks that run through its steps.

Jobs and tickets give events, forms, requests, DOM changes, and history work a common path for sequencing, waits, errors, targets, data movement, and cleanup. Browser and network inputs can still vary.

Keep interface steps in order

Give contact and signup flows named jobs for form collection, validation steps, requests, alerts, and DOM updates. Your backend can continue to own the HTML, validation, authorization, and business rules.

The same approach supports panels, modals, and CRUD lists. It gives API operations, list transforms, target handling, and cleanup a place in the workflow.

Recover through page and session changes

Use named phases for readiness gates, request chains, protected-session recovery, page replacement, and history restoration. Each phase can wait for the condition it needs and report errors through its ticket.

That gives workflows a clear place for cleanup when a target changes or an operation fails. Your application remains responsible for the decisions behind the page.

Start with the guided tutorials

Download Active Tags, then work through the tutorials to see jobs and tickets in use.

Choose the view layer your application already uses, including server-rendered HTML, progressive enhancement, and SPA-style navigation. Evaluation and import modes need author-controlled configuration and a Content Security Policy that permits the intended code loading.

• Read Part 1
• Read Part 2
• Read Part 3