recommend:
I have been wanting to create a document management system similar to Kanyun for a long time. I searched for a long time on the Internet and found a few better ones to share with you.
1. Mindoc open source software
2. BookStack is also open source software
3. Docsify is the same as the documentation generated by GitBook. We can directly deploy the documentation website to GitHub Pages or VPS.
These three are relatively powerful, but they need a certain programming foundation (PHP, Go), and there are certain thresholds. Anyway, I have studied for a long time haha...
Recently, I accidentally found one that can be built without any programming foundation and share it with you: docsify
At that time, I didn't think there was anything strange. I didn't know it was a static blog until I found out that quick-markdown was used below and read his deployment blog post. Similar to hexo, it is deployed on github or gitlab (I don’t know if hexo can be deployed here). The author deploys it on gitlab, so the speed is not slow. I also struggled with hexo earlier, but I can’t say it’s troublesome. Just installing the software locally, submitting commands and writing blog posts gave me a headache. Even though some automated tutorials were released later, I still don’t like it (I really find it cumbersome).
quick-markdown is a markdown display tool that can quickly generate a display page for your markdown file, that is to say, after uploading the .md file, directly accessing this file will parse it into a web page, then you will have it later It is deployed as a blog (if it is deployed with gitlab like the author, you can write and post directly in gitlab without downloading any software to upload files, etc.).
advantage:
- easy to deploy
- Migration is simple, directly packaged and taken away
- pure static
- Deployment and operation do not cost a penny (github/gitlab)
- A markdown file is an article or page (it can be said to be DIY at will)
- With Markdown syntax and html+css, you can build personalized pages
- There are 7 built-in themes, and the theme writing is not troublesome. Only html, css, you may use js
Deployment tutorial:
1. Before you use this project, you must have a github account and create
你的github ID.github.ioa warehouse
2. Fork the project to the warehouse project address you just created GitHub - mengrru/quick-markdown: a markdown display tool that can quickly provide your markdown The file generates a display page.
3. Select Settings -> Pages, check gh-pages in Branch in the Source column, and save. Then select Actions in the upper menu, click the green button in the middle to open the Action function, and bind a custom domain name in the page.The deployment has actually been completed here.
The deployment method of gitlab can refer to the author’s tutorial. Compared with github, the advantage is that it will not expose the original blog warehouse. Gitlab’s native WebIDE can be directly used as a blog background to publish articles, and no special things are required for speed
. What I see is that gitlab startsCI/CD -> Pipelinesthis function (similar to the action function is automatic deployment). It needs to verify the credit card to ensure that you are a real person and not a robot. After reading the document, I learned that the article list on the homepage of this blog relies onfiles-listthe author’s built-in article list plug-in. By running this plug-in to update the article list on the blog home page, gitlab can start and run by detecting the file update status. Set in advance Plugin commands. If you can't use Gitlab, then the same server can also complete this function.
Server deployment:
The environment I use is: Centos + pagoda
server deployment can be said to be very simple, although the original intention of this static blog is to deploy without spending a penny, due to the slow speed of github, and I found that compared with the first two after deployment The server seems to be simpler.
1. Download the project locally and upload it to the server to decompress, cut all the files in quick-markdown to the root directory of the website and create a new domain name: www.example.com 2. The core
configuration file of the blog is config.js, which contains Set the theme, blog name, blog post storage directory, etc. See the explanation below for details3. The path after configuration is: /?docs/xx.md
Conclusion:
Although the theme is html and css, it may not be very friendly to Xiaobai, but no one cares about this project and no one develops the theme.
I think this project is especially suitable for people who purely write and record their lives, and the speed of pure static files is also very fast. Imagine using typora to record some things alone at home at night, save them and throw them directly on the server, or even save and sleep after writing and throw several files together next time after writing, because you don’t need a database and want to migrate in the future. Pack it up and take it away.No other complicated configuration, just regain the fun of writing, the file determines the page, highly customized