1
0
mirror of https://github.com/osmarks/mycorrhiza.git synced 2024-12-04 18:19:54 +00:00
Wiki engine fork.
Go to file
2022-08-07 01:07:52 +05:00
.github/workflows Update release.yaml 2022-06-05 20:45:00 +03:00
admin Admin: Get rid of QTPL templates 2022-08-06 22:33:37 +05:00
auth Delete package views 2022-08-06 16:35:17 +05:00
backlinks Backlinks: Fix the bug 2022-06-10 18:45:27 +03:00
categories Style and translate /edit-category to Russian 2022-07-24 17:13:51 +05:00
cfg Remove mentions of the sibling hyphae sidebar 2022-08-06 13:49:01 +05:00
files Interwiki: Start implementing 2022-05-22 12:25:22 +03:00
help Remove mentions of the sibling hyphae sidebar 2022-08-06 13:49:01 +05:00
history Recent changes: Fix Russian translation 2022-06-11 12:52:23 +03:00
hyphae Tree: Drop the sibling sidebar 2022-08-06 13:45:10 +05:00
hypview Delete package views 2022-08-06 16:35:17 +05:00
interwiki Interwiki: Translate to Russian and update docs 2022-08-02 14:29:25 +05:00
l18n Admin: Get rid of QTPL templates 2022-08-06 22:33:37 +05:00
migration Mycomarkup: Update to v5.0.0 2022-06-05 15:35:40 +03:00
mimetype Make mimetype.FromExtension case-insensitive 2022-02-20 12:28:33 +03:00
misc Delete package views 2022-08-06 16:35:17 +05:00
mycoopts Backlinks: Fix the bug 2022-06-10 18:45:27 +03:00
shroom Implement redirection hyphae #152 2022-07-01 20:51:22 +05:00
static Admin: Get rid of QTPL templates 2022-08-06 22:33:37 +05:00
tree Tree: Drop the sibling sidebar 2022-08-06 13:45:10 +05:00
user Implement /edit-category 2022-07-24 16:41:16 +05:00
util Mycomarkup: Update to v5.0.0 2022-06-05 15:35:40 +03:00
viewutil Admin: Get rid of QTPL templates 2022-08-06 22:33:37 +05:00
web Delete package views 2022-08-06 16:35:17 +05:00
.gitignore Allow changing the wiki path for make 2021-10-26 12:45:28 +07:00
.mailmap Add a .mailmap 2022-02-01 20:47:32 +07:00
Boilerplate.md Fix typos in Boilerplate.md 2022-08-07 01:07:52 +05:00
Dockerfile Docker: Delete the line 2022-02-19 12:25:23 +03:00
flag.go Remove some unused stuff 2022-02-20 13:11:29 +03:00
go.mod Mycomarkup: Update to v5.1.2 2022-08-06 16:13:21 +05:00
go.sum Mycomarkup: Update to v5.1.2 2022-08-06 16:13:21 +05:00
httpd.go Migrate to gorilla/mux for web needs 2021-07-16 00:47:00 +07:00
LICENSE Change the license to AGPL 2021-03-29 16:13:52 +05:00
main.go Admin: Get rid of QTPL templates 2022-08-06 22:33:37 +05:00
Makefile Move mycorrhiza.1 to help directory 2022-03-26 18:54:01 +03:00
README.md README: Mention interwiki 2022-08-02 14:33:16 +05:00

🍄 Mycorrhiza Wiki

Mycorrhiza Wiki is a lightweight file-system wiki engine that uses Git for keeping history. Main wiki

A screenshot of mycorrhiza.wiki's home page in the Safari browser

Features

  • No database required. Everything is stored in plain files. It makes installation super easy, and you can modify the content directly by yourself.
  • Everything is hyphae. A hypha is a unit of content such as a picture, video or a text article. Hyphae can transclude and link each other, forming a tight network of hypertext pages.
  • Hyphae are authored in Mycomarkup, a markup language that's designed to be unambigious yet easy to use.
  • Categories let you organize hyphae without any hierarchy restrictions, with all the benefits of a category system.
  • Nesting of hyphae is also supported if you like hierarchies.
  • History of changes for textual parts of hyphae. Every change is safely stored in Git. Web feeds for recent changes included.
  • Keyboard-driven navigation. Press ? to see the list of shortcuts.
  • Support for authorization. Both plain username-password pairs and Telegram's login widget are supported.
  • Open Graph support. The most relevant info about a hypha is made available through OG meta tags for consumption by other software.
  • Interwiki support.

Compare Mycorrhiza Wiki with other engines on WikiMatrix.

Installing

See the deployment guide on the wiki.

Contributing

If you want to contribute with code, open a pull request on GitHub or send a patch to the mailing list. If you want to report an issue, open an issue on GitHub or contact us directly.

Consider supporting the development on Boosty.