Hi @richardpoelderl ! That's exactly right! It's BYOC and we've also got some components that are built-in by default so that you don't need a development team to get started. As far as loading custom fonts in the builder, it's something that's in our roadmap. There's two workarounds for now: - You can use our Snippets feature to add custom fonts - You can use a custom host and add fonts like you would in any Next.js app With regards to marketing wanting to customize the appearance of a component: Yes, the component ultimately exposes a props interface that allows it to be customized. This gives the developer full control of what should and shouldn't be customizable. We make it very easy with our controls (e.g., `Style` https://www.makeswift.com/docs/c...) for a developer to decide what can be overwritten. That being said, we provide all the basic building blocks needed to build a site: Box, Text, Image, Button, and more. So a marketer really only needs the developer to expose functionality when it's a custom component (i.e., a form that talks to an internal API). We're also working on a `Slot` control which will allow developers to leverage component composition so that marketers can drop any component inside the component the developer built. This results in a combinatoric explosion in variety. For example, a developer could build an animated carousel component and have each slide use a `Slot` so the marketer has full control over what goes in each slide and can use any other component available to them—including the default built-in components! If the developer wants to, they can even expose different animation options, or they could opt not to.

@ollermi Yeah Slots with BYOC is a game changer. Imagine if that worked with radix (which use the composable components pattern), how well you could provide components without having to depend on whatever the builder supports for the provided components. 😍 Does Style also expose atomic css via tailwind for example? I could see how marketers learn tailwind instead and thereby having full control over the appearance. If something breaks, devs can restrict class usage of tailwind if preferred. Oh and by the way: kudos to your pricing model. Having the custom domain on the free tier is really nice. In fact, I think your pricing model is so nice I was surprised not to see a screenshot in the carousel here on ProductHunt.

@richardpoelderl 100% You can use Radix today with Makeswift! At the end of the day it's all just React components all the way down. We're working on making `Style` use atomic CSS for performance reasons but we're also exploring integrations with libraries like Tailwind so that if you have a Tailwind config you can easily expose that to your marketing team. Think colors, shadows, typographies and other Tailwind design tokens available in the Makeswift `Color` control, `Text` control, etc. And thanks on the kudos on pricing! We've iterated on it so so much and we're very happy with where we're at. We think it aligns well with what the developer community expects while still being inclusive of no-code users that want to start with a small site and grow with us!

@ollermi Quite exciting. I’m curious if you’ll implement the tailwind integration. Would love to see that but understand that it hasn’t been implemented just yet in the Style api.

@richardpoelderl The `Style` API is intended to provide a class (or multiple classes). What we'll probably do is allow the developer to define a list of classes, which can be Tailwind classes, to also include in the prop controlled by `Style`. That being said, you can Integrate Tailwind with Makeswift today by using the `Select` control: https://www.makeswift.com/docs/c.... In the code you can map values from `Select` to Tailwind classes. For example, a value of `'primary'` could map to `'text-sky-500 text-bold ...'`. This can get tedious, though, so we're looking to work with our community of developers to better understand how they would want to expose their Tailwind config visually to their non-technical peers. If you have any ideas we'd love to hear them! We've go our open-source package at https://github.com/makeswift/mak... and also have a Discord community at https://discord.gg/hwm33EJa

@rauchg @appledger Alan, this looks pretty awesome. 🚀

Thanks @mrahmadawais ! Happy to answer any questions and would love to hear feedback. We're working hard on making the UX and DX better and better every day 😄

@ollermi @fadi_francis1 Thanks Fadi! It's been such a treat working with you and the Recurrency team.

@amelia_charlie thanks so much!

@tikhon_bernstam thanks, Tikhon! Great to have your support.

@tikhon_bernstam really appreciate it!

Thanks, @michael_sengbusch1! You're an OG and we appreciate your continued support!

@withfulgid thank you! Let us know if you have any feedback 😊

@brandonesc thanks, Brandon! Appreciate your support.

@uibreakfast Thanks! It was great chatting with you today!

@uibreakfast Thanks, Jane!

@merket 🙏

Thanks, @karimsaif!

@jpknegtel thanks, Jonathan!

Thanks, @philiplakin!

@myared Excited to continue to work with you and the team at Echobind!