Anduin2017 / Anduin2017/HowToCook
关于分类优化的建议: 引入标签代替类别
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 102k
- Forks
- 11.1k
- Avg merge
- 14h 21m
- Merged PRs (30d)
- 2
Description
现在的分类其实有很多冲突和纠结之处。
像是{早餐/煎饺}用的是速冻水饺，所以应当同时属于半成品加工，甚至它也应当属于主食（或者那个被人叫做锅贴…）。
同样的，{半成品加工/水饺}也可以作为主食；{汤与粥/皮蛋瘦肉粥、小米粥}也可以作为早餐；{荤菜/.\*(炖).\*}
其实问题在于分类用的类别本身互相之间不是同一个分类标准。
所以在想，是否采用Tags会比细化分类标准更好。这样的话：
- 解决不同分类标准的类别造成的分类混乱问题
- 可以兼容多种分类方法
- 查阅者可以更好地找到自己想要制作的菜肴
- 多种做法的同一种菜品可以很好的区别和查阅
- 同时，针对之前有人Pr的八大菜系问题，菜系作为1个标签相比类别可以在保证分类功能的情况下减少冲突
- 用菜系作为类别，功能性不如原先的素、荤、主食
- 有些菜在多个菜系中都有，首先可以避免争议，其次可以变成多种做法
- 更加美观
关于在mkdocs中使用tags这点，可以使用：mkdocs-tags
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing category scheme described in the issue and the linked mkdocs-tags documentation. Compare how tags could represent the examples and cuisine labels without losing discoverability. Done means an agreed tag model and a documented implementation plan for replacing or supplementing the conflicting categories.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100