English
jason's blogObservations on web standards, browsers, and frontend development

Category: Frontend Tooling

Figma Sites: can a design become a published website?

How Figma Sites connects design and publishing, using a small event page to explore its practical boundaries.

Published 05/07/2025

Figma Sites arrives, and another round of 'Will frontend developers lose their jobs?' practically writes itself. Publishing a design as a website sounds close to the button people have wanted for years: I drew it; make it real.

I do not find that especially objectionable. If an event page's content and layout are settled, rebuilding the same screen and revisiting all its spacing is work worth reducing. How far that convenience goes depends on what the website needs to do.

Announced in May 2025, Figma Sites brings responsive layouts, interactions, and website publishing into Figma. The result is a live page, not just a prototype link. Portfolios, event announcements, and product landing pages are easy uses to appreciate.

A talk page with speaker photos, a schedule, and an external registration link is already a complete, useful thing. It does not need a framework merely to justify its existence. Keeping content changes in the same tool is appealing too.

Even there, a good desktop design does not guarantee a readable phone layout. Cards, wrapping headings, and small buttons still need attention. Responsive tools and somebody actually reading the page on a phone are different kinds of help.

What remains for the frontend?#

For that event page, perhaps there really is no need to implement everything again. I think we can admit that without immediately defending the profession. Removing some work is a reasonable purpose for a tool.

Now require login, membership pricing, seat limits, payment, and refunds. The screen can look just as polished, but there are data and business rules behind it. Publishing the page does not finish those systems.

An existing Nuxt product introduces another question: does the page need shared authentication, navigation, and data? That is different from publishing an independent campaign page. Opening in the same browser is not enough to make two systems integrated.

What I would like to see is more of the small websites that previously felt like too much trouble to build. Moving a whole product can wait. Getting a portfolio online is already a perfectly worthwhile use.

Sources and further reading