Squarespace development for a site you can still edit

Inside a Squarespace job

New sites are version 7.1 in Fluid Engine: pages, menu, site styles, forms, a blog if you publish, and a small shop when Squarespace commerce fits.

Repairs are usually one fault. A header covers the first line on a phone, a form never sends its email, a code block shows raw script, or a slug 404s. We read the version, the plan, and the injection fields before proposing a rebuild.

Developer mode applies to supported Squarespace 7.0 sites and exposes a copy of the template code for customisation. Disabling it can remove developer changes, so we inspect and back up the existing custom work before changing that setting. Squarespace 7.1 has a different editing model and does not offer that developer mode.

Setup, CSS, and leaving

Setup covers the domain, an owner login, contributors, titles, descriptions, form delivery, and URL mappings. Placeholder pages stay off the live domain.

We use native blocks and site styles where they cover the design, then scope custom CSS for remaining layout gaps. Existing styles are saved before editing. Review includes phone breakpoints and the pages affected by a shared rule, with clear ownership of publication.

Code injection can connect analytics, chat and verification services where the current plan and page support it. We check those permissions before quoting custom scripts, and keep the script list short. Checkout has platform restrictions of its own; we confirm the specific extension point rather than treating every page as an unrestricted code area.

A Squarespace to WordPress move rebuilds from a partial export. XML includes layout pages, text and image blocks, and one blog, up to 1000 comments a post. It omits CSS, styles, drafts, a second blog, and store, portfolio, index, video, audio, and product blocks. Products leave as a CSV of up to 10,000 rows. Redirects go on WordPress, because Squarespace mappings end when the domain moves. A [name] rule covers a prefix change, /p/ on 7.1 included. Gaps are listed before a date depends on them.

From the email to handoff

Send the URL, 7.0 or 7.1 if you know it, the problem or the launch, and a date with a real cause.

Repeatable bugs are hourly. New sites, wide CSS, and migrations are fixed quotes once scoped. If the brief only says the site feels stale, paid discovery comes first, and you keep the outline.

Your business keeps the Squarespace owner login, billing and domain registration. Invite us with permissions suited to the agreed change. We decide how to preview the work before publishing and keep a record of existing CSS and scripts. Handoff identifies the blocks, code-injection fields and URL mappings involved, plus the changes your staff can make without custom code.

Where the platform stops

No PHP, no SQL, no server-side code, and no theme you can take away. A reshaped checkout, a signed-in product, or a promotion the commerce screen cannot do belongs on Shopify, WooCommerce, or Next.js, React, and TypeScript.

Shrinking images, dropping an extra chat widget, or fixing a header script are in scope. Squarespace's own JavaScript is not. We set labels, contrast, alt text, and heading order, and we do not certify compliance. Squarespace help that is only visual still starts from the version and the plan. That reading is what a Squarespace expert is for, and what a Squarespace developer does on one piece.

Who it suits

It suits owners who will edit, agencies that need one slice, and teams that already have a developer. Agree who saves the CSS panel. There is one field, and the later save wins.

If the brief is still open, paid discovery can turn it into a defined feature list and acceptance checks. If you already have a developer or agency, we can take a bounded part of the work and agree how it joins the wider project. Share the target date so we can assess capacity and dependencies before committing.

hehe.software works from Vancouver, British Columbia. Clients elsewhere in Canada, and throughout the United States, are remote.

Proof, and a faster quote

Our website is hand-built, and our nine App Store apps are products we own. They demonstrate design and implementation in those contexts. For Squarespace, the work you review is a preview of the agreed pages or repair, followed by notes on blocks, CSS and injected scripts. Handoff should leave your staff able to make the routine changes the site needs.

Send the plan, the version, logo and type files, the page list, and who approves copy. A shop adds a product CSV. A move adds the URLs that must survive and which one blog the XML keeps. Access can wait until we agree to look.