PrefectHQ / prefect-recipes

Snippets and templates representing common Customer Success patterns
https://PrefectHQ.github.io/prefect-recipes/
Apache License 2.0
238 stars 29 forks source link

Find a solution to sharing more in-depth examples for Prefect Collections #155

Open ahuang11 opened 2 years ago

ahuang11 commented 2 years ago

💻

What problem are you trying to solve?

See discussion here: https://github.com/PrefectHQ/prefect-collection-template/pull/90

Describe the solution you'd like

Are there plans to make a prefect-recipes webpage, combining visual cards like https://orion-docs.prefect.io/recipes/recipes/ and filtering ability like https://www.prefectlabs.com/experts? Then all collections can link to a specific URL with the filter applied corresponding to the collection, e.g. Click [here](https://www.prefectlabs.com/recipes?tag=prefect-snowflake) to see recipes related to the collection

I imagine the single source of truth / backend data can be the prefect-recipes page with addition of tags that indicate whether it's core prefect or a prefect collection.

I feel like if we add a link to those specific recipes to each repo, there will be three places that we need to keep track of, which is likely to become out of sync:

  1. prefect-recipes
  2. Prefect docs
  3. the corresponding Collection

Describe alternatives you've considered

Alex proposed: "Based on a scan of the recipes repo, those recipes are for 1.0. I don't think that we have any recipes that use collections, which is something we should fix! I think the link to the Prefect Recipes repo can be added on a case by case basis once a recipe for the given collection exists... I think it makes sense to have a link to Prefect Recipes repo in the collection repos that correspond to those recipes. Potentially even link to those specific recipes in addition to a link to the recipes repo landing page."

Documentation, Adoption, Migration Strategy

No response