gregaitch

Hey @tuanphan, that worked! Brilliant, thanks very much.
Also solved a related thread of mine on the bottom rows of pixels getting cropped (link below) Thanks again!
Only tweak, which would be great, is if I can register the 0.95 size from the image's left. Currently reduces registered to image's centre, which leaves a gap on the left between the image left edge and block's left edge.
 

Hey @tuanphan
Update: just checked your helpful response (code snip below) to a related thread I started (link below), which solved *this* one as well. Brilliant, thank you!
.thumb-image.sqs-gallery-design-strip-slide.loaded { transform: scale(0.95); }  

Thanks @paul2009. Settled for dragging the pages out of the Member area into Unlinked pages, and explaining they'd be behind a Sign-in page. Trial site is password-protected anyhoo.
On this, wondering if Squarespace Member area supports non-password access, ie provide email address and tick declaration box, once. Content doesn't rate that much security and audience won't appreciate the extra password.

Squarespace has too big a gap between contributor/managers and admin. ie Contributors can't add new pages (for example); they need full admin access, which includes billing privileges. Which is bad. Essentially, if I'm to give a client the ability to add their own content pages, I need to hand over ownership so my credit card is not wearing their purchasing decisions.
This suggests a cynical approach by Squarespace to increase purchases or leapfrog the reseller for a direct relationship with the end client.
This exposure – and lack of clarity on costs incurred and time to recoup from the end client – is the biggest impediment to us developing Squarespace websites for clients.
It makes Squarespace not fit for its core purpose: reselling a product (the website).

Squarespace has too big a gap between Website Editor and Administrator. ie Editors can't publish new pages (for example); Only Administrators – who have billing privileges – can publish new pages. Which is bad.
Essentially, if I'm to give a client the ability to publish their own content pages, I need to hand over site ownership so my credit card is not wearing their purchasing decisions. There is lack of clarity on costs so incurred, meaning too much time to recoup from the end client. Plus a need to anticipate these transactions and define terms in the contract.
The easiest win (ie a minimum), would be to de-couple Billing privileges from Administrator, so you could attribute Administrator, without Billing. Currently, selecting Administrator mandates Billing, even thought they're seperate privilege line items. But, ideally, either including the ability for Website Editor to publish new pages, or a new Website Manager role, is necessary.
This suggests a cynical approach by Squarespace to either increase purchases by the client ("Hey, I'm not incentivised to check if selecting this feature incurs costs; the reseller will let me know … probably"), or leapfrog the reseller for a direct relationship with the end client.
This exposure, or pressure to handover the account to Squarespace,  is the biggest impediment to us developing Squarespace websites for clients.
It makes Squarespace not fit for the purpose of reselling the platform while retaining the hard-won relationship with the client.

So far, it’s a combo of Elfsight event calendar plug displaying events on page, linking to corresponding events on Tickettailor for registration

Squarespace has too big a gap between contributor/managers and admin. ie Contributors can't add new pages (for example); they need full admin access, which includes billing privileges. Which is bad. Essentially, if I'm to give a client the ability to add their own content pages, I need to hand over ownership so my credit card is not wearing their purchasing decisions.
This suggests a cynical approach by Squarespace to increase purchases or leapfrog the reseller for a direct relationship with the end client.
This exposure – and lack of clarity on costs incurred and time to recoup from the end client – is the biggest impediment to us developing Squarespace websites for clients.
It makes Squarespace not fit for its core purpose: reselling a product (the website).

CSS grid like any technique will have limitations at some point. I'm not aware of any official stated limitation. The limitations you are likely to run into is how various browsers handle rendering the grid. Making calculations and such takes memory, taxes the performance capabilities of the browser, computer, and even the network. The other thing to consider is not everyone has the latest and greatest of all these pieces of the pie.
So with that in mind SS may have done some testing to find a balance between too many columns and too few. Or they could have done something simple like hey 12 columns in the classic editor isn't enough fine grain control and went to 24.

I didn't get any further than the pricing, which starts at USD99/mth if you want the platform branding removed

I checked out your app and it looks fantastic. But even your cheapest plan is quite expensive... more expensive than Squarespace's Business Plan. So the calendar would cost my clients more than their whole website. I work with small businesses and nonprofits (such as churches and schools) who are not making money off their events. I want to suggest that your app develop a "non-ticketing" plan that is actually affordable for those who are not selling tickets... comparable to Loxi.io which is $8/month. Thanks for sharing!

Unfortunately this is one of the two very frustrating limitations of the Member Areas product. It makes it so difficult to agree the workflow with clients because they cannot preview the onboarding process or setup a member area account/subscription until they've committed to purchase Member Areas.
However if you make your client a contributor, they will be able to view the member area page content, even though they cannot test the onboarding or the Member Areas account features.

h1 strong
or h2 strong
or h3 strong
or h4 strong
or h5 strong
or h6 strong
or
h1
or
h2
or
h3
or
h4
or
h5
or
h6

.summary-metadata-item {opacity: 1 !important;}  

Add the following to Design > Custom CSS.
/* hide quotes for quote blocks */ .sqs-block-quote span:first-child {   display : none;      } .sqs-block-quote span:last-child {   display : none;      } This is for a v7.0 site using the Brine template family.
Let us know how it goes.