← ClaudeAtlas

squarespace-portlisted

Port a designed static/custom site (Cloudflare Pages, a static build, a Figma-to-code export, etc.) INTO Squarespace 7.1 by pasting markup into Code Blocks and CSS into the Design / Custom CSS panel, and driving the admin via a browser. Use this WHENEVER the task involves editing a Squarespace 7.1 site's Custom CSS or Code Injection, pasting HTML/CSS into a Squarespace Code Block, making a Squarespace site match an existing design, or debugging why a Squarespace page "looks off," has invisible text, a white/blank hero, broken mobile, giant mobile headings, a stuck image carousel, an empty/oversized footer section, or unstyled pasted markup. Also use for Squarespace + WebGL/canvas heroes, native Form Block styling, and "make it match the Cloudflare/worker version." These platform behaviors are non-obvious and have burned real sessions — consult this before hand-editing, not after.
SipMyBeers/claude-squarespace-skill · ★ 1 · Web & Frontend · score 54
Install: claude install-skill SipMyBeers/claude-squarespace-skill
# Porting a designed site into Squarespace 7.1 Squarespace is not a blank canvas. It injects its own CSS, strips some of your code, wraps everything in fluid-engine grids, and its editor preview lies about mobile. Every item below cost real debugging time. Read the relevant section **before** editing, and verify by measuring, not by eyeballing. ## The two facts that reframe everything 1. **Custom CSS lives at `Design → Custom CSS`** — direct URL `https://<site>.squarespace.com/config/design/custom-css`. It is NOT under Settings, NOT "Website > Styles", and NOT at `/config/custom-css`. A capable agent looked in all those places, concluded there was no Custom CSS panel, and almost put global styles into a per-page Code Block instead. If you can't find it, you're looking in the wrong place — go to `/config/design/custom-css`. 2. **Squarespace strips `<style>` out of Code Blocks but keeps `<script>`.** So when you paste a page whose markup and CSS lived together (a `<style>` block + HTML in one Code Block), the HTML renders and any `<script>` runs, but the CSS silently vanishes — the page looks unstyled/broken. **All CSS must go in Design → Custom CSS.** Markup goes in Code Blocks; CSS goes in the global panel. Keep them separate. ## Where things go (the porting architecture) - **Global stylesheet** (your design system + every page's rules) → Design → Custom CSS. One big pane. This is the single source of truth for styling. - **Per-page body