Hello everyone, I’m Daotin, the leader of the front end. If you want to get more wonderful content of the front end, please follow me (with the same name on the whole web) and unlock the new pose of the front end growth.

The following text:

background

As a programmer, having a personal blog is a necessary element to accumulate knowledge and build influence. But because there are so many writing platforms out there, choosing a blog that is right for you can be a bit like shopping. Each blog platform has its own advantages and disadvantages. Here, based on some of my own ideas and personality, I will make a selection of the current writing platforms in the market and select the most suitable blog platform for me.

Each person’s requirements are not the same, the personality is not the same, the selection of the blog is not the same, here is just for my own ideas for screening, do not take the number.

I expect the characteristics of the writing platform

  • Stable (can live for decades with no problem)
  • Security (data cannot be lost)
  • Support for Markdown format (I write mostly in MD now)
  • Full text search support (this is a must)
  • Easy to export backups (not necessary if you are sure you are alive for a long time, but not yet)
  • Convenient Posting (do not need to compile what, mobile phone computers can send text, etc.)
  • Comment feature (preferably)
  • Aesthetic (not a big problem)

Mainstream writing platform in the market

  • GitHub series (Needless to say, the world’s largest gay dating community, a must for programmers)
  • Similar to GitHub are GitLab, Gitee, etc

  • Based on a lot of

    • Hexo
    • Hugo
    • Vuepress
    • Jekyll

  • Based on making the API

    • Pure issue writing
    • The page is generated according to the API to obtain issues

  • Blogging platform

    • CSDN
    • Blog garden
    • The Denver nuggets
    • Segmentfault

  • Note the software

    • Language finches
    • Notion/Wolai
    • Evernote/youdao Cloud Note
  • The curtain
  • Graphite document/Tencent document/fly book document

My note selection

First and foremost, as a technology, GitHub is the best calling card if you want to make a personal technical impact.

Therefore, I plan to build my own blog based on GitHub. And GitHub basically fulfills most of the “features I’d like to see on a writing platform” listed above.

So I now have five options:

  1. Write MD articles directly on GitHub and then push them
  2. Push after compiling into a website using Hexo etc
  3. Use Jekyll to write MD Direct Push to automatically generate websites
  4. Write directly on Issues
  5. Write articles directly on Issues and generate a website based on the API

After some choice, I chose the third way, using Jekyll’s method.

The reasons are as follows:

  • Way 1, the advantage is convenient, the disadvantage is no comment, search trouble, unlike personal blog
  • Approach 2: trouble. I don’t like having to compile every time I write an article, especially if I use a different computer
  • Option 3, the advantage is convenient, support comment, is a personal website, support search, easy to export backup.
  • Way 4, advantages convenient, support comments, disadvantages, not beautiful, others can also add to it, unlike personal blog, export backup is not convenient, and I feel that the warehouse is not safe and stable
  • Mode 5, because of the shortcomings of mode 4, did not choose

Afterword.

Finally, I finished writing this article. When I meet a new writing platform and choose a blog platform, I will take a look at it. The problem will be solved instantly.

My blog address: https://daotin.github.io, welcome!

— End —

Hello, I’m Daotin, the front-end leader, focusing on sharing front-end and cognition. I hope to share my front-end learning and working experience with you here, and record my personal growth.

Want to get more front-end exciting content, pay attention to me (the whole network with the same name), unlock the front-end growth new posture.