Why did I choose Wiki .js note-taking?

Why did I choose Wiki.js Take notes?

For a long time, I was troubled and felt stuck in the mire of notes, and the accumulated so many notes did not form my own body of knowledge.

The previous way of taking notes

The source of the note

• WeChat public account
• Technical blog
• Paper books
• Official website documentation
• .PDF
• Scattered thoughts of their own
• Web page

Previous note-taking software

There are several:

• For the knowledge notes
• Browser bookmarks
• MarkDown documentation
• Calibre eBook Library
• folder
• Git repository
• Personal blog
• …

What are the disadvantages of the way you took notes before

• Scattered, scattered everywhere
• There is no association, the notes and the notes are relatively independent before, and there is no complete two-way link system
• When I used it, I couldn’t remember where it was, and I had to search again
• The notes included in the clipping are likely to never be read again
• Notes are diverse and not uniform
• Weizhi notes are a proprietary format, can only be seen with it, migration is difficult
• MarkDown images are a big problem, sometimes using absolute links from the local computer, sometimes relative links, sometimes original links (which will cause hotlinks or images to hang), and sometimes uploading to their own image bed
• The Calibre e-book library is expensive to use and is hardly opened for the purpose of reading books
• Personal blogs are sometimes too lazy to update.

My new generation note-taking needs

• Uniform format: all MarkDown + pictures (personal picture bed) + attachments (can be PDF, other documents, audio and video, etc.)
• Two-way synchronization is convenient: two-way synchronization or one-way backup can be done through Git, sync folders, WebDAV, S3, etc
• Two-way link: Pass [[双向链接]] and ![[]] This format of two-way picture links establishes associations for all documents and forms a knowledge network
• Online web pages can be generated for easy online browsing and editing
• The documentation is complete, Chinese translated, and easy to use

Wiki.js advantages

• Beautiful, intuitive, modern interface
• Detailed and extensive documentation
• Support for Docker deployments
• Powerful management
• High degree of customization
• You can choose to make the wiki public or private
• The online MarkDown editor is great to use
• Support Chinese
• History, version finality, version comparison
• Git is synchronized in both directions
• The query function is highly customizable and powerful, and can be connected to ES
• Cloud storage, supported: AWS S3, compatible S3, personal cloud disk
• Local storage and backup
• open source
• Rich integrations
• There will be plugins in the future

Expect more from Wiki.js

Of course, my needs for Wiki.js are not fully met, and I expect it to be able to supplement it in these conveniences in the future:

• Supports bidirectional link syntax and is highly compatible with Obsidian

Above.

My search process

I’ve used the Markdown Wiki tool