From c39e4d6bf5246034952536d988ebdbae4001cb7e Mon Sep 17 00:00:00 2001 From: Vinta Chen Date: Sun, 16 Aug 2026 16:47:34 +0800 Subject: [PATCH] docs: restrict sub-items to awesome-* also-see links Removed the companion-project clause from the Sub-item definition in CONTEXT.md's vocabulary. Its examples (aws-sdk-pandas under pandas, flower under celery) went stale this sitting: those companions were promoted, re-homed, or deleted. Per the maintainer's 2026-08-16 policy decision, sub-items are now reserved for awesome-* also-see links only - a companion project must earn a full Entry in its proper Use Case or not be listed. Co-Authored-By: Claude --- CONTEXT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTEXT.md b/CONTEXT.md index cda364e5..434afbc7 100644 --- a/CONTEXT.md +++ b/CONTEXT.md @@ -10,7 +10,7 @@ The editorial domain of awesome-python: which projects the list carries, how the A single listed project: `- [name](url) - Description.` The unit that is admitted, displaced, or pruned. Named by PyPI package name when one exists, else by repository name. **Sub-item**: -An indented link under an Entry (awesome-django under django, aws-sdk-pandas under pandas, flower under celery). Not an Entry: it holds no slot, does not count against the Cap, and rides its parent — re-homed or removed with it. Maintainer-only placement, for a companion project whose job is inseparable from its parent's (flower monitors celery) or an awesome-* also-see list. +An indented awesome-* also-see link under an Entry (awesome-django under django, awesome-pytest under pytest). Not an Entry: it holds no slot, does not count against the Cap, and rides its parent — re-homed or removed with it. Maintainer-only placement, and only for awesome-* lists: a companion project either earns a full Entry in its proper Use Case or is not listed. **Thematic Group**: A bold group line (e.g. "AI & ML", "Web Development") that clusters Sections in the TOC and the Projects body.