I haven’t used this yet but I just wanted to share feedback that the screenshots in the “Explore Figma Sites” article feature large blocks of neon yellow, which is harsh on the eyes and is likely to be particularly unpleasant or painful for users with visual or sensory sensitivities. It makes it difficult and uncomfortable for me to read the article and learn about this new feature. It would be better to use more subdued colors. 

This is the second thing I’ve looked at related to this year’s ConFig launches, and the second thing that has failed basic accessibility standards and principles (see my other post about the announcement modal being inaccessible). 

I’m also really glad to see people in this thread raising accessibility concerns, though I’m dismayed that they need to. I agree with ​@Emily Lawes: 

Figma, at your scale, I would implore you to get this right and not ship products that will perpetuate continued creation of inaccessible digital products. 

Please do better. You have a responsibility not just to your users, but to their users, too. You are actively contributing to making the web less accessible and that is not okay. 

Hi Figma team and community!

With the launch of Figma Sites, I’m curious if there are any plans on the roadmap to support local fonts in addition to Google Fonts. Our team relies on brand-specific typefaces that aren't available via Google Fonts, so having the ability to upload local files—or even reference fonts through a GitHub repo or similar method—would be a game-changer.

Happy to provide more details if helpful. Thanks for all the amazing work you're doing!

In reading the responses here the more common theme seems to be regarding font and typography support.

I posted a question regarding the roadmap to support custom fonts that align with our brands here:

This would be extremely helpful for portfolios. Having the option to password protect a whole site or just some projects would be extremely helpful!

You already let me upload a video file – it's on your servers, it plays in the fill layer preview, but it won't play on the live site. Why? Never mind, I don’t even need an answer. I’ll just wait a year until you announce it as a new big feature.

I can upload video in Figma Design. Copy direct link to S3 file in DevMode. Embed it with iframe in Figma sites. What are you trying to avoid here?

Are they only available for publishing on the Figma service? I mean, the tool can't export code, so I can deploy it myself on my own project or server?

The Embed element in blocks has hidden height parameters, so it’s impossible to configure the section to adapt to the height of the embedded content, such as an iFrame. A more complex example is an iFrame that changes its height using a script inserted via settings. The script works perfectly, but the height still depends on hidden, uncontrolled wrapper DIVs.

This makes it impossible to properly build layouts — there’s no control due to these hidden height settings, like a default min-height: 1px, or in the case of “Hug” sizing, one of the wrapper divs still has an absolute height like height: XXXpx.

Is it possible to remove these unnecessary parameters for Embed Blocks, or at least make them configurable, to work in a more logical and predictable way?

PS. Thanks for Sites – this amazing!

This is related more towards the CMS end of Sites. Is there the possibility of letting that CMS tie into other products like Buzz? 

The team I’m a part of uses Figma for everything from display ads, social ads, social tiles, email designs, etc.Often in a campaign format. So while the xlsx is great for bulk create it’d be great to be able to set up content natively in Figma and tie that to other assets. 

Really glad to see something like Figma Sites, but I’m baffled that I’m forced to publish into figma and can’t export / use the code myself elsewhere. Is this a planned feature?

Of course it’s a planned feature. This is isn’t meant to be a tool that is maximally useful, like everything else software does these days, it’s designed to keep you in the ecosystem.

I have had an issue while playing with Sites where the entire page broke and I lost all of my content. I can no longer create or see desktop/mobile breakpoints, and this is the error I get when I try to preview.

This is the greatest advancement for Figma ever! Awesome work team!

However, two things so far break functionality for our companies sites. 

• Not supporting any local fonts - this is a must have for custom brands etc.
• Not having a still of a video embed IN the editor. (We use a lot of simple vids per page that auto play and loop) 

Otherwise, this would completely take over! 

I feel like when every time Figma has introduced the new feature, they don’t really think throughly or specifically touch how the current system can work with it seamless and benefit from the new features, which is a major problem. There’re certainly some issues might happen as they can’t transition well from here to there. I’ve been tested out with our own current section components. As they all work fine on the Figma design file, but has some problems when it’s on the Figma Site. Here’re some issues I’ve encountered when I did the testing with our current component.

• On Prototype, the icon can’t be displayed normally. ( It works fine on Figma design’s prototype )

• Breakpoint wise, I’m sure every website has their own grid/responsiveness setting, which in our case let’s say 1000px above is laptop/desktop, 999px-561px is tablet, and 560px below is mobile. However, I find those breakpoint feature is difficult to be used as 1280px is always be there as sorta default setting, which causing some problem shifting resolution on prototype.
   

  

• The layout break issue. Apparently they seem looking fine on design frame but broken on prototype. 
  After few tries, I’ve found that changing the auto-layout alignment to ‘align top’ can fix the problem. I guess it’s another bug as well.

  

  
   
• It has some issues with variable I suppose? I’ve created the variables for the title set up with three different font-size (laptop, tablet, and mobile). As the title looks fine on the design frame, but it doesn’t apply properly when viewing on prototype as you can see. 
  
  Same as the quotation marks on the testimonial card component, I’ve created the multicolor with variables(orange as default, blue, green, pink) and applied onto the center component. That card component’s variable has been selected to blue, with its own hover effect which just simply changing its shadow to be stronger. However, on the prototype I hover the component, its quotation change back to the default orange color which shouldn’t happen..
  
  Therefore, I assume Figma site’s prototype has some bug issue with variables.
  (Note: None of those happen on Figma design’s prototype) 

  

   

• It certainly a great idea to have ‘primary’ frame, so when you select the elements from it, all the corresponding elements will be selected across frames. However, it comes with one of the problem as inner layer within the instances can’t be shown if there’re multiple things being selected at the same time. Thus, there’s no way I can do things from my instance’s inner layer from the primary one.
   

  

  

  
  
  I believe there’re more issues which I just not encounter yet. Hopefully Figma could fix up these points asap, and let know how this Figma site could work seamlessly with the current built elements.

How can I make an interaction to switch between (light/dark) modes?

hello. I am an engineer developing a design system at a company called Karrot (daangn.com) in Korea. I went to SF this time and saw Config, and I have high expectations for the new features.

For accessibility, I will move on because many people have already raised issues above, and Figma needs to upgrade the Interaction tab.

1. Motion Variables

It's great to be able to set custom beziers and custom springs, but we need the ability to manage these custom values at the team level.

It would be nice to be able to create and apply Variables to values like Duration, Bezier, etc.

I've been thinking about this before, but with Figma Sites, I feel like it's even more important.

2. Need the ability to manage Custom Bezier, Custom Spring

It's nice to be able to apply custom transitions for each element.

But that's about it. It doesn't seem to be possible to copy or clone custom transitions yet. I would like to be able to create custom transitions like Smooth Reveal and Expressive Reveal and share them as a team.

I'm very excited about the CMS, Figma Make, and other features that have yet to be released.

Thank you.

Recently while I was about to publish my website, I saw that one of the errors suggested that I must remove auto scroll to particular section within a webpage because it is not supported in Figma Sites. This feature is a must because usually users want to create one pager website.

figma sites are made frankly poorly, as is the figma forum, which apparently no one reads.

the division of files into specific sites and specific designs is unclear why it was invented at all, synchronization between layouts in different files is unclear how it works, and if there is no synchronization, what's the point of your layouts in figma sites files? Why do you always make a lame horse?

you turn on figma sites, wait six months for a cms update, turn on the cms update, wait six months for a figma make update. What is the point of such updates? to create a design in the current update, knowing that in six months this site will need to be changed to another, because the interaction structure will have already changed? and projects are not done quickly, complex projects take a lot of time, not in order to spend the same amount of time changing the structure in six months.

the projects that you presented last year are still in beta. You have an extremely strange and, in my opinion, completely opaque approach to your updates. The layout has been broken since last year, and you don't fix anything.

A lot of services doesn't mean a lot of good services. Try to do one thing well, so that updates come out on the day of the announcement, and not broken after half a year

I have finally had the opportunity to experiment with the Figma Sites. I am particularly interested in some of its features, such as:

1.  Loading a custom template to initiate a project
2.  Implementing breakpoints for specific responsive behaviors

However, my ultimate objective is not to directly create public websites, but rather to generate mockups that can be seamlessly integrated into our framework. Is there any possibility that I will be able to access features like a template library or genuine breakpoints within the default Figma interface?

I’ll agree with others who have wondered WHY embeds seem to have internal padding? If I use the same code to embed a video on Webflow or Framer it’s perfect - fits my layouts exactly as you’d expect. But in Sites it places the video with padding, making the video smaller than other images etc., completely throwing off the design intent. 

How it should line up:

Yet smaller when published:

Also, like Framer and Webflow, we very much need a preview of our embed in the editor. Impossible to design correctly without it. 

When you set the scroll behaviour of a frame to overflow: horizontal, or overflow: vertical, this only works when ‘clip content’ is switched on. I think this is how the overflow property works in CSS, but it might help to have a warning

I’ve run into 2 issues so far.

1. Overlay interactions copied over from ‘design’ don’t seem to work properly. ‘Sites’ sees the interaction, but it doesn’t actually work. In my example, clicking a button to open and overlay a frame.

   

    

2. A common font I am using ‘Montserrat’ doesn’t show properly when previewed.

I’m super excited about Figma sites and plan to use it extensively. I’ve been doing some testing and have found a few issues I hope that are fixed. The new effects of noise and texture don’t seem to work when previewed and blend modes don’t always work for some reason. Excited for the full release.

Just a suggestion: You may consider adding REAL value to your CORE product (e.g. better prototyping), instead of a range of half-bakes solutions for hobbyists that will never come to full fruition. You are becoming Adobe...

Hi, 

Figma sites sounds like a framer killer, but it’s pretty useless until we get viewport and % sizing.

Keep up the good work guys.