142 karma · joined July 21, 2019
For email domains, we don't handle your emails. You could use any email provider that you want, like MailChimp, Sendgrid, etc. Since connecting custom domains doesn't require you to point your nameservers to Typedream, you can add MX records, etc. that is usually required for you to set up your email provider.
Thanks for your explanation on A/B testing, that makes sense and we have had a couple of similar requests as well! This is definitely something we're looking to add as a feature.
- A/B testing: not supported yet, although we are thinking on building this. Would love to learn more from your use case! - Incoming referral, bounce rate, time on page are available through our built-in analytics. If you're familiar with Plausible https://plausible.io, we're using their self-hosted version to offer the analytics feature, so you should get everything they offer. - Not familiar with n8n.io, looks like it's similar to Zapier. We don't have any integration like this yet, but most functional components that you can add to your Typedream site (like forms, waitlist, etc) can be done using HTML embeds. For example, to add a form, you can embed an Airtable form in your Typedream site. This means that any automation supported by those tools can be used.
With that said, interactions such as allowing customer to buy a product, sending emails, and adding orders to Airtable/Google Sheets can be done by using a third party service, like Stripe Payment Links to allow users to buy a product, then use Stripe's functionality or Zapier/n8n.io integrations to send emails or add orders to Airtable/Google Sheets. This is also the case with comments, for example you can embed https://commentbox.io/ into your Typedream site to enable comments.
Hope this makes sense!
Thanks for pointing out about Pinegrow as well, this is my first time hearing about it! We focus more towards non-pro users and trying to make the UX as familiar and simple as possible. Seems like Pinegrow is somewhat similar to Webflow and the pricing is more "per user" than per site.
Is there any specific reason why you would like build lots of sites? We did encounter some requests on enabling code export and make a software package pricing so users can host the exported sites themselves, would love to understand your use case!
Have you had any solution that allows you to do this with other website builders?
And yes the context menu is covered when it's near the top , a bug we need to fix.
About the color, I am not sure whether you want the ugly color or you don't lol, but you seem to have figured it out :D
Thanks for the feedback!
I'm not sure if you're saying you want to add html/css or you don't, but just letting you know that we do have a Code Injection feature to add code to the <head> and <body>.
We use React because our editor is built in React (which does have a lot of interactivity and changing states), and so, since it's a WYSIWYG editor, the user will be seeing how their site is rendered as they are editing it, so we render their site in React as well. Also, we are using this React framework, Next.JS, which have a functionality to generate static pages from our React component. At the end of the day the React does get compiled into static pages in HTML/JS/CSS. I'm not sure if this answers your question though, would be happy to answer more questions
The JSON format allows us to only specify the main type/value of each block, while giving full flexibility on how to render them. I think there are several approaches to rich text editing out there, we picked this one because it seemed to be the most flexible and portable, as we need to invent our own types of standard "blocks", like columns, containers, etc.
Not sure if this answers your question though, happy to go deeper if you have more thoughts on it.
We want to take a different UX approach to most of the features necessary for website building, to make sure beginners can make a functional website with almost no learning curve. Of course, that's a huge challenge :D.
And yes, we do plan on building the frequently-used integrations as native features. Our plan for the near future is to build a native CMS, forms, gated content like Memberstack, some simple animation, and email newsletter. We're sort of taking inspiration from Ghost & Notion on UX, and SquareSpace/Webflow/etc for features.
However, we probably are not competing directly with Webflow, as our target users are quite different. Webflow seems to target designers that require complete control over every pixel. While for us, we focus more on builders/founders that want to get something out fast while keeping sites looking pretty & modern by providing design defaults.
I see, I personally haven't played around with PWA much, but that sounds like something we should look into, thank you!
It doesn't support PWA yet. Do you have input on this?
And yes presenting on nextjsconf would have been really cool!!
And yes, it's the editor itself that is our biggest selling point, and we did have users who preferred to use the editor as a software, and then export the code and host them anywhere. Would love to get your thoughts on this approach! What kind of pricing model would work for you if we offer this as a software package?
We can setup a call in the chat/email if you'd like. Thank you!
(Trusted device would work with browsers in the future when WebAuthn is more widely adopted. https://webauthn.io/)