This issue is dedicated for the creations of the mockups for building a richer recipe catalog.
Expand the technologies
Each recipes are focused on a particular use case, example "creating a chatbot" or "building a text summarizer".
Those recipes could, be build with different tools, frameworks and languages.
As a user, I should be able to define the technologies (tools, frameworks and languages) I want to filter the recipes, so I can see only those who are interesting to me.
As a user, I should be able to see the technologies used by the recipes while I'm browsing the catalog of recipes
As an end-user, I want to be able to search for recipes that use a specific combination of programming languages and technologies so that I can find complex workflows or integrations.
Hardware specific
A recipe, might be optimized for a particular hardware architecture. We should be surfacing this to the end-user.
Example: a sample is optimized to be running on Intel infrastructure and as such, use specific Intel components (openvino).
As an end-user, I want to know which specific hardware components a recipe uses so that I can ensure compatibility with my existing infrastructure.
As an end-user, I want to be able to run a recipe optimized for my specific hardware architecture without having to worry about compatibility issues so that I can focus on using the recipe effectively.
As an end-user, I want to be able to filter recipes in the catalog by hardware architecture so that I can find recipes optimized for my specific setup.
Application Patterns
There are more and more application patterns that are being worked on by the community. Those could be related to pre-processing, post-processing, rag, guardrails.
We should also provide categories of recipes that are covering different application patterns.
Contributions
We would like to include a way in the recipe catalog to indicate to the end-users and the community, where they can find the catalog, how they can expand it with their own catalog and eventually contribute to the upstream catalog.
Epic domain
This issue is dedicated for the creations of the mockups for building a richer recipe catalog.
Expand the technologies
Each recipes are focused on a particular use case, example "creating a chatbot" or "building a text summarizer". Those recipes could, be build with different tools, frameworks and languages.
Hardware specific
A recipe, might be optimized for a particular hardware architecture. We should be surfacing this to the end-user. Example: a sample is optimized to be running on Intel infrastructure and as such, use specific Intel components (openvino).
Application Patterns
There are more and more application patterns that are being worked on by the community. Those could be related to pre-processing, post-processing, rag, guardrails. We should also provide categories of recipes that are covering different application patterns.
Contributions
We would like to include a way in the recipe catalog to indicate to the end-users and the community, where they can find the catalog, how they can expand it with their own catalog and eventually contribute to the upstream catalog.
Additional context
No response