Feat/5.0

[QingWei-Li]

Please makes sure these boxes are checked before submitting your PR, thank you!

• Make sure you are merging your commits to master branch.
• Add some descriptions and refer relative issues for you PR.
• DO NOT include files inside lib directory.

• New Feature: Generate static html Generate static HTML site (static site generation, SSG) #136 ref Generate static HTML docsify-cli#55
• New Markdown Syntax: Friendly doc Helpers, Friendly doc Helpers #413

The other two features I don't plan to develop. Not much effect.

@docsifyjs/core @jhildenbiddle

First of all, I have to apologize.

I haven't read the issues for a long time and haven't noticed your email. I may have to leave this project.

I have promoted @timaschew to owner and hope that you can continue to maintain docsify.

This is my last contribution to docsify. If you feel that there is no problem, then I will release 5.0. And give the release permission to your.

[QingWei-Li]

@timaschew
If you need permission to post, please let me know your npm account.

[timaschew]

As @jhildenbiddle mentioned here: #657 (comment)
I agree with him to delay this PR (bump to 5.0) until some bugs are fixed which should be released as 4.x
Merging this without bumping the major version seems not an option since this PR contains some breaking changes like the syntax for the helpers.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[trusktr]

Develop has diverged from this PR. There's 11 files with conflicts. What do we want to do?

I think we either

• take effort to clean up the PR
• or close it, and open a new branch

Either way, we should not let existing branches get stale. After each pull request is merged, we should merge develop into the breaking-release branch (that is, if we want to keep the breaking changes).