THE PROJECT

A more open future
for content.

ContentLIBRE is being shaped around a straightforward idea: teams should have the freedom to understand, adapt and take responsibility for their content platform.

The name, in full.

Content Lifecycle Integrated Bundle Runtime Environment.

The long form describes the direction. ContentLIBRE is the name to use in navigation, headings and conversation. “Your content. Your platform.” is the promise we want the website to make; the documentation and capability-status page keep its technical scope clear.

The choices behind the project.

Open

A business-friendly Apache 2.0 licensing direction, with room to modify and fork.

Adaptable

An explicit feature assembly and project extension model rather than one fixed implementation.

Accountable

Implementation statements, design proposals and unverified behavior are different kinds of evidence. They should stay visibly different.

Source publication is the next connection.

The project owner’s intended GitHub organization is github.com/ContentLIBRE. A public repository and release destination are not yet confirmed. Until they are available, start with the documentation and current capability status.

Intended organization: https://github.com/ContentLIBRE

Until the repository is public

Start with the documentation and the capability-status page; both describe the release, not the roadmap.

A project, not a service promise.

This website does not claim a hosted offering, commercial support plan, service-level agreement, customer adoption or a formal governance model. Those details should be published when the project can support them with a real operating commitment.

Open possibilities start with clear choices.

Explore the foundation, understand its boundaries and bring your own requirements to what comes next.