richardlitt / meta-knowledge

💡 A list of knowledge repositories

meta-knowledge

💡 A list of knowledge repositories

Use GitHub repositories to document everything. \o/

Repositories

• Aizat Faiz
• Alex Pliutau
• Alper Kanat
• Andrew Zappella
• Benjamin Lupton
• Bhupesh Varshney (Source on GitHub)
• Bruno Coimbra (Source on GitHub)
• Blue Book (Source on GitHub)
• Caio Gondim
• Carlos Delfino (Source on GitHub)
• .CLI
• Daniel Schildt
• David Gasquez
• E. Ferreira
• Eyal Levin
• Ezekiel Kigbo
• Harald O. Bakke
• Joseph Rex
• Josh Johnston
• Josh Pierro
• Junwei Zhao
• Kamil Ronewicz
• Kirill Gorbachyonok
• Manassarn Manoonchai
• Marc Loupias (Source on GitHub)
• Marshall Bowers
• Mathias Borgmalm
• Mehmet Kanat
• Mingyang Li
• Myles Braithwaite (Source on GitHub)
• Nick S. Plekhanov
• Nikita Voloboev
• Nimalan aka mark1626 (Source on GitHub)
• Oleh Kuchuk
• Omar Bahareth
• Piotr Stojanow
• Prasanna Loganathar
• PuiMan Cheui
• Rachel Brindle (Source on GitHub)
• Richard Littauer
• Sam Yamashita
• Simon Vocella
• Stephen McAleese
• Stephen Whitmore
• Tommi’s Jam — Source
• Yoshua Wuyts
• Zeh Fernandes

Contribute

If you know of any more, add them here! Please alphabetize your entry.

If you're interested in downloading all of the repos at once, see the discussion and shell script provided in #1.

Resources

For more knowledge sharing repositories that are not personal you can check these:

• Learn Anything
• Awesome Lists

Other knowledge sharing compilations:

• Maggie Appleton's compilation
• Nikita's compilation
• KasperZutterman's compilation
• Best-of Digital Gardens

License

CC0.

meta-knowledge's Issues

Add 'Rules' Section

There's a lot of good content compiled here and it's great to see so many people documenting (and sharing their documentation) on Github.

I do believe that a small section talking about basic rules or recommendations prior to adding a new repo to the list could be useful though.

After navigating a dozen or so repositories off the list, I've come across a couple that contain PDF versions of books that are not open-source or in the public domain. That, in my opinion, is a good example of something that could be added to the rules as something that should be avoided.

Other topics that could be covered are:

• Licenses: make sure the repositories have chosen and displayed the appropriate licenses so people know how to use the content they find

• Contributions: Proper contribution guidelines

• Link Back: Suggest a link back to this repository to stimulate the creation of a network of documentation and knowledge sharing

Add more metadata on the repositories

Hi, it would be nice to be able to have more metadata of the repositories, such as number of stars, last commit, watchers, contributors...

Something like this site. So if you agree I don't mind doing a PR with the updated readme entries with the following format:

| Name | Topics | Popularity | Metadata |
| ---------- | :---------- | :----------: | :----------: |
| [**Blue Book**](https://github.com/lyz-code/blue-book) | DevOps, Life automation, Python, Data analysis |[![stars](https://badgen.net/github/stars/lyz-code/blue-book)](https://badgen.net/github/stars/lyz-code/blue-book)| [![contributors](https://badgen.net/github/contributors/lyz-code/blue-book)](https://badgen.net/github/contributors/lyz-code/blue-book) [![watchers](https://badgen.net/github/watchers/lyz-code/blue-book)](https://badgen.net/github/watchers/lyz-code/blue-book) [![last-commit](https://badgen.net/github/last-commit/lyz-code/blue-book)](https://badgen.net/github/last-commit/lyz-code/blue-book) [![open-issues](https://badgen.net/github/open-issues/lyz-code/blue-book)](https://badgen.net/github/open-issues/lyz-code/blue-book) [![closed-issues](https://badgen.net/github/closed-issues/lyz-code/blue-book)](https://badgen.net/github/closed-issues/lyz-code/blue-book) |

Example:

Name	Topics	Popularity	Metadata
Blue Book	DevOps, Life automation, Python, Data analysis

Submodule maybe?

It would be handy if you could submodule the referred repositories so one can pull them altogether in one go.

subtree is rather copyright invasive that I'd not look into it though.

Add https://github.com/plutov/notebook

https://github.com/plutov/notebook