If you are interested in contributing to sheets.wiki, you’ll have to understand the basics of Git , making pull requests, and Obsidian. You can also suggest edits in the Spreadsheets Discord Community.
If you are unfamiliar with making pull requests, W3 Schools has an excellent tutorial. If you are unfamiliar with Obsidian, please refer to their documentation. If you need assistance with this, you can ask in the SDC.
Edits and new articles should be in accordance with the Style Guide.
Quickstart
- Fork the sheets.wiki articles repository and clone it to your machine.
- Create an Obsidian vault from your forked repository. Alternatively, you can use Foam or any other PKM system that supports wikilinks.
- Make whatever edits you’d like. Make sure to
git pullrelatively often. - Push to your fork and make a pull request. A maintainer will review and potentially merge it.
Recommended plugins
Obsidian supports a number of community plugins that greatly enhance the editing experience. The only plugin I would really recommend adding is Shiki Highlighter, configured to support gse.
FAQ
Why Obsidian/Quartz instead of an actual wiki framework?
Ordinary wikis require a server to handle editing, and sheets.wiki doesn’t really need that since it’s so lightweight. It’s what we call a static site—its server just sends static pages, and doesn’t receive information other than requests for said pages.
Also, it is much cheaper and easier to maintain than a traditional website with a backend.
Why can’t I edit the wiki on the website?
sheets.wiki used to support this kind of editing through Decap CMS, a system which essentially used Astral’s Github account to push edits. While this worked, the editor did not autocomplete wikilinks and lacked core features in most PKM systems. While not having a built-in editor complicates some things—having to make pull requests, for instance—I think it ultimately leads to a superior editor experience.
Will sheets.wiki ever change frameworks?
Probably, but not for a while.