As low-hanging fruit, just having an obvious answer to the above question would be great. It'd be helpful to have callouts to other resources at the end of the tutorials section. "Now that you know assets and ops and jobs, this is what you need to know next." (The assets tutorial does this, but the ops and jobs one does not. Additionally, the conclusion of the asset section doesn't even talk about repositories or projects, which feels like a missed opportunity.) In general, though, I'd suggest significantly expanding the tutorials section. The content that's there is great, but as I mentioned above, it just feels like a disjointed island. Once I know about assets and ops and jobs, it'd be good to have more tutorials that introduce me to other related topics. I've listed them below, alongside a summary of what the learning outcome of that section would be: • graphs -- now that you know about assets and jobs, here's how to think about interconnecting them (the assets page does cover this somewhat, so maybe it's redundant) • schedules and sensors -- how do you trigger and orchestrate these graphs/assets/ops/jobs that you've defined • repositories -- now that have a few assets and sensors, how can you group them together? • projects -- what's the big picture view of how all these things come together And maybe the 'fully-featured project' (or a simpler version of it) can be what the tutorial builds towards. I'd recommend looking at Prefect's docs for inspiration. They have a separate Concepts section that does a deep dive into each topic, but for many of the foundational concepts, they also have a tutorial page that provides a more succinct introduction to that concept. That may feel redundant, but it's helpful to have a place where I can just get a high-level overview of a topic and maybe a couple of simple examples before learning about every nook and cranny. I finished going through Prefect's tutorials before coming to Dagster (I'm comparing the two products to decide which one we should use) and I never felt confused when reading Prefect's tutorials or unsure about what where I needed to do next. On the other hand, as soon as I finished going through the tutorials section in Dagster's docs, I was immediately confused about where to go from here. Most importantly, I felt like I could actually create Prefect project on my own (because I was introduced to the relevant components with some simple examples of how they connect) after finishing their tutorial, but Dagster's tutorial doesn't even discuss the concept of a project so I did not have the same feeling here. (Getting Started does go through creating a project, but doesn't explain why I need a project or what it is, just how to quickly get a scaffolding.)

Also, I agree with you specifically on the idea of a "project". Dagster has "repository", "package", "code location" and "deployment", all of which have some overlap semantically. I know that the team is actively working on simplifying this ontology to improve this experience, though.

@erin Awesome! The more I'm learning about it, the more I'm liking the project so it's good to know that you're also focusing on improving the new user experience alongside adding new features. I'll also add that I actually like the concept of a Concepts page (I appreciated it both here and in Prefect's docs) as a compendium of everything related to a given topic that's also more human-readable than just reading through docstrings and function arguments in the API reference. It's moreso that before I start to read the Concepts page and learn about all the nuts and bolts, there's a clear need for me to get a high-level lay of the land first. @Pete Hunt I was actually just about to add a comment referring to that blog post (which I discovered over the weekend) as an example of what a more beginner-friendly layout and flow for a new user might be: building a fully-functional project that gradually introduces concepts like schedules, resources, and configs as needed.