Hey all,
I made this myself and am looking for feedback from anyone with time to spare some
Thanks in advance!
- Attractive and professional landing page
- Fully featured demo site, free to try
- [1] Over 10 SDK's built for all popular platforms (react, vue, angular... etc)?!!
I would be happy to have implemented just a fraction of what you've done... Like a sibling comment said; you should be very proud of yourself
Get ready to scale :)
[1] https://github.com/BuilderIO/builder/tree/master/packages
My concern for you is there are a lot of GUI site builders out there. So I wonder how this stands out?
Your concern is totally valid, and I perhaps need to make this more clear on my landing page. But Builder is different because it works like a headless CMS.
It can hook into any site to power page building, regardless of what tech stack that site was made with. So as opposed to other site builders that lock you into their system completely and can't hardly be extended with real code and engineers, Builder does this in reverse.
Companies come to use my product when they have already built some kind of custom website, but need to provided non-dev users with the ability to quickly build and test pages.
It just takes one simple API integration to make all that possible and retains your freedom to completely own your tech stack.
Anyway, happy to elaborate further if you like!
Edit: typos
So far I've been working on this product for about a year and a half, though I did spend almost a full year beforehand just trying to figure out how to approach/solve this problem in the first place
I point out swamp code and it’s “yeah I’ve been meaning to fix that but I don’t have time [fixing these 20 other debts we created]”
And yes - this is actually totally doable. I've done it so far for platforms like Wordpress, Shopify, and Magento, as well as a couple custom internal admin tools of customers so far.
It isn't something I have standard pricing and docs on yet but I am totally open to doing that. Do you have a use case in mind?
Why? Ongoing "battle" between a large CMS (AEM) and a more modern SPA using microservices. Our claim is that the SPA is actually a superset of everything. It can SSR (like the CMS), it can also get data to display (like the CMS). All that is missing is a service for such data (we have other services delivering domain specific data).
Now the problem is not in a data service, but rather in the whole infrastructure around it - to make it easy for an content editor to use. These people like drag and drop and they would love your solution.
Great job!
Maybe consider pricing by amount of content and requests?
That said if someone wanted to get real fancy they could comb through the content and replace the image URLs with some of their own. You are right, this will have to be sorted out if this becomes a common way people use the product.
Thank you for the feedback
I don't think anyone would "could comb through the content and replace the image URLs" to save a few dollars, as the development effort would far outweigh the cost savings. So maybe you are OK there.