[johnny_utah]

I've been using Squarespace's developer platform for a gallery site. It's decent. I used the blank developer template, so I built most of the CSS from scratch. In my opinion, some of the drawbacks are:

- The editable text fields only support h1, h2, h3, and p tags. If you plan to have four font sizes or the people maintaining the site don't mind using the editable code blocks, this isn't a bad thing. - If you use the built-in blocks then write your own CSS overrides, you are assuming those classnames (generated on squarespace's side) will be the same. Forever. - I found myself overriding a lot of the system blocks with very bad css (some !importants)

The good things: - Every post has an associated JSON endpoint. No heavy lifting on this side. - In my experience, support gets back to you in a day or less with helpful answers. - The support for custom post types (See the docs) is finally acknowledged.

In my opinion, the developer tools are great for your own site or if the client has familiarity with basic html tags. I am not sure I would use it again for a site to hand off to a non-technical client. If the system blocks (built in video, text, image types) were customizable, I would recommend Squarespace more heartily.

I have not used Squarespace's ecommerce functionality so I am unqualified to comment on those. I have heard good things about Webflow's CMS offering, so I would check that out to compare.

This post was very helpful to me in seeing how other people use the dev platform (I have no affiliation): http://www.instrument.com/latest/creating-a-clean-custom-mai...

Hope that helps!

[jc_811]

Thanks for answering! Definitely very helpful