Hexo, git push, xxx.github.io problems, some usage obstacles after successfully building blog.

  node.js, question

XXX. github.io has been successfully deployed on Github with hexo.
Now my operation is the three steps provided by hexo after writing xx.md locally each time:
hexo clean
hexo g
hexo d
Pushing local articles to remote github is like this, which goes beyond the steps provided by git:
git add .
git commit -m “xxx”
git push origin master

If I only use xxx.github.io to write a blog for hexo, it is good to say that I will only use the three commands of hexo. However, if I hope xxx.github.io can also display some self-made web page index.html, then I must push through git. This will cause a conflict. The remote server is already ahead of the local, so I need to pull down the remote server first. For obsessive-compulsive disorder, I feel that I have inadvertently generated a lot of garbage that I don’t need.

So was it the wrong way I used it? Is there any good way for me to balance hexo, git and xxx.github.io conveniently? How can I make good use of github page without worrying about such conflicts?

Put your web page into source, and every time hexo g is included.