-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Static web manifesto blog post #707
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please add a paragraph about how this connects to IPFS, and why IPFS is so useful as a deployment target for static sites, and how Orbiter makes use of IPFS?
Feel free to draw inspiration from https://blog.ipfs.tech/dapps-ipfs/#the-benefits-of-ipfs-for-d-app-developers-and-users
https://blog.ipfs.tech/2024-shipyard-improving-ipfs-on-the-web/#service-worker-gateway
@2color resolved the suggestions and added an intro section about why we use IPFS specifically. |
Co-authored-by: Daniel Norman <[email protected]>
Co-authored-by: Daniel Norman <[email protected]>
Co-authored-by: Daniel Norman <[email protected]>
FYI, I'm using this fork PR to test a fix to the deployment workflow that allows it to work for forks too. |
🚀 Build Preview on IPFS ready
|
Thanks @polluterofminds! It's live at https://blog.ipfs.tech/2025-03-static-web-manifesto/ |
Blog post requested by Daniel Norman.