@Marvin documetnation to example prefect folder structure best practice?

The Prefect documentation doesn't have a dedicated section to describe a specific folder structure that constitutes best practice for Prefect projects. However, it provides some guidance that can help structure your project, especially when deploying flows and setting up CI/CD processes. One example is the organization of project folders within a repository for CI/CD workflows: Here is an excerpt that can serve as guidance:

├── cicd-example-workspaces-prod # production bucket
│ ├── project_1
│ └── project_2
└── cicd-example-workspaces-stg # staging bucket
    ├── project_1
    ...

This suggests separating different projects into their own folders, with separate subfolders for different deployment environments (e.g., production and staging). You can also have a look at an example

prefect.yaml

file from the guide on CI/CD practices with Prefect, which would be at the root of your project and configure deployments, including external code storage. Please note that the exact structure of your project may vary depending on your specific requirements, such as the number of flows, their dependencies, and any external services you integrate with. The structure above is simply provided as a common example. For more detailed information, here's the link to the guide on CI/CD practices: CI/CD with Prefect If you require more specific or tailored advice on your project structure, feel free to detail your project's needs and constraints.