Bones, the web platform by DBETA

The platform behind our larger sites.

Bones is the web platform we make and build on. Bones 8.0 runs the sites we build today. Bones 9, with its core, customer portal and staff console, is being rebuilt as an application on Laravel.

Build on Bones Talk to us
Today
Bones 8.0
Runs the sites we build
Next
Bones 9
Being rebuilt on Laravel
Bones 9 release
Not yet
In development, no date set
Use it now
From £12,500
Bones Implementation, ex VAT

Bones 9 · In development

What Bones is

Bones is the web platform by DBETA, being rebuilt as Bones 9, an application on Laravel. It treats a website as a structured system rather than a set of pages: each kind of information is a content type, stored once, connected to the rest and published wherever it is needed.

Bones 9 is in development, with no release date. Our larger sites run on Bones 8.0 today; smaller static sites are hand-coded.

  • In development

    Several websites, one place

    Designed to run several websites and workspaces from one place, instead of a separate system for each.

  • In development

    Your own content types

    Define your own types of information, such as services, projects or people, with their own fields and relationships, in the admin rather than in code.

  • In development

    Governance by design

    Changes are reviewed before they publish, with per-person access and a record of who changed what.

  • In development

    One source, every output

    Pages, Schema.org markup (JSON-LD), AIDI files, sitemaps and llms.txt are generated from the same records.

  • In development

    Built on Laravel

    Rebuilt as an application on Laravel, with a Customer Portal for clients and a Staff Console for our team.

  • Planned

    AI assistance

    AI tools to help create and check content are planned, not built yet.

How it fits together

One source, many outputs

Your organisation is described as content types. People change the records, someone approves, and Bones generates every place the change needs to appear. Pick an example.

Example Business: A new case study

Your content types

  • Servicename · summary · price from
  • Case studyclient · problem · what we built
  • Articletitle · author · published
  • Reviewrating · source · date
  • Companyname · address · opening hours
Bones
  1. 01

    Each fact stored once

  2. 02

    Records linked to each other

  3. 03

    Drafted, approved, then publishedBones 9 · in development

  4. 04

    Outputs generated, never copied by hand

Generated outputs

  • PagesWhat people read/case-studies/new-site
  • JSON-LDSchema.org markup"@type": "Article"
  • AIDI filesShort JSON summaries/aidi/cases.json
  • SitemapsFor search engines/sitemaps/cases.xml
  • llms.txtFor AI tools/llms.txt
Who changes it
Marketing drafts the case study; a director approves it.
How the data connects
The case study is linked to the services it supports and the client’s review.
What updates
The case study page and those service pages update, with their structured data.

Examples are illustrative. Content types, fields and approval steps are set up for each organisation.

What Bones 8.0 does today

These come from how the platform is built, on every site we build with it.

01

Structured content

Each service, case study, article and review is kept as structured data, not locked inside a page layout.

02

Facts stored once

Company details, services and reviews are stored once and reused across pages, structured data and AIDI files.

03

Readable by machines

JSON-LD, AIDI summaries, sitemaps and llms.txt are generated from the same content as your pages. About SEO and GEO.

04

No plugin stack

Custom code on Bones, not a WordPress theme or plugins. It still needs updates and maintenance.

In development

What Bones 9 is made of

Three connected parts, each written up as a case study. All three are in development.

In development

Bones Core

Organisations define their own types of information and relationships, then review, publish and reuse them. Read the case study In development

Customer Portal

Where client organisations are planned to manage their users, installations, releases, domains, support and billing. Read the case study In development

Staff Console

Our internal tool for operating the installations we manage, with per-person access and an audit trail. Read the case study

Roadmap

Where Bones is, and where it is going

From the platform our sites run on today to Bones 9 and what comes after it.

  • Live
  • In development
  • Planned
  • Exploring

No dates are set. Everything after Bones 9 is our direction, not a commitment, and may change.

  1. 2019

    Client platforms

    We start building and looking after client platforms.

  2. Today Live You are here

    Bones 8.0

    Runs the sites we build. Content is kept as structured data and the pages, JSON-LD, AIDI files, sitemaps and llms.txt are generated from it.

  3. In development

    Bones 9, on Laravel

    Rebuilt as an application, in three parts: Bones Core, the Customer Portal and the Staff Console. No release date yet.

  4. In development

    Alpha

    Bones is in active development; early versions are demonstrated by DBETA and are not yet available to clients.

  5. Planned

    Customer Portal

    A customer account area for managing your Bones subscription is planned.

  6. Planned

    Run by us, or on your own servers

    We plan to offer Bones both as a service we run for you and as a version you run on your own servers.

  7. Planned

    Modules

    Organisations define their own kinds of records in Bones; optional modules from DBETA are planned.

  8. Exploring

    Partners

    We intend to support partners who deliver Bones for their own clients.

Using Bones today

Sites are built on Bones 8.0 through Bones Implementation, starting with a Structural Blueprint from Structural Strategy.

Your content and data belong to you. Bones itself remains DBETA’s proprietary platform; the terms for using it are set out in your agreement.

Structured to connect.
Built to scale.

Hire us info@dbeta.co.uk