Add Post: dAppling Introduction #615
Conversation
|
Hey @Namaskar-1F64F! Queuing this up to be reviewed by a few folks. Will get back to you! |
|
@Namaskar-1F64F Do you have an ETA of when your product will be out of beta? |
I do not |
|
We've got several blog posts lined up, so will probably not get this one published for another week or so — one piece of feedback from the team was the reference to "100% up time" being a bit unrealistic when even Filebase and others can't guarantee such a thing. We'd recommend tweaking that a bit. |
sounds good!
good feedback, and makes sense. the intention wasn't to say "we guarantee uptime" but more like, "if you use dappling in addition to your existing frontend, you can get much better up-time". Either way, I will get that changed. |
There was a problem hiding this comment.
HI @Namaskar-1F64F, thank you for submititng this.
It is great to see projects which glue multiple dweb protocols in user-friendly product, would like to figure out a way to connect you with potential users.
Given how extensive the 101 tutorial here is, and how many screenshots and hands-on things it includes, this blog may not be the best venue, or the content needs some adjustment.
Some thoughts, hope you find them helpful:
-
👉 Did you consider publishing this 101 tutorial on your own blog instead?
- Focusing on this would be my suggestion, you really want to control the origin of your content.
- This way you could get featured in IPFS Newsletter for increasing the reach. The newsletter is sent to users via email and also gets published to the blog and https://discuss.ipfs.tech/, so you effectively reuse content to reach more potential users.
-
⚠️ If you wish to land a dedicated post on blog.ipfs.tech, the content might need to be revised:- The entire "The Walkthrough" buries the lead, waters down your value proposition and hides features like ENS/IPNS/your "AI" integration behind mundane screenshots of "how to create a github repo" :)
- For an engaging blogpost, you may want to focus on condensed primer on the value your project brings, e.g. how it takes care of publishing CID using multiple protocols (ENS/DNS/IPNS) to maximize resiliency.
- The step-by-step guide feels like something that should live in as a tutorial in your own blog or https://docs.dappling.network/, after you hook reader's attention (see comment inline).
- For baseline, see similar product showcases from the past (they aged relatively well):
- The entire "The Walkthrough" buries the lead, waters down your value proposition and hides features like ENS/IPNS/your "AI" integration behind mundane screenshots of "how to create a github repo" :)
ps. you could also:
- Consider adding your project to https://ecosystem.ipfs.tech/ and https://github.com/ipfs/awesome-ipfs/
- Add yourself to the list of services at http://docs.ipfs.tech/concepts/persistence/#pinning-services
- Submit a case study (on your own, or joint with one of your clients)
| # The Walkthrough | ||
|
|
||
| I will guide you step by step through the process of deploying a project on dAppling. I will be using a blog template that I created, but you can use any code that you want to deploy. | ||
|
|
||
| The final project, [on the dAppling platform](https://dappling.network/projects/7ebe4f4f-70f0-4705-828b-c610fb1d9ddc), will be accessible at a URL like [hello-ipfs-blog.dappling.network](https://hello-ipfs-blog.dappling.network). | ||
|
|
||
| Let's start exploring! |
There was a problem hiding this comment.
Perhaps https://docs.dappling.network/getting-started/? (or create dedicated single-page 101 tutorial there).
This way the blog post will not get old / outdated as your project evolves, and you don't overwhelm reader with wall of screenshots how to create a github repo :-)
There was a problem hiding this comment.
To add to Lidel's comments, we think it could work well to have you host this blog on your own site and then we'll do a communication collab by promoting it on our Twitter + in the IPFS Monthly newsletter.
There was a problem hiding this comment.
I think your suggestions are a great idea. How are we able to get featured in the IPFS newsletter? Happy to host this 101 content on our blog + promote in the newsletter, then create a simpler / revised post for the IPFS blog.
Great tips on the ecosystem/docs/case study -> we will work on those.
There was a problem hiding this comment.
Hi all. @Namaskar-1F64F 's cofounder here. Thanks for the great suggestions!
@lidel just submitted to the IPFS ecosystem page & already on the awesome-ipfs repo 😄
There was a problem hiding this comment.
@Namaskar-1F64F Just @ mention me here with the post's URL or you can submit it via our form here: https://airtable.com/appjqlMYucNiOYHl7/shrfPrKe112FW3ucv
There was a problem hiding this comment.
thanks @damedoteth I sent in a request 🌌
|
I've updated the blog to be more of a "here's what we do" sort of article. sharing key features of ease of use + access. |
|
|
||
| So the most straightforward way to fetch your content would be directly from an [IPFS node](https://docs.ipfs.tech/concepts/nodes/). Since not everyone is running an IPFS node (yet), you can instead use an [IPFS gateway](https://docs.ipfs.tech/concepts/ipfs-gateway/) in which a third party fetches the content from their node and serves it over HTTPS. | ||
|
|
||
| Since we store the on our `dappling.eth` ENS name, you can also fetch the content through a service like [eth.limo](https://eth.limo). This service first reads the IPNS key that we set, resolves it to a CID, and then serves the content like a gateway. |
There was a problem hiding this comment.
"since we store the..." it looks like a word is missing? What is being stored?
There was a problem hiding this comment.
updated the text here. it's the IPNS key that's being stored as the content hash, but didn't want to get that technical
|
@Namaskar-1F64F Thanks for all the updates to the post! I've gone through and done some copyediting suggestions throughout. |
Co-authored-by: dame.eth <[email protected]>
|
thanks for the suggestions. they all seem sensible. |
|
@Namaskar-1F64F Hey there, sorry for the long delay on this post — had a lot of other priorities to juggle. There was an issue with our blog publishing system between when this was originally submitted and now. Is it possible I could get you to resubmit this post as a new PR and then I can finally get it published? You can just reference this old PR one for legacy comments. |
|
Closing in favor of #657 🙏 |
Howdy, ya'll. I crafted this post about my app: dAppling. We build and deploy code to IPFS. This is a walkthrough of how a user can deploy a simple blog using the platform.