Hello, I used Figma site a lo recently and here are some feedback :

• The requirement to use a subdomain is quite restrictive. For example, if I'm forced to deploy my site on www.domain.com, I also need to redirect domain.com to www.domain.com to avoid users being blocked or unable to find the site when simply typing domain.com. This redirection then has to be set up manually on the server side, whether through a .htaccess file or an Nginx or Apache configuration. I have the technical skills to do this — it's my job — so it didn’t take me long. But it's far from accessible for someone who isn't a developer. In my case, the simplest solution would have been to host the site directly on domain.com.
• Dynamic components (e.g : carousel) which have breakpoint variants do not adapt responsively to the screen size. This cause major interface problems. The problem is not observed for static components.
• Buttons do not have focus states (interactions) which is highly problematic ATM for designing website with good button behaviors.
• Text styles can’t be define (even when I try using the right naming) → big problem for SEO
• To many div blocks (that do not exist in the design) are added by Figma site when inspecting the code once the website is published.
• Many animations require workarounds to work ( e.g : marquee lack a padding parameter to get a consistant space between each loops)
• When a component is given several states, this creates a conflict, Figma can’t sequence the right way the transitions from one state to the others. (e.g : a button component has a “While pressing” state changing his background color → this button is inserted within a larger component like a carousel and an “on click” interaction is added to it in order to animate the carousel. Figma won’t be able to make both interactions work and will solely prioritize the seed one (while pressing)).