gregaitch

Just checking in to see if anyone might have a solution to removing the padding when the image is CSSd as a Block ID, but fits correctly (snugly) when referred to as a property selector. Thx!

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); }

Hi @tuanphan, thx for checking. Yes pls, snug-fitting is the target. It snug-fits when I CSS a property selector for the entire site, but adds padding when I CSS block-ID (same CSS).

Thanks for taking a look, @tuanphan I've disabled autoscroll for a gallery block in a new page (link below, need to keep the above example scrolling as it's live). I also tried adding your code above as CSS; it disabled the border and border-radius (your new CSS now removed). If you also have a solution to my CSSd gallery 20px right-margin between images offsetting them cumulatively an additional 20px from the left edge of the block (so last image gets right-cropped significantly), I'd appreciate it. https://matter.media/gallery-test

Image insets from border when applying CSS to image with block ID with below CSS, but fits snugly when the same CSS is applied to the property selector .image-block-wrapper. See two uploaded images below for comparison. I only want to apply to select images, not universally. If I can resolve, I'll add more feature image block-IDs to the entry. Thank you! #block-dd9a8d05f998d8510303 { border: 1px solid hsla(45, 5%, 90%, 1.0); border-radius: 20px; box-shadow: 0px 0px 20px 5px hsla(45, 5%, 45%, 0.2); } Relevant web page CSS to Block ID insets image: CSS to property selector .image-block-wrapper fits image snugly:

Included a reference URL, but not seeing it post, so: https://matter.media/impact/isle-website Other eg's: https://matter.media/impact/

Currently using this code to gain space between gallery block carousel images, which works … .thumb-image.sqs-gallery-design-strip-slide.loaded { margin-right: 20px !important; } … but after the first image, cumulatively left-offsets each successive image another 20px from the block's left edge (ie fourth image is offset 60px from left edge of block). Standard behaviour is each image slides in to be hard left-aligned with block's left edge. Result of using margin-right is, if there's a lot of images, the later images offset so much they straddle the left and right block edges, with no clear focused image. Also the bottom row of pixels is cropped out. For CSS, pls quote sitewide properties rather than block-ID, thx!

If recommending a CSS solution, please include site-wide selector rather than block-ID, TY!

Hey SqaureSpacers, gallery block carousels are cropping the bottom row or two of pixels of images throughout my site Scroll down on the reference page (and other blog "/impact/" pages) to see examples, or look carefully at the bottom edge of the image uploaded to this post where the 1px grey border disappears (pls ignore the left edge; they're fine) Was evident before I applied CSS border and border-radius, although they make it more obvious Thanks for any help!

SS Permissions are far too basic and have exactly the implications mentioned above. The only way to provide clients/contributors a practical level of permission (eg publish new pages) is to bestow Administrator permission, complete with billing privileges. It compromises either the service we offer, or forces us to introduce unnecessary business risk. https://forum.squarespace.com/topic/224934-only-an-administrator-can-publish-new-pages-are-sqsp-permission-levels-too-basic/#comment-568477

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.

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).

I also need to increase section grid column count. Blocks snap to the grid, and at 24 columns, the grid is too chunky for fine positioning. The set number of columns also restricts equal distribution of peer elements across the page. Can we adjust the section column count? If not, is it an implementation by Squarespace, or limitation of the underlying CSS grid technology?

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

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

@Badge20, could you share an example of that?

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.

Thanks @tuanphan

Putting together a website – still in trial – with a member area. Previewing the site via its Squarespace development URL and clicking the link to the membership area takes my client to to a Join/Sign in page. Clicking either of those pops up a box: MEMBERSHIPS IS CLOSED Memberships for this site is closed. Contact the site owner for access. DISMISS Is there any way for the client to preview the membership pages via the development URL?

Thanks @marcel.weisheit And for headings? Replacing p strong with h strong didn't seem to work