TEMPLATE INFRASTRUCTURE / LOCAL-FIRSTTemplates that remain data

A typed DSL, safe HTML rendering, PHP API, CLI, and local-first browser editor in one monorepo.

TrafficOps template pipeline from source to static output

One language

Parameters, types, blocks, conditions, and repeaters live beside HTML and behave consistently in PHP, the CLI, and the editor.

Explicit policy

The host application selects the dialect. A safe profile ships by default; executable extensions require a deliberate integration.

Local-first tools

Generate in a terminal or edit and export a ZIP in the browser without uploading template sources to an API.

Ordinary output

The result is static HTML and unchanged assets that can be deployed to any suitable host.

Minimal example

tpl

@template "Campaign" version=1

@section content "Content"
  @param title String = "New campaign" required
  @param body Markdown = "Start with an **idea**."
  @param destination Url = "https://trafficops.io"
@endsection

@layout
  <main>
    <h1>{{title}}</h1>
    <div>{{& body}}</div>
    <a href="{{destination}}">Continue</a>
  </main>
@endlayout

Save it as index.tpl, then open it in Template Studio or generate the page with the CLI:

npx @trafficops/cli --template ./index.tpl --output ./generated

Where to go next

Build your first template, then choose your integration path: PHP and Laravel, CLI and Template Studio, or agent skills.