raphael-gold

8 ms·

31.
by raphael-gold 6y ago
Yes, back-end integrations seem to be one of the main reasons why users decide to adopt us. Being able to add their own components is also one of the big reasons. Also, being able to customize the front-end without limits also reassures dev
32.
by raphael-gold 6y ago
we are also planning to expand support to other browser engines as we grow :)
33.
by raphael-gold 6y ago
these are definitely real life example we experience every day. It is hard to draw the line between simplicity and customisability. For this our biggest inspiration is Figma. It's amazing to see non-designers drawing things in Figma w
34.
by raphael-gold 6y ago
yes, that's a pattern that we saw as well! Teams migrating to webflow or wordpress to give back the autonomy to marketers. We also saw teams willing to migrate to the Jamstack from squarespace sites or webflow sites but not doing it be
35.
by raphael-gold 6y ago
we handle CSS at component level, this means that you can add custom css for every element or "section" (UI block) in the site but not at site level. If you import your custom component it can have its own CSS. We don't suppo
36.
by raphael-gold 6y ago
we actually "privately launched" 18 months ago and we knew some people in these companies who had the problem we are trying to solve - so they were willing to try us out. They gave us tons of feedback, we improved the product than
37.
by raphael-gold 6y ago
that's a good point, we are currently discussing this with our early adopters to find the right balance. We might increase this per-visit limits. What would be a fair limit for the business plan according to you?
38.
by raphael-gold 6y ago
that's interesting, we actually have a real difficulty here because our buyers are either marketers or developers. As the problem we are trying to solve is shared between them, both are looking out for solution and we are having a hard
39.
by raphael-gold 6y ago
Oh wow this flow would be really cool! Both observations are linked in a way: the WordPress ecosystem is really impressive and we'd love to create something similar in the Jamstack universe. To do that we are planning to open a "m
40.
by raphael-gold 6y ago
whoops! yes sorry the editor only works with chromium based browsers. We will add a message to let users know!
41.
by raphael-gold 6y ago
The collaborative feature is built from scratch :D It works with WebSockets. At the beginning we used WebSockets to enable autosaving and undo (ctrl+z) in the no-code editor: we save all the actions happening on the elements with unique IDs
42.
by raphael-gold 6y ago
yes for the free tier we host the website. Starting from the paying tiers we enable self-hosting. Today it is still an on-demand feature but we are planning to enable self-hosting in self-service before the summer. We also plan to have one-
43.
by raphael-gold 6y ago
yes, we've seen that one of the drivers for choosing our tool is often a shorter time to market and faster iteration cycles.
44.
by raphael-gold 6y ago
yes, from a no-code edition perspective, it is the problem we are trying to solve. We've seen a lot of users frustrated by their regular site builders because they couldn't do this extra 10% of customization. Another frustration w
45.
by raphael-gold 6y ago
We've typically seen technical people using weweb.io when they want to collaborate on the website with non-technical people (their content creators or marketing team). Interestingly, we see teams splitting the work on the website as fo
46.
Launch HN: Weweb.io (YC W21) – Create websites visually using JAMstack tools
195 points by raphael-gold 6y ago|89 comments