In our case, our use case was we wanted a chat interface into our docs. We provide dour docs, forum, and open source examples as the knowledge from the GPT, via this crawler. Base GPT isn't that knowledgable about our product, but with this approach its significantly more capable of answering detailed questions about how to integrate Builder.io or deal with errors
Totally fair. The intended argument is that downloading (and parsing and executing) an entire page just for one button click to load is slow.
But if you can hydrate granularity, and prefetch smartly (based on visibility, analytics, etc) things speed up a lot.
If done right, there is no delay on interaction, and a lot less time and resources required to load a page, increasing lighthouse scores and TI specifically
Thats what we’ve seen in the field too, the FAQs in the article link to some real world examples. Tho I can’t say our prefetching is as smart yet in practice as we want, so sometimes there is a delay on very first interaction. There is a straightforward way to improve this tho that we are working on
Oops, thanks for catching. I implemented the client side routing there from scratch with partytown and must have forgot a check to make sure the ctrl/cmd/shift keys aren’t down when canceling the event for a client side routes. Will get that fixed this week
If anyone is looking for something like this but uses flexbox positioning (no absolute positioning) and support for other frameworks (Vue, Svelte, plain HTML/CSS, etc) - https://github.com/BuilderIO/figma-html
Oh interesting I haven't heard of indie hacker, I'll check it out
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
Not at all - you can easily balance your usage of Builder and your own code as much as you like. You can put Builder content within your code components, and you can easily use your code components within the Builder content.
Yeah, your concern is totally valid. One thing that would hit people who cache the API is they would also be subject to fair use policies for bandwidth usage (namely serving the images used). Pretty much all CMSs have some form of this that basically requires large bandwidth users to pay for one of the higher price plans anyway so not to be losing money on customers
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.
Thanks! I'm not sure what a company posting means but yes? Haha the company is just me anyway
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.
And what you ask for is actually possible in two ways -
One is to use webhooks to side load the data. Aka when people publish content in Builder, it will trigger a webhook sending the data to an API of yours to store and then serve how you like. You can see some docs on that here https://builder.io/c/docs/webhooks (and feel free to reach out for further explanation - I'll create a detailed guide on this at some point)
The second way, which is not available yet but will be soon, is an embedded Builder editor you can work into your internal software. This is not publicly available yet but is used by one customer and will be available more broadly soon. If you're interested in trying that when available shoot me an email at [email protected]
Thanks for the question! The big difference is that Builder works like a headless CMS - so you can easily hook it up to existing sites with an API.
This is most useful for existing sites or apps that have a lot of custom coded content, but you want non-devs to be able to make and manage landing pages and other content without relying on developers at all
I've been working on this for about a year and a half now, though I was able to get my first customer just a few months in.
The first place I went to was ShopStyle, since I had worked there previously and had experienced the problem that Builder aims to solve first hand (non-dev teams needing to build new pages all the time, and devs without time to constantly code up all this new content).
So since I had a good rapport with them and this was a pretty "hair on fire" problem with them, they were willing to be my first customer. I also charged them very little - at first at least ;)
Then I got new customers from word of mouth and from being able to demonstrate what ShopStyle had done (the pages their non-devs were making and how it was helping their business). When people liked the product they were happy to refer me to others who could use it. This was slow but it eventually got me a handful more initial customers, some I knew personally and some I didn't.
Anyway, happy to answer more about the process if you have other Qs or interested in more detail!
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?