Skip to content

How JSON schema versioning works and how it's different from the theme.json version #260

@bph

Description

@bph

Discussed in #256

Originally posted by juanmaguitar May 1, 2024
Based on feedback like this one

https://twitter.com/ChrisHufnagel/status/1784316768393052284

It would be useful for developers to have an additional explanation about how JSON schema versioning works and how it's different from the theme.json version.

Such an article should cover IMO, at least the following ideas:

  • JSON Schemas for block.json and theme.json
  • The benefits of using a JSON Schema
  • Which JSON Schema version (which URL) should I use for my project?
  • What's the purpose of the version property in a theme.json?
  • What's the relationship (and differences) between the version of the JSON Schema and the version of the theme.json?
  • What's the purpose of the version property in a block.json? Is it related to the version property in a theme.json?

@ajlende is on board about writing a post about this topic (see this comment)

It's confused often enough that I'm planning on writing a developer.wordpress.org blog post to help explain how JSON schema versioning works and how it's different from the theme.json version.

Metadata

Metadata

Assignees

Type

No type

Projects

Status

Published (Done)

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions