Clean up README.md, made SETUP.md

[kirbyfern]

Summary

• Clean up README
• create separate SETUP.md
• update CONTRIBUTING

PREVIEW: https://github.com/kirbygit/docsify/tree/update-readme

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Docs
• Build-related changes
• Other, please describe:

If changing the UI of default theme, please provide the before/after screenshot:

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
  this is a PR for update readme, add Discord to site, other improvements/changes #1224

You have tested in the following browsers: (Providing a detailed version will be better.)

• Chrome
• Firefox
• Safari
• Edge
• IE

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/docsify-core/docsify-preview/8q5b9k4kd
✅ Preview: https://docsify-preview-git-fork-kirbygit-update-readme.docsify-core.vercel.app

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 0276fb7:

Sandbox	Source
docsify-template	Configuration

[kirbyfern]

#1224

[trusktr]

Thanks @kirbygit For the ideas! As we chatted about,

• Let's make separate PRs, one just for the tag line for example. (don't forget to set the base branch of those PRs to Docsify's update-readme branch)
• Regarding SETUP.md I believe we should have content like that in the docs/ so we can show it on the site as well. People can still navigate the files here on GitHub too.

[trusktr]

Another thing is (and note I made a separate PR for CONTRIBUTING.md, but maybe we should merge into one PR) maybe we can put the contributing guide in the docs, and link to it?

For example, this is how my one of my projects' CONTRIBUTING.md files looks like: https://github.com/lume/lume/blob/develop/CONTRIBUTING.md (WIP)

My thought is then we can have all things easily in one place. Having the root CONTRIBUTING.md file satisfies the GitHub community requirement (https://github.com/docsifyjs/docsify/community), so in my project's case I just link to the docs.

[kirbyfern]

Thanks @kirbygit For the ideas! As we chatted about,

• Let's make separate PRs, one just for the tag line for example. (don't forget to set the base branch of those PRs to Docsify's update-readme branch)
• Regarding SETUP.md I believe we should have content like that in the docs/ so we can show it on the site as well. People can still navigate the files here on GitHub too.

Will make a small PR's for every change made. I agree that linking the SETUP.md inside /docs so we can show it on the site as well and people can also navigate the file from here. For that setup.md, do you think that content is perfectly fine?

Another thing is (and note I made a separate PR for CONTRIBUTING.md, but maybe we should merge into one PR) maybe we can put the contributing guide in the docs, and link to it?

For example, this is how my project's CONTRIBUTING.md file looks like: https://github.com/lume/lume/blob/develop/CONTRIBUTING.md

Whats the best way to merge that PR to here?

[trusktr]

@sy-records this is good, honestly we need more details because "magical" on the cover doesn't say much. Although I think we might become incompatible with IE11 now, and we shouldn't mention experimental and incomplete/broken SSR support.

[sy-records]

Isn't there a description of some Features below? https://docsify.js.org/#/?id=features