Adding Spheron CLI and IPFS service details on the docs

[rekpero]

Describe your changes

We've integrated references about Spheron's role in IPFS storage and website deployment on IPFS. Furthermore, we've enriched our content with details on the Spheron command line interface, including the steps to upload using the Spheron CLI.

Our platform facilitates easy deployment of static apps on IPFS, equipped with an inbuilt CI/CD for seamless automation. For a hands-on look, we've hosted an instance of this documentation forked to our organization. Feel free to explore it at ipfs-docs-77ff9c.spheron.app.

In addition, we conducted a swift lighthouse comparison with the doc.ipfs.io domain. The results highlight a significant performance enhancement in the instance deployed via Spheron.

We genuinely believe in the potential of the Spheron platform and encourage you to give it a try. Should you have any feedback or require modifications, please don't hesitate to inform us.

Files changed

• docs/concepts/persistence.md
• docs/concepts/usage-ideas-examples.md
• docs/quickstart/publish_cli.md
• docs/welcome-builders.md

What issue(s) does this address?

• Add spheron ipfs storage details
• Add spheron command line interface to upload files to ipfs storage

Does this update depend on any other PRs?

N.A

Checklist before requesting a review

• [ ] Passing the beta version of the Check Markdown links for modified files check. Action results can be viewed here.

Checklist before merging

• [ ] Passing all required checks (The beta Check Markdown links for modified files check is not required)

[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 (grammar and spelling checked, any code blocks checked and commented) and in its best form. Follow the docs 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!

[rekpero]

This looks ok to me. However, could you please remove the spheron info added to publish_cli.md? We'd like to keep that tutorial scoped to web3.storage as it currently is.

Yes, I can remove it. Would it be possible to explore other places to highlight Spheron CLI? I believe it could greatly benefit the IPFS community to be aware of alternative CLIs like Spheron, especially in scenarios where services such as w3s might be unavailable. Your thoughts?

[rekpero]

This looks ok to me. However, could you please remove the spheron info added to publish_cli.md? We'd like to keep that tutorial scoped to web3.storage as it currently is.

Yes, I can remove it. Would it be possible to explore other places to highlight Spheron CLI? I believe it could greatly benefit the IPFS community to be aware of alternative CLIs like Spheron, especially in scenarios where services such as w3s might be unavailable. Your thoughts?

I've removed Spheron from the CLI section for now. I will circle back about this again later.