-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add libraries to the "Use" section. #77
Comments
dependencies are definitely worth mentioning, all software is based on them. I only have a problem with the sheer number, e.g. digiwf has 250 pages of dependencies, even if I add them automatically I can only display the static data, which has no added value for me. We always try to put all the software we list in relation to us, where do we use it, why this particular software. I couldn't do that with 250 dependencies per repo. But we should make dependencies more prominent, can you think of anything? |
I expect a lot of dependencies to overlap among different projects but I agree that the number will be higher from what can be meaningfully displayed. For displaying one could reduce this to direct dependencies (instead of including transitive ones). Also one hint that static generated pages can contain javascript (e.g. a static json file with the data and a javascript list to populate based on this data including search and pagination). Another thing I find very useful is the overview at "back your stack": https://backyourstack.com/it-at-m. |
https://backyourstack.com/it-at-m was new for me, thx. I will definitely look into this |
One can explore the dependencies for a repository in the dependency graph.
The text was updated successfully, but these errors were encountered: