Building a Cool Memos Using Gitblog#
Create a new repository on GitHub specifically for storing memos, and only use Issues. Open the Gitblog website, create an account, and select the repository you just created. Fill in the blog name, upload a website icon, and you're done!
It's as simple as that.
Of course, writing a blog on GitHub's Issues may seem a bit strange, as the plain text formatting lacks aesthetics. Therefore, I thought of using it as memos, without the need to install the offline memos project through Docker. Keep things simple and get it done in a few minutes.
You can treat it as a personal circle of friends. If you don't want it to be public, simply close the project.
The principle is simple: convert GitHub Issues into a beautiful blog page, with a visually appealing backend for data display.
After selecting the specified repository for Gitblog installation, an external link with the repository name will be automatically provided. I know that domain names are not a problem for you. Developers offer free domain name binding services, just add a CNAME record behind the domain name service provider. Remember to go back to gitblog.io, enter the domain name address, and save it for it to take effect.
The entire deployment process will not take more than ten minutes. The theme layout does have some issues, but perhaps it can be resolved by modifying the CSS to change the style.
The page loads instantly, and the overall experience can be summed up in one word: fast!
🎉Welcome to visit the open memos, "Cold Bench Murmurs"
Benefits of Editing on GitHub#
- Markdown syntax can be used
- No need to worry about uploading images or traffic issues
- There are beautiful tags, projects, milestones, and progress on the right side, allowing ordinary fleeting notes to take flight
- No need to worry about data backup, even if the Gitblog project is gone, all content will be preserved in the GitHub repository Issues
- GitHub's search function is powerful, so you won't have trouble finding notes even if you have a lot of them
- Open notes, comments can directly jump to the project repository. If you have any questions about the notes, just leave a message in the Issues, allowing blog writers to experience the joy of programmer development
There is No Perfect Note-Taking Tool#
- Currently, it feels inconvenient to use, as you need to open GitHub and enter Issues to edit text, unlike Flomo-like tools that can be opened anytime to record
- The paid version of Gitblog provides an API, which is probably used to solve the problem of fast input
- The free version of the page theme is limited to only one, and the key is the layout. After clicking on it, the title is too big, giving a shocking feeling
- It seems that it can only be used with stairs. If you find it difficult to even open GitHub, then it's better not to play with it
ps. To speed up opening GitHub Issues, simply add a button in Quicker. With a flick of the mouse, you can quickly open it. Very convenient.
Gitblog is a lightweight, simple, and powerful blogging solution.
This tool can convert GitHub Issues into a static blog website, and it's free for individual blogs.
Official website: https://gitblog.io/