- Not intended to be beginner-friendly, or written like a guide (although you can write like that)
- Centralized reference website to other websites / any information you could want: links to utility websites, chart guides, data tables, etc.
- If you find something useful, put a link to it, even if it's in Japanese
- Someone else / you can summarize it later if they want to
- Don't worry about organization -- I will take care of it
- Create new pages if you have ideas for them
- Add a link to it from the homepage under "Unorganized"
- I might merge or restructure new pages as needed
- Don't bother with writing quality, point form / unfinished is fine
- Would rather have the information at all than have it neatly organized
Wiki.js allows you to create and edit both Markdown and rich text pages. You can use whichever but each has their downsides.
As a general rule, I would say stick to Markdown. Chart guides can be created in rich text because placing images is kind of painful in Markdown.
Markdown pages <-> Rich editor pages can be converted with the "Convert" option under the menu.
- Disadvantages:
- Some formatting can't be done in rich text pages
- can't colour text
- can't use footnotes
- won't be able to use custom javascript elements (if I ever add them)
- Advantages:
- GUI is easier to use
- Images are much easier to place/align
- Tables are easier to create
Formatting images in Markdown is complicated unfortunately, here's a guide for some common tasks.
https://stackoverflow.com/a/21242579
# width
# height
# both
<center>
</center>
The blank lines are important or the parser will not read the Markdown syntax.
<figure class="tright">
<img src="/your_image_here.png" width="200" />
<figcaption>figure caption here</figcaption>
</figure>
(continue the article here)
I investigated a few different wiki softwares:
- Miraheze / self-hosted Mediawiki
- Wiki.js
- Outline
- Google Docs
Why not Miraheze: After editing it for a while I found it kind of constraining, as since it's a "public" wiki I couldn't really talk about what I want. This led me to stray away from it.
- (+) much more powerful templating software out of the box
- (*) vibes are not as homey? I want people to feel like they can edit anything and MediaWiki feels too rigid
- (-) not as private: for example, I don't want to talk about Mythos on a public wiki
Why not (self-hosted) Mediawiki: Self-hosting a wiki solves the problems with Miraheze and I'd be down for it if people are willing.
- (+) much more powerful software
- (+) visual editor is pretty good
- (*) vibes are not as homey?
- (-) probably requires a stronger server; might have to host on a paid server
Why not Wiki.js:
- (*) vibes are pretty good
- (+) Has some nice features out of the box: Discord integration (easy way to make accounts), backup to git repo
- (-) Missing a few features that would be nice for wiki editing, like page/element templates
- (-) image pasting is awkward without some modding (I'd have to rebuild Wiki.js)
- (-) Is not being actively maintained
Why not Outline: I found out you couldn't colour text and noped the heck out. At least Wiki.js has a backdoor where you can use raw HTML.
- (+) nicest UI, like Notion
- (--) formatting is way too limited
Why not Google Docs: I also thought about just having a Google Drive folder for people to put google docs in. For some reason I got halfway and abandoned it.
- (+) vibes
- (+) free, 100% availablity
- (+) easy to use
- (-) must be invited to edit it
- (*) Wiki.js/Mediawiki is flexible enough to host Javascript calculators which could be useful, can't do it with Google Docs