Content and the people who edit it
WordPress starts with posts and pages. Case studies, people or resources each become a custom post type, and WordPress’s advice is to define them in a plugin, so switching theme doesn’t lose them. A developer does that setup.
Squarespace offers no equivalent. A collection is one of a set list: blog posts, products, events, portfolio projects, and on 7.1 course lessons and videos. We searched Squarespace’s help centre for custom fields on 7.1 collections and found none. Inside that list there is plenty of room for a small site, with 1,000 pages allowed, no cap on blog posts and 350 events a month.
WordPress has six built-in roles. A user with the Contributor role can draft posts, and publishing them falls to someone with a higher role. WordPress stores a revision each time a draft or update is saved, and any two can be compared. Posts can be scheduled.
Squarespace gives each contributor a free account and a role. The Website editor role lets someone put content into pages that already exist, without adding new pages or touching styles. Posts on a blog can be scheduled. Review before publishing is harder to arrange. Page drafts are reserved for Squarespace’s top tiers of customer, and the Draft editor, who can’t publish, is an Enterprise role. Squarespace keeps no revision history, so leaving the editor makes a change final. A deleted page or post can be restored for 30 days.
For a second language, Squarespace 7.1 has Weglot built in, free for one extra language up to 2,000 words. WordPress core can’t run a second language out of the box, so that means a plugin or a multisite network.