Client sites, built as a team
Invite the people who build each site and give each the right role. Components keep every page consistent, and each page keeps 30 days of versions.
Work as a team, with a safety net.
-
Every version, kept
Each page keeps its versions for 30 days, so a bad afternoon is one restore away.
-
Tools your team already knows
The canvas works the way a design team expects, so nobody has to learn a new way of thinking.
7 design-tool habits that carry over
- Layers
- Components
- Auto layout
- Color Styles
- Hover states
- Smart guides
- Alt to measure
-
Access ends when the job does
Revoke a freelancer's access when the project wraps, and their seat on that site is free again.
One footer, on every page.
Turn the parts every page shares into components, so four people never end up with three different footers.
Components
Every component in the website, in its own tab beside Layers.
The instance
This footer is a copy of the master, the same on every page that uses it.
Go to master component
Jump to the master and edit it once to change every copy.
Detach instance
Make one copy independent when a page needs its own version.
Set up the studio in three steps.
-
Invite the team
Add the people who build each site from its Team tab, as Admins or Members.
-
Build the shared parts
Import the design from Figma, then turn the nav, the footer and the cards into components.
-
Split the work
Agree who edits which page, publish, and restore an earlier version if something slips.
Frequently asked.
Can two designers work on the same site at once?
Not in the same page at the same moment, because there is no real-time co-editing. Studios agree who holds each page before anyone opens it, a rule the team keeps rather than one the editor enforces.
Can we bring our designs over from Figma?
Yes. The Siter.io plugin imports Figma frames into a Siter page on every plan. The import runs one way, so settle the design in Figma first, then finish and publish it on the canvas.
How are seats counted?
Per website, for everyone with access to it, you included. Each paid plan includes some seats and you can add more (see the plans). Add people only to the sites they work on.
What can Admins do that Members cannot?
Members edit and publish pages. Admins can also invite and remove people, and transfer or delete the website. There is no view-only role, so anyone you add can edit.
What happens when someone leaves?
Make sure someone staying is an Admin, then revoke the leaver’s access, which frees their seat on that site. To move a site out of a personal account, transfer it by email to an account on a paid plan.
Should the studio’s own website live here?
A portfolio of project pages with a contact form fits well. There is no CMS, so writing published on a schedule is better kept elsewhere.
Who else it is for
- Portfolio builder A designer's portfolio on a free-form canvas, with case-study pages, a contact form and your own domain.
- Landing page builder Design a launch or waitlist page on a free-form canvas, collect sign-ups with forms, track campaigns, and publish it on your own domain.
- No-code builder Design on a free-form canvas and publish forms, hosting, your domain, analytics and SEO without writing code.
- For photographers Full-bleed galleries, a phone layout you place, and a licensing form.
- For artists A portfolio that looks like the work, with an inquiry form for sales.
- For nonprofits A site your team can edit, with a Donate button to your giving page.
- For designers The core case: your Figma file is already the site.
- For agencies Several client sites, roles for your team, and a clean handoff.
- For freelancers One designer, a few client sites, and a handoff when the work is done.
Put one site in front
of the whole studio.
Import a finished frame and see what the build takes before you commit a client project.