> you'll be able to serialize dashboards to Cue schema It'll be possible to serialize/represent the dashboards in CUE. Here's a handwavy, pseudocode-y example

> you'll be able to serialize dashboards to Cue schema It'll be possible to serialize/represent the dashboards in CUE. Here's a handwavy, pseudocode-y example i use in the talk: https://gist.github.com/sdboyer/d76196f94ca78d1e84c739e95e64d3eb https://gist.github.com/sdboyer/d76196f94ca78d1e84c739e95e64... That said, it's not like we're planning on replacing all the "export JSON" buttons in the Grafana UI with "export CUE." One of the interesting properties of defining schemas in CUE is how it allows us to remove schema-defined default values from a dashboard's JSON. The JSON representation can actually look a lot more like a concise CUE representation. > versioning Versioning of the Grafana schema is the essential design goal of the "scuemata" system that is under discussion in that epic issue Versioning of artifacts that are instances of the schema is a key goal with Polly https://docs.google.com/document/d/1GU0DGy-X6z4FVwbJYPsBKRdqApi2RppW0q2U6YUXOp8/edit#heading=h.psq84twzkwrt https://docs.google.com/document/d/1GU0DGy-X6z4FVwbJYPsBKRdq... > non-visual editing Like, editing something other than raw code in an editor? Yes, this is also something directly enabled by the schema (again, see the Polly doc, the "Produce" heading). For data-intensive tasks, such editing experiences are the only way to see your logic in the context of data, and therefore IMO prerequisite for confidence > reproducibility Yup. This already isn't "hard" to do today, but reproducibility gets more complicated at scale - those questions about how to map what's on disk to what's in your Grafana (or whatever app) in my parent comment become more complicated, leading to friction, leading to staleness.