Update README.md, remove unused URLs

[stevenjoezhang]

Changes:

• In Vi's repo there are many URLs in README.md, but most of them are removed now... However the link of them are keeped. This PR moves them into the <!-- --> comment

• Deleted a link to an expired website
  See: iissnan/hexo-theme-next@020109d#diff-4b29e98dc086ca7ee0e534c9eb921739

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines.
• Tests for the changes was maked (for bug fixes / features).
  • Muse | Mist have been tested.
  • Pisces | Gemini have been tested.
• Docs in NexT website have been added / updated (for new features).

PR Type

What kind of change does this PR introduce?

• Bugfix.
• Feature.
• Code style update (formatting, local variables).
• Refactoring (no functional changes, no api changes).
• Build related changes.
• CI related changes.
• Documentation content changes.
• Other... Please describe:

What is the current behavior?

Issue resolved: N/A

What is the new behavior?

• Screenshots with this changes: N/A
• Link to demo site with this changes: N/A

How to use?

In NexT _config.yml:

...

Does this PR introduce a breaking change?

• Yes.
• No.

[ivan-nginx]

Wait...

[ivan-nginx]

No need to uncomment badges, they stay there as backup.
No need to switch places badges, it's just variables and don't affect anything.
Also, readme's soon will be strongly refactored. Almost all links with docs must be targeted on site.

Rolling back unneded changes. Thank's.

[stevenjoezhang]

@ivan-nginx https://blog.zzbd.org is not accessible now.
feature-request was renamed to %22Feature+Request%22

[1v9]

@stevenjoezhang His certificate has expired but site is available.

[ivan-nginx]

@ivan-nginx https://blog.zzbd.org is not accessible now.
feature-request was renamed to %22Feature+Request%22

Yep, only this 2 changes enough.

[stevenjoezhang]

@1v9 Seems it was redirected to this: https://dnspod.qcloud.com/static/block.html?d=blog.zzbd.org

[stevenjoezhang]

@ivan-nginx OK, I'll revert some changes

[ivan-nginx]

@stevenjoezhang also, u can do like me: create local branch and then push this your local branch to remote repo, to this repo (coz u have Admin rights, all members they have) and after that create pull-request from this branch to main master. It will be able to change branch here and see live preview before pull merged.

Example: https://github.com/theme-next/hexo-theme-next/blob/security-section/docs/zh-CN/CONTRIBUTING.md

See the difference:

[stevenjoezhang]

@ivan-nginx Thanks, this is a better solution 👍