reboot awesome ipfs

[2color]

What kind of PR is this?

• Reboot the list while reducing the maintenance overhead
• Kill zombies (dead links and ancient and unmaintained projects)
• Use markdown only with no static site
• Update the workflows to only run against readme.md

Notes

• datasets and articles have been removed to keep this focused on projects/services
• Many of the projects here are long inactive and probably not working and take the thunder away from actively maintained awesome stuff — those have been removed. The repo still has the full history for those interested.
• The workflow to remove broken links has been removed as it won't work with the simple README.md format. This is not a problem because we will still get the results from the awesome_bot in the comments of PRs via danger (example).

[welcome[bot]]

Thank you for submitting this PR! A maintainer will be here shortly to review it. We are super grateful, but we are also overloaded! Help us by making sure that:

• The context for this PR is clear, with relevant discussion, decisions and stakeholders linked/mentioned.

• Your contribution itself is clear (code comments, self-review for the rest) and in its best form. Follow the code contribution guidelines if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment. Next steps:

• A maintainer will triage and assign priority to this PR, commenting on any missing things and potentially assigning a reviewer for high priority items.

• The PR gets reviews, discussed and approvals as needed.

• The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution. We are very grateful for your contribution!

[bmann]

Looking good! I think we can create a website again later but that’s a step 2.

can we kill this bot, too?

[meandavejustice]

Link to line that reports for README edits on pull requests https://github.com/ipfs/awesome-ipfs/blob/master/dangerfile.js#L10

[2color]

Thanks for the review @SgtPooki. CI is failing because this PR breaks some of the old workflow/danger config. After this PR is merged, it should be sorted.

[ipfs-gui-bot]

	Fails
:no_entry_sign:	Please do not edit the README directly. It is generated from the data in the data/ directory.

	Messages
:book:	Changes were made within the .github folder.

Generated by :no_entry_sign: dangerJS against 256ca860c06bada4e06e92b0e329de0c985ba196

[patcon]

Thanks for doing this cleanup!

I think we can create a website again later but that’s a step 2. -- @bmann

Big +1 from me, as a fan of that website! The flow of how this repo worked (in the past when it was being maintained) was one that I redirected probably 50 ppl to over the years. The prior markdown/yaml/html example was a beauty to behold and I hope it comes back as an example of how great documentation can be :)

I'll go back in history and extract out a template, and I'll be sure to share that here if I get it cleaned up, so that others like me can keeping demonstrating the documentation flow to others 🙌