[104] How to Choose the Right Squarespace Features Before You Design

Start With Function, Then Make It Look Good

Let’s say someone hires you to build a staff directory in Squarespace. They have 50 employees, multiple locations, different departments, headshots, bios, contact information, and they want visitors to be able to filter through all of it.

Your first instinct might be to picture the finished page. Maybe it’s a beautiful grid with headshots, names underneath, and some slick hover effect. But that’s not where I’d start.

I’d start with the information.

What needs to be stored? How does it need to be organized? Where else might it appear on the website? And six months from now, can the client add a new employee without calling me? Once I know those answers, I can start looking at the features already built into Squarespace and decide what makes the most sense underneath the design.

For that staff directory, I’d probably use a blog. Not because we’re publishing articles, but because blogs already give us titles, thumbnails, excerpts, categories, tags, links, summary blocks, and archive blocks. Suddenly, I have most of the functionality I need before I’ve written a single line of custom code. Then I can use design, CSS, and occasionally a little JavaScript to make it look nothing like a blog.

That shift in thinking has become a huge part of how I build Squarespace websites. Instead of deciding exactly how something should look and then forcing Squarespace or AI to recreate it, I start by asking what it needs to do. In this episode of Think Inside the Square, I’m sharing how I make those decisions, a much stranger portfolio workaround from a real project, where AI-assisted coding fits into the process, and why knowing when not to get clever might be one of the most valuable skills you can develop as a Squarespace designer.

Next
Next

[103] How to Talk to Squarespace Clients About Using AI