Connect any website.

Keep the HTML you already have. Birkly fills it with content through one script tag, or hands you JSON for whatever stack you prefer.

{from 'birkly' get 'integration'}

Your HTML, one script tag, live content.

Write normal HTML and put template tags where content goes. birkly-client.js fetches published entries and fills them in. It works on the same host as Birkly or on any other domain.

<!-- any page on any site -->
<script src="https://cms.example.com/birkly-client.js"></script>

<ul class="posts">
  {for each entry in 'blog' ordered by newest limit 3}
    <li>
      <a href="post.html?collection=blog&slug={slug}">{title}</a>
      <time>{created_at format "F j, Y"}</time>
    </li>
  {endfor}
</ul>

{for each entry in 'stacks'}

Four ways to put Birkly on a page.

Pick by one question: who renders the page? All four read the same published content.

default

HTML templates

Plain HTML with template tags, rendered by birkly-client.js. No build step.

web components

Regions

Drop in a <birkly-region> for a header, footer or list, and enhance it with your own JavaScript.

SPA

React, Vue and co.

Fetch JSON from the Public API or Birkly.fetch and render with your own components.

SSR / build time

PHP, Astro, Next.js

Render on the server or at build time for SEO, no-JavaScript fallbacks and static hosting.

{from 'templates' get 'language'}

A template language that reads like English.

Single braces, plain sentences, nothing to compile. Here is most of it.

loops

Lists

Filter, sort and limit any collection.

{for each entry in 'events'
  ordered by newest limit 5}

conditionals

Show or hide

Fallbacks for empty fields and per-language copy.

{if entry has 'image'}…{else}…{endif}

single entries

One known entry

Load a header, a footer or any one-off page block.

{from 'site_elements' get entry 'footer'}

detail pages

From the URL

One template serves every entry; the URL says which.

post.html?collection=blog&slug={slug}

media

Images and embeds

Ready helpers for images, galleries, maps and videos.

{media_img('hero', 'Alt text')}

forms

Public forms

Visitor submissions become entries in a collection.

{entry for 'contact'}…{endentry}

{from 'birkly' get 'delivery' with 'control'}

Hosting, routing and versions, under your control.

Birkly runs wherever PHP runs and decides itself which hostname serves the admin and which serves the site.

rendering

Server-side or client-side

Files in the project folder render on the server. Any other site connects through one script tag and renders in the browser. Same templates either way.

routing

One template, every entry

A single blog-post.html serves the whole collection. Add an entry and its page exists. No generation step, no deploy.

hosting

Anywhere PHP runs

Shared hosting, a VPS, a container. No Node process to keep alive, no queue to supervise, no service you cannot restart yourself.

insights

Analytics without another product

Privacy-friendly delivery metrics in the same admin, so you are not bolting a dashboard onto a CMS that already knows the answer.

git

Pull and push from admin

Design and templates stay versioned with your remote, so a rollback is a revert rather than a restore from backup.

NextEvery feature, in one list