Pixeltender

The CSS seems to be missing from the stylesheet.
Try adding this in your Custom CSS, change the hex to the colour you need. Save and refresh.
blockquote { border-left: 5px solid #B564F7; padding: 1px 10px 1px 20px; }  
@fufu15 If this doesn't help, then the issue is likely different and specific to your site, you'll need to share url.

Thank you so much! That sure wasn't the answer I was hoping for, but the heads up about setting up the URLs properly was much appreciated.

This is my response for moving from 7.0 to 7.1 but can be done when moving to a new site as well. There isn't a way to automatically transfer Acuity from one site to another.
 

As far as I know, you can’t transfer the acuity account to the 7.1 account. If somebody sees this and knows how to do it, please add the info.
What I did when I moved over to 7.1 was when the site was done I went ahead and clicked on the Scheduling tab on the new site which will start a new trial. I copied everything over and then I went in and changed the scheduling, link custom URLs on the old account to something random , and changed the random ones on the new account to what I needed them to be with the custom URLs. 

It's important that you have the right URLs on the active Scheduling account before you delete the old site if you're going to. I did not do that, and it was a headache to fix.

Very happy to hear Squarespace might finally address this, but the links in your post are giving me permissions errors, and I can't figure out how to find the "Vote on Feature Requests" section of Squarespace anywhere. 
How did you find that originally?

Add to Home > design > Custom CSS
.header-actions-action .btn { padding: 20px 30px; font-size: 15px; color: red !important; background: green !important; border-color: violet !important; }  

A friend with a Squarespace site wants to refresh their site with a new theme/template but couldn't figure out how to do that. I volunteered to investigate the issue for them, which led me here. I'm flabbergasted to find that it's really not possible and the only way to refresh the design of a site is to cancel the whole account and start a new one. Even if you wanted to go to the trouble of manually changing all the things, it appears there's no option to do it in a staging area and push it live once it's ready. You'd have to either do it live where everyone will see it as you're working on it or shut your whole site completely down until you're finished. Unbelievable. I can only assume that this is some kind of cost-savings measure on the part of Squarespace, possibly to minimize man-hours spent by their team, because, from a UX perspective, it sure seems exceptionally bone-headed. 

And, while I'm ranting, what's going on with the versioning system? They push the biggest change to the system in years but instead of incrementing the major version number they increment the minor version? Going from 7.0 to 7.1 implies a feature update, maybe some bug fixes, and that backwards-compatibility has been maintained. A massive change like this which is incompatible with the old system should require a major version change; this should be 8.0, not 7.1. Some really perplexing decisions from Squarespace here.

Thanks for following up! I still get a permissions error, but I've worked out that you must have to be a Circle Member to view and vote on this... so then I learned what Circle Members are and signed up to be one!
All in the name of .webp! (and .svg!)
For anyone else unfamiliar, you can sign up here https://www.squarespace.com/circle
The requirement is that you've built or contributed to at least 3 Squarespace sites.

Thanks for following up! I still get a permissions error, but I've worked out that you must have to be a Circle Member to view and vote on this... so then I learned what Circle Members are and signed up to be one!
All in the name of .webp! (and .svg!)
For anyone else unfamiliar, you can sign up here https://www.squarespace.com/circle
The requirement is that you've built or contributed to at least 3 Squarespace sites.

It can be done with custom css
@media screen and (max-width: 767px) { .header-title-logo img { max-height: 250px; } }

On Squarespace, headings use h1 to h4 tags, but there aren't p1 to p3 tags for paragraphs. Instead, all paragraphs use a standard p tag that can be combined with classnames, as explained below:
 
Paragraph 2
Standard paragraphs (described as Paragraph 2 on the toolbar) use a <p> tag like this:
<p class="">Paragraph 2</p> To style them, you can use CSS to target the p tag like this example to set the color:
p { color:red; } This may target just the "Paragraph 2" style of paragraph or all paragraphs, depending on the other CSS being used.
 
Paragraph 1
Larger paragraphs (described as Paragraph 1) also use the <p> tag but they do so in combination with the sqsrte-large class, as shown below. The class name is an abbreviation of "Squarespace Rich Text Editor - Large".
<p class="sqsrte-large">Paragraph 1</p>  You can style them by using CSS to target the p tag and the sqsrte-large class like this example:
p.sqsrte-large { color:green; }  
 Paragraph 3
Finally, smaller paragraphs described as Paragraph 3 also use the <p> tag in combination with the sqsrte-small class, as shown below:
<p class="sqsrte-small">Paragraph 3</p> You can style them by targeting the p tag and the sqsrte-small class like this:
p.sqsrte-small { color:blue; } Was this post helpful? Please give feedback by clicking an icon below  ⬇️

@SaranyaDesigns In all my years I'd never learned about nth-of-type selectors. It worked perfectly (though I did have to add the !important property), thank you so much! 
https://www.jaclynandthejemstones.com/events-test

Thanks for the details @LMallon10 (sent by DM).
I've published a solution here: Make Squarespace list items clickable.
This takes the link that you've assigned to each CTA button and applies it to the entire list item. This means that users can click the image or any other aspect of an item to trigger the CTA action on your 'Simple' (not scrollable) List Section.
  If this post has helped you, please click a 'Like' or 'Thanks' icon below  ⬇️

You should be able to hide the buttons with CSS. For example, something like:
.list-item-content__button-wrapper {   display: none; }  

For anyone else who might be looking for an answer to this question, this tutorial worked for me. I believe this plugin would also get the job done.