colin.irwin

No problem!

Why do you need them?

It's not possible.

I would advise against justifying web text. It's a big usability problem. It makes copy very difficult to read particularly, but not only, for dyslexic readers.

Do you mean you want it to be a different size on mobile? If so, adding the following to your custom css should help @media only screen and (max-width: 640px) { h4 { font-size: 88px; } } That should work - all you need to do is tweak the 88px to whatever value you want.

You'll need to set a breakpoint at whatever stage the layout breaks (looks like roughly 1400px wide) At that breakpoint you should target the collection id to restrict the rule to one page and then for the columns that are 4 wide to span 100% of the available width. @media only screen and (max-width:1400px) { #collection-5cda8559cb2c42000142030b section#le-conseil-1 .sqs-col-4 { width: 100% !important; } }

In the editor, scroll to the bottom of any page and edit Info Footer Content to remove the text.

Try this input.field-element::placeholder { color: red !important; }

Please post. a link to your site

Try turning off parallax scrolling in Site Styles if it is enabled.

A link to your site would make it easier to provide a solution.

Personally, I wouldn't use inline styles in a code block for precisely the reason that you have highlighted - it's difficult to make them responsive. However, you may be able to get things looking better with your inline styles if you use vw units rather than em. vw is relative to the viewport width. A better approach is to learn how to target a specific block for styling. This Chrome extension shows you block names that you can use in custom css. https://chrome.google.com/webstore/detail/squarespace-collectionblo/bggpdfnccodbnmcndckmeehdjkjojkde Enabling the extension in your Chrome address bar will overlay the collection ID and block ids on a page. To style a text block containing the example you gave earlier you would create a normal text block and insert 4 centered lines of text. #the-block-id { p { font-size: 2vw; // the first para } p + p { font-size: 2.5vw; // para followed by a para, so 2nd para } p + p + p { font-size: 3vw; // para followed by a para followed by a para, so 3nd para } p + p + p + p { font-size: 3.5vw; // para followed by a para followed by a para followed by a para, so 4th para } } Note that the vw values I have used may not be ideal but you can tweak them. Also, the way I have targeted the paras isn't the most elegant, but it should work and give you an idea. I would use the above to get the sizing correct for wide screens and then create breakpoints to tweak the size at smaller screen widths. #the-block-id { p { font-size: 2vw; // the first para @media only screen and (max-width: 640px) { font-size: 3vw; //increase text size for screens up to 640px } } p + p { font-size: 2.5vw; // para followed by a para, so 2nd para } p + p + p { font-size: 3vw; // para followed by a para followed by a para, so 3nd para } p + p + p + p { font-size: 3.5vw; // para followed by a para followed by a para followed by a para, so 4th para } } The above shows an additional breakpoint for the first para on screens under 640px in width.

Try adding the following to your custom css area (Design > Custom CSS) .html-block a:not(.sqs-block-button-element) { color: red !important; // standard link color &:hover { color: blue !important; // hover color } &:active { color: green !important; // color link goes when clicked } } Then insert the colors you need.

I haven't worked with Revolution Slider but I have adapted other JavaScript utilities to work with Squarespace. If you have non minified code it's relatively straightforward, though can take some time, to go through the code and swap out all references to /assets/ /css/ /fonts/ and replace them with /s/. That sets the code to expect everything to be in one folder. You should now move everything from /assets/ /css/ /fonts/ into a single directory with your script and test it locally. If it all works you should be good to upload all of the files to the Squarespace site. This can be time consuming because you need to upload the files one at a time. Another option, if you are working in Squarespace 7.0, is to work in developer mode, where you have the flexibility to upload folder structures. This comes with a downside - your template is effectively locked the moment you engage developer mode - but it means there's no hassle in modifying folder structures.

Squarespace sites are responsive. The aspect ratio of image and video banners is dependent on the user's screen dimensions and browser width. Typically you'll see the banner going from landscape to square and then to portrait as browser widths get smaller. You should think about it in the same way TV stations coped with the transition from 4:3 to 16:9 widescreen tvs. Editors used to work around the 'dead' areas where text would be cut off on a 4:3 screen and avoid having key action happening in those dead areas. For Squarespace to be as safe as possible the primary content should be in a central square on the video. You should consider optimising for the most popular screen dimensions used by your visitors. Also, the black bars are typically used to fit wider screen video into a 16:9 broadcast video aspect ratio. With the web you're not restricted to 16:9 so you can crop the output in your video editing package to remove the black bars and render it at exactly the aspect ratio you need.