👋 folks! I feel like Prefect's docs could use some improvement.

Constructive criticism

is my love language, could folks reply to this thread with where you'd like to see them improve the most? Even if you're out of ideas and it's a simple "I once tried to figure this out and it was wayyy to complicated" then that counts!

Create a document that explains what "ephemeral servers" are and why I keep getting errors about them.

My vote would be for some quickstarts or cheatsheets. One page, end to end, and something works, talking through why, with links to the docs to learn more. Remove the need to jump around (create a flow, now over here to deploy, now over here to do X)..... I recently felt like I was bouncing around the docs to connect ideas. I was able to get up and running, but the idea would be something that is cookbook-style and task specific, with recipes that vary in terms of complexity or assumed knowledge (e.g. how to get your first prefect flow onto Cloud and scheduled with managed services)

True about what's news, would be nice to have more info about what's getting in. Currently what I do is to check Github releases directly because is more reliable. Also I really like the resource "big data", I would love to see the content on that page to be more extensive discussed. Also, would be great if the docs could have more guides like that covering others topics covering and Prefect features. https://docs.prefect.io/3.0/resources/big-data

• It's very hard to find all the settings and what they mean • Community resources and github issues and old documentation sites constantly confuse Prefect 2.x and 3.x • the SDK docs are ugly and not well linked to the main docs • there are no good benchmarks to help understand what to expect

Everything related to prefect_test_harness -- what are the features of this? How do I diagnose why it keeps crashing? Testing best practices?