In reply to Justin Tadlock.

Well, my pain is, that I feel left out in the cold considering the theme.json approach in general. It begins with what is being described here: what to change where and above all: why? As long as I‘m lacking a real good explanation behind the logic behind the system I‘m sticking with classic themes, as they provide me a tried and trusted way to design them and do not confront non-tech-savvy editors with option after option to mess up the site.

Once this overhaul of the concept is somewhat finished and not prone to what seems like neverending overhauls I might consider having a second look. Because whenever I try to grasp the sense of the whole approach I‘m getting more confused about the concept behind it all, besides keeping a lot of people occupied with it.

The other point that bugs me about theme.json is that to me it provides a lot of bloat, endless lines of seemingly redundant definition after definition adding an extra layer to the never ending evolvement of CSS and not a tool in sight to make editing it more comfortable for designers. The whole concept seems to me as being dominated from a mere coder’s perspective, the in-crowd and the paupers that lack the ability to focus on nothing but coding. The approach seems to be targeted on bigger agencies with designated specialists for every field.

I really hope the handbook mentioned might sometime clear up my irritations and the disappointment coming from it.