{
    "version": "1.5.0",
    "item": {
        "id": "blog_v23",
        "title": "What Is DBETA Bones? Our Web Platform, 8.0 to 9.0",
        "url": "https://www.dbeta.co.uk/blog/dbeta-bones-framework-development.html",
        "summary": "DBETA Bones is DBETA's own proprietary web platform, the software DBETA builds client websites on. Its main value is control over information, with each fact kept once as a structured record and changed through controlled releases, and speed, from lean custom code without a plugin stack and from layers that let design and content change separately. Schema.org JSON-LD, AIDI files, sitemaps and llms.txt are generated from the same records. Research between 2021 and 2024 led to Bones 8.0, the production version that DBETA client platforms run on today, focused on modularity, platform-level automation, performance through architecture and structured machine-readable output. Bones 9.0 is a next-generation version under active development, being rebuilt as an application on Laravel and designed to start from business information and its relationships rather than pages. Its design covers user-defined content types and relationships, staged publishing with review, a section-based website builder, structured data and AIDI, role-based governance and optional AI assistance, for enterprises, developers, agencies and a range of sectors. Bones 9.0 is not currently available and no release date has been announced.",
        "category": "Software Engineering",
        "image": "https://dbeta.b-cdn.net/blog/dbeta-bonesv8.png",
        "author": {
            "name": "Donatas Tranauskis",
            "url": "https://www.donatastranauskis.com"
        },
        "published_at": "2025-09-11T08:00:00+01:00",
        "updated_at": "2026-11-03T11:06:00+00:00",
        "faqs": [
            {
                "question": "What is DBETA Bones?",
                "answer": "DBETA Bones is the web platform we make, the software we build client websites on. It keeps each fact, such as a service, case study or review, once as a structured record, so information stays consistent and changes go live through controlled releases. Sites are lean custom code without a plugin stack. Pages, Schema.org JSON-LD, AIDI files and sitemaps are generated from the same records. It is not a theme, plugin or downloadable CMS; organisations use it through DBETA's Bones Implementation service."
            },
            {
                "question": "How does DBETA Bones differ from WordPress or a typical CMS build?",
                "answer": "Many CMS builds scale through added plugins and template exceptions. Over time this can increase dependency risk and make performance and governance harder to control. DBETA Bones is engineered as a platform where structure, modularity, and automation are designed into the core so the platform can evolve with clearer rules and fewer moving parts."
            },
            {
                "question": "Is this just custom software, or is there evidence behind it?",
                "answer": "Bones 8.0 came out of research between 2021 and 2024 into architectural modularity, performance through design, platform-level automation and reduced reliance on third-party plugins. The aim was to test whether these could come from architecture rather than routine configuration or third-party tooling."
            },
            {
                "question": "How does Bones support machine discovery and AI-readability?",
                "answer": "Bones emphasises structured content modelling and consistent generation of machine-readable context (such as Schema.org/JSON-LD) across templates. This reduces ambiguity for systems that interpret websites at scale, including search engines and AI-driven answer systems."
            },
            {
                "question": "Can Bones support multilingual websites?",
                "answer": "Yes. Bones is designed to support structured content management patterns that work across languages, with shared rules that reduce template duplication and minimise drift as new language versions are introduced."
            },
            {
                "question": "What kind of performance outcomes should we expect?",
                "answer": "Outcomes depend on content weight, integrations, hosting, and the condition of the legacy platform. Bones is designed to enforce consistent performance practices at platform level, and we validate impact through measurement during audits and staged releases."
            },
            {
                "question": "What is Bones 9.0 and can we use it?",
                "answer": "Bones 9.0 is the next generation of DBETA Bones. It is under active development, being rebuilt as an application on Laravel, and designed to start from business information and its relationships rather than pages. It is not currently available and no release date has been announced. Projects starting today are built on Bones 8.0."
            },
            {
                "question": "What maintenance is required over time?",
                "answer": "Bones aims to reduce reactive maintenance caused by dependency churn and template sprawl. Maintenance focuses on planned updates at platform level rather than frequent patching of numerous third-party components."
            },
            {
                "question": "Can we still use a familiar CMS interface?",
                "answer": "In some cases, yes. A hybrid architecture can be implemented where a CMS is used primarily as a content interface while the Bones platform controls front-end delivery and system structure. The best approach depends on governance needs and content workflows."
            },
            {
                "question": "Is Bones suitable for every project?",
                "answer": "No. For smaller or short-lived sites with minimal governance needs, a well-managed CMS may be the better choice. Bones is designed for organisations where scale, longevity, and structural clarity are critical."
            }
        ]
    }
}