Repository navigation
v0.2.0
Pre-releasev0.2.0 is the one where pages get a body. Until now a TachyonCMS document could hold text, numbers, links and lists, but nothing you'd call an article. Now a page can be built from blocks you define, and a post can carry real rich text that you write as JSON or Markdown and read back as JSON, HTML, Markdown or plain text. It's still pre-alpha: drafts, media and the admin screen are next, so keep it off public networks for now.
Get it
- Binaries for Linux (x86_64, arm64, static) and macOS (Intel, Apple silicon) are attached below.
- Docker:
docker pull ghcr.io/tachyon-cms/tachyoncms:v0.2.0. SetTACHYON_DATABASE_URLandTACHYON_PUBLIC_URL, and it serves on port 3000.
Upgrading from v0.1.0? Replace the binary or the image and start it. The one migration runs by itself.
What's in it
- Pages built from blocks. A
blocksfield holds rows of the block types you define: a hero, a quote, a call to action. Each row keeps its ownidandblockType, and you can filter into them withwhere[layout.blockType][equals]=quote. Field rules apply inside every row, so a field only Editors may see stays hidden in each block that has it. - Blocks you write once. A shared block (
"kind": "block") can be used by any number of collections. Change it in one place and every schema that uses it is checked and migrated in the same transaction. If that change would break a page somewhere, it's refused before anything is saved. - Rich text that can't run a script. Paragraphs, headings, lists, task lists, quotes, code, tables, links and embedded blocks, with the features turned on per field. HTML output is built and escaped by TachyonCMS itself, never passed through, and every link is checked against
http,https,mailto,teland relative paths, on the way in and again on the way out. - Write it in Markdown. Send
{"format": "markdown", "value": "…"}and it's converted on the way in, with extensions for blocks (:::callout{type="warning"}), links to other documents ([guide](doc:pages/install)) and embedded references. Anything that can't be converted faithfully is a 422 with the line number, not a quietly mangled post. - Read it however your site wants it.
?format=html,markdownortexton any read, populated and joined documents included. A link to something the reader can't see comes out as its text alone. - Config mistakes stop at startup. A
--configfile that doesn't exist, a misspelt key intachyon.toml, anallowed_originsentry that could never match (a path, a wildcard, no scheme),lockout_attempts = 0and a session that ends before its idle limit are now errors that name the setting, instead of surprises later. Andtachyon schema diff nope.jsonwith the database down now says the file is missing straight away, while a connection that fails names the host, port and database it tried, never the password.
The docs at docs.tachyoncms.com have a page each for blocks, rich text and Markdown input, with every rule the converter applies.
Supply chain
Every binary records its dependency tree, and each archive has an SPDX SBOM. The checksums are signed with cosign, the archives and the image carry build provenance, and the image is signed. Scorecard runs weekly, and every commit is signed off under the DCO.
Thanks
To @foothillsdigital, the first person to send code to TachyonCMS: every startup and CLI fix in this release is theirs (#47, #48, #52), and so are the docs for the first two. There are more good first issues waiting, and this section has room for more names.
Verify a download
cosign verify-blob \
--certificate-identity 'https://github.com/tachyon-cms/tachyoncms/.github/workflows/release.yml@refs/heads/main' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--bundle checksums.txt.sigstore.json checksums.txt
sha256sum --check --ignore-missing checksums.txtFull changes: v0.1.0...v0.2.0