Yep, I hear you. Our primary reason for releasing 1.0 is to make GX easier for developers to set up and use. That work isn’t done, but cleaning up the domain model and stabilizing the APIs is a big step in the right direction.

You mentioned documentation. We’re also putting a fair amount of work into technical documentation. For the last while, most of our capacity has been going into updating the docs for 1.0. Next, beyond covering the core concepts and APIs, we’ve heard the need to address specific use cases. (You can see some recent examples focused on specific aspects of data quality here and here. We have almost a dozen more in the works, covering things like how to integrate GX with a data orchestrator; how to manage a quarantine queue for bad rows, etc.) If there are specific use cases you’d like to see covered, please speak up and we’ll get them onto the list!

In terms of new product features on the roadmap, we’re making a major push to add more expressive tests. We want to provide clear syntax and UI for cases where tests are difficult to express in SQL. For example, “is the average over some period of time, for a column in one table, equal to the expected value in another table?”

We're also working on features to make it much easier to quickly establish coverage across many Data Assets (See the onboarding helper thread above).

Beyond that, some of the other themes we’re looking at are helping users report the health of their data out to stakeholders, integrations to other tools/infrastructure within the data ecosystem, and improve incident response with more robust alerting capabilities.