luanti-org / luanti-org/contentdb
Add recommendation to packages
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 115
- Forks
- 62
- Avg merge
- 19h 7m
- Merged PRs (30d)
- 5
Description
Problem
Actually aren't great way for recommendation some packages in other packages. Now can package publisher use only:
- collections (actually the best but in the first package you can't see, what is in package and now are collections relatively hidden)
- optional_depends (it is for technical depends but not for thematic recommendation)
- write it in README and mod page (not good visible for downloaders)
- write it on forum/discord (nobody see it)
Do you think that your mod will be great with some game although is technically usable in more other games? Do you think that for your mod is great using texturpack from other creator? Or did you make two technically not-depends mods but for decoration is nice, when somebody want one from them, use both?
Solutions
Add category (as is depends and optional_depens) named "recommended_with" or similar - for thematic recommendation.
Alternatives
Big rework of colletions but I think that it will be so much harder to work and not so beneficial as category "recommended_with".
Additional context
I think that this doesn't need picture.
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
No files or tests are named. Begin by locating the package metadata handling for collections, depends, and optional_depends, then determine where a recommended_with category would be exposed to downloaders. Done means publishers can declare thematic recommendations and users can see them clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100