From 13d074e5db9569f32b8989424b1b4f1410d0cb88 Mon Sep 17 00:00:00 2001 From: Hongsheng Liu Date: Sat, 18 Apr 2026 09:35:38 +0800 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Hongsheng Liu Signed-off-by: hsliu --- recipes/README.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/recipes/README.md b/recipes/README.md index 293c73c48..2e7e97eae 100644 --- a/recipes/README.md +++ b/recipes/README.md @@ -1,13 +1,16 @@ # Community Recipes -This directory contains community-maintained recipe templates for answering a +This directory contains community-maintained recipes for answering a practical user question: > How do I run model X on hardware Y for task Z? -We suggest organizing recipes by model vendor, aligned with -[`vllm-project/recipes`](https://github.com/vllm-project/recipes), and using -one Markdown file per model family by default. +Add recipes for this repository under this in-repo `recipes/` directory. To +keep naming and layout consistent, organize recipes by model vendor in a way +that is aligned with +[`vllm-project/recipes`](https://github.com/vllm-project/recipes), but treat +that external repository as a reference for structure rather than the place to +add files for this repo. Use one Markdown file per model family by default. Example layout: