Webhook is a thing that people google for information about all the time, and these jerks have just made finding information about webhooks, especially for any other CMS, twice as hard.
Stop shitting in the internet tech namespace commons and spend another five minutes naming your things.
Here's a handy rule, if you aren't 100% confident your project will be in the top 5 google results for your exact name search within two weeks of launch, you're probably shitting in the commons and should find another name.
> Can I self-host Webhook
> No, but we get this question a lot and obviously want to provide it. Honest truth? We'd like to hire another engineer first. That way we can dedicate a resource to making it as good as our hosted solution. It's just not as simple as pushing to an S3 bucket.
This is a deal breaker for me and I suggest most dev shops working for clients.
I don't totally get it. On one hand he's selling this idea that making a dream site can be easy (and it is if it's a very simple site, I guess). He's got 2 decades of experience that say there's more to creating a site than the tool that you're using.
Then running the backend of usual cms systems is made to be hard. But if you know how to install node.js and you're talking about these other components and services like firebase, really that isn't any harder than running click and point software that installs all the backend for you for these other cms solutions. It's not a breakthrough leap in simplicity.
Demolished might be a strong word. It's raised ≈50% more than what was expected but compared to Kickstarter baselines that's not super unusual. As an example, I kicked in a bit for this wallet (https://www.kickstarter.com/projects/supr/slim-the-thinnest-...) that had a $10K target and raised $200K, that could potentially be described as demolishing the target.
This is cool, and there's definitely a need for a better WordPress, but I feel like this setup flow is backwards. Ideally, the flow would be something like this: I go to webhooks.com. Create an account, then create a new project (newproject.webhooks.com). I can edit my site from my site's admin page (newproject.webhooks.com/admin), or as an advanced option, I can install the repo locally to fully edit the code.
Am I missing something here? Don't understand why a user would want to install locally first. Also especially for a non-technical person, this creates barriers to get started.
Kickstarter has a funny dynamic to it. I'm not sure I really understand what motivates people to back projects. This doesn't sound like a bad idea. There seems to be room for several CMS companies and the good ones do well.
I'm surprised that people will kick in donations to fund what is essentially a company.
I wonder if local brick and morter businesses could raise on kickstarter.
I've had a fair bit of NPM installation issues as well and I am a big NodeJS supporter. Often their service is down. If you installed npm a long time ago, it likely doesn't work reliably with the service as it is now and you need to do an "npm install npm" to fix it.
Generally, npm needs to get more professional and I think they are trying.
Not to mention that every language has it's own package manager and all of them have a different idea of how to implement one - total not invented here syndrome IMO
Webhook is a thing that people google for information about all the time, and these jerks have just made finding information about webhooks, especially for any other CMS, twice as hard.
Stop shitting in the internet tech namespace commons and spend another five minutes naming your things.
Here's a handy rule, if you aren't 100% confident your project will be in the top 5 google results for your exact name search within two weeks of launch, you're probably shitting in the commons and should find another name.