Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Advanced Search

colin.irwin

Circle Member
  • Content Count

    3,456
  • Joined

  • Last visited

  • Days Won

    89

Everything posted by colin.irwin

  1. 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.
  2. 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.
  3. 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; } }
  4. In the editor, scroll to the bottom of any page and edit Info Footer Content to remove the text.
  5. Try this input.field-element::placeholder { color: red !important; }
  6. Try turning off parallax scrolling in Site Styles if it is enabled.
  7. A link to your site would make it easier to provide a solution.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. The safest way to do this is to create a new free trial to build the redesign in. If there are large amounts of content from the old site that need to be in the redesign you can use @michaeleparkour's chrome extension to copy content from one site to another. https://www.squarewebsites.org/squarespacewebsites-tools-extension-pro Once the redesign is ready to go live you have a couple of options. Disconnect domain from old site and reconnect it to new site. Temporarily password the old site, delete its content and use the chrome extension to copy the content for the new site into place. You'll also need to copy across code injections, site styles settings and custom css. Which of the above you prefer to do will be influenced by the following factors: If your current site is commerce enabled option 2 is preferable because otherwise you lose customer information and sales history Do you have a large amount of your subscription period to run? If so, option 2 is again preferable because it runs on your existing subscription. Note that Squarespace Circle members can get partial refunds for early subscription cancellations. Option 1 involves less work and, in my experience, switching the domains over is very fast. Most of the DNS settings are already in place so you typically only need to change one CNAME and everything kicks in.
  13. Are you trying to center the search interface within the page and then tweak the date picker height? If so, for centering the search interface you should wrap it in another div and then center the search within that. <div id="search-widget-wrapper"><div id="search-widget">..the script..</div></div> Then center it using the following inserted into the custom css area #search-widget-wrapper { width: 100%; #search-widget { margin: 0 auto; } }
  14. I generally spin up a new free trial and build the new site there. There's a tool available that will let you copy content across to the new trial so that you don't have to rebuild tons of content. The same tool allows you to copy the approved new version over to the existing site to replace the current version. Here's a link to the tool. https://www.squarewebsites.org/squarespacewebsites-tools-extension-pro NB. The tool does the content copying from one site to the other. The Site Styles settings can be exported from the trial site and imported into the old site. Similarly custom css and header and footer code injections need to be manually copied from one site to the other.
  15. Yeah - rather than just /#purpose you can use /home#purpose However, this has the disadvantage of reloading the page rather than just scooting down to the anchor point. If you're happy with coding you could leave the desktop links as they currently are and modify the mobile ones to contain /home#whatever
  16. You put the actual pages in the Not Linked section and then add Links to them in the main navigation.
  17. If you're not going to use the Squarespace cart and checkout process I would recommend using normal pages or blog posts as product pages. They are far more flexible for presenting the features and benefits of a product and you can use normal buttons to link to the enquiry page.
  18. One way to achieve this is to have both gallery types on the page and use custom css to hide one or the other depending on screen width.
  19. I suspect you have inserted the css into the page / section injection point. Instead, move it to sitewide custom css area - Design > Custom CSS NB. You don’t need <style > .. </style > in the custom css area
  20. That's not where you inject it.. Put it in Design > Custom CSS
  21. Find the collection id of the page in question. You do this by inspecting the source code and looking at the body tag. Then insert the collection id into the following code (making sure you keep the # character in the code) and paste the edited code into your custom css area. #collection-id-here { header, footer { display: none !important; } }
×
×
  • Create New...