Coming up to speed on Dagster, so figured I'd share one noob observation. There are a lot of imports supported directly from the top level

dagster

module. That might be handy for experienced users, but as a newcomer I generally expect stuff available at the top level to be the most important, core concepts and models. Learning the structure below that tends to reveal a lot about the mental model that the framework uses. I think I'd be learning faster if the import structure and docs forced me to reach into the relevant sub-module for what I need.

Hi Nathan, thanks for the feedback! Did you get a chance to take a look at our docs site? I’m curious to learn your thoughts on the Concept page (https://docs.dagster.io/concepts) or API Docs section (https://docs.dagster.io/_apidocs). Do you think any of these would help the learning, or would you expect something different?

Yes, I've spent time with those sections of the docs. I think the organization of the docs is quite good. That said, I've found myself frequently referring to the Dagster codebase to answer questions where the docs are not currently clear. I also think the docs could be improved by having more realistic examples. It covers concepts and API usage well, but I think leaves quite a bit of work for the reader to figure out how to put it all together into a working project.

Got it. Totally agreed. Again, thanks for the feedback. Re: realistic examples, you can find several examples that represent more realistic use cases here: https://github.com/dagster-io/dagster/tree/master/examples We also have a few guides written for certain use cases: https://docs.dagster.io/guides, one of which walks through a fully feature project: https://docs.dagster.io/guides/dagster/example_project Meanwhile, I’m actively working on producing more examples. I’m happy to learn if you have any how-to questions or use cases that you’d like to see examples for. Please feel free to either comment here or DM me!