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

colin.irwin

Circle Member
  • Content Count

    3,462
  • Joined

  • Last visited

  • Days Won

    90

Everything posted by colin.irwin

  1. It does. I liked your solution but thought that a Markdown block to contain the FAQs would be easier for a non-technical person to maintain. There's still some know-how required but the tools inside the Markdown editor make it relatively straightforward to maintain.
  2. Here's a slightly more concise solution, using jQuery. The idea is to use a Markdown block to hold your questions and answers. It should be the only Markdown block on the page. The Markdown will look something like the following (The + at the start of each question is a cue for the user to know they can expand the entry). + This is a first question ----------------- This is the first line of an answer to the question above. This is a second line of the answer. * Bullet points * Can be used too + This is a second question ----------------- This is a one line answer to the question above. Questions should be styled as H2. Then put the following code into your page's injection point: <script type="text/javascript" src="//ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script> <script> $(document).ready(function(){ $('.markdown-block .sqs-block-content h2').css('cursor','pointer'); $(".markdown-block .sqs-block-content h2").nextUntil("h2").slideToggle(); $(".markdown-block .sqs-block-content h2").click(function() {$(this).nextUntil("h2").slideToggle();}); }); </script> The first can be omitted if you already have a link to jQuery in your sitewide code injection point. The second script tells the mouse cursor to become a pointer when over the Markdown H2s - this is to tell the user it's clickable. Then, when an H2 is clicked it toggles the visibility of all content between the clicked H2 and the next H2 / the end of the markdown block. See it in action here - http://www.silvabokis.com/idea-testing/
  3. Dpi is a function of the printer/display capabilities. A 1500 pixel wide image appears 5 inches wide at 300dpi, 10 inches wide at 150dpi & just over 20 inches wide at 72dpi. The file size remains unchanged. You're correct that if you wanted to display an image 5 inches wide on a computer display then saving 5 inches wide at 300dpi would produce an unnecessarily large file. However, Squarespace resizes your image based on the screen size & supported pixels per inch. That means it will deliver a lower res (smaller file size) file for a standard display than it would for a retina display.
  4. If you're outputting at a certain pixel size then dpi isn't a factor you need to consider when saving an image.
  5. You can create custom maps using Google Maps and then embed them in your Squarespace site.
  6. Google is transitioning its Analytics offering over to a new structure that has, among other things, a different Javascript call to post analytics data. Can this be supported via a Squarespace configuration rather than needing to insert custom code in a template?
  7. Hey! No, it's not an out-of-the-box feature, but it could be implemented using custom scripting. The caveat is that if a person disables scripting in their browser then they would bypass the verification process, but this is true of all verification processes, I think.
  8. Hi Jackie, There's more than one way of doing this. 2 that I can think of: Create an age verification page using Squarespace. On each page test a cookie to see whether age verification has been passed. If it has not been passed the user should be redirected to the age verification page. Create a piece of code that is in the sitewide code injection point. This code would similarly check for presence of an age verification cookie value and, if age verification has not been provided a layer would obscure the screen and ask for age verification.
  9. <style> .post-meta { visibility: hidden } </style>
  10. Hi, I've recorded a screencast that shows the steps required to achieve this.
  11. As I said in a comment to another answer in this thread, keep an eye on the performance of your site. High quality DSLR photos (Jpeg FINE or similar) give a very large file size that Squarespace will then produce versions of for display on different device viewports. If you experience slow image downloads it may be a good idea to experiment with saving out your original images with more Jpeg compression before uploading (70-90% quality gives good results * much smaller file size). It should be the case that the versions Squarespace creates from the smaller original will also be smaller.
  12. I'm not sure if that's 100% true. There was another user who had very slow loading galleries. When he optimised his images and reuploaded them, the site loaded quicker because the images had smaller file sizes.
  13. Squarespace online materials state that a width of 1500 pixels is optimal. Images wider than 1500 pixels are resized to 1500 on upload but can have a small delay before becoming available. The system produces different versions of the uploaded image for different usage scenarios - browser, tablet, retina display - and serves out the most appropriate one for the user's device.
  14. There should be a way of autoplaying by triggering the same function that is attached to the player's onclick state, but it's beyond my understanding of the script to work out which function(s) would need calling and in which order.
  15. Here are a few reasons, in addition to my browsing at work scenario, that autoplay non-stoppable music can be undesirable: Users on smartphones are forced to stream audio that wastes their bandwidth. Users may be already listening to audio on their device, or be multitasking by browsing on their device while watching TV. Autoplay music is an unwanted distraction in that case. If a user journey spans many pages that have autoplay music and/or they revisit the same page multiple times they end up hearing the same starting section of music again and again. Annoying. Doesn’t the fact that you ‘do not find that people will click on the player’ prove that it’s not important to people in the context of your site? After hunting around the screen for a (not present) mute/volume button they are just as likely to hit the back button as they are to turn their speakers down. You need to clear the rights with copyright owners and music publishers before putting commercially available music on your site. For a website to engage with its users it should allow them to feel like they can choose their own path without intrusion or distraction. Forcing users to break from their chain of thought in order to seek a mute button will break their concentration. After all of those caveats, here’s how to hide the player. Add the following CSS to the header injection point: <style media="screen"> .sqs-audio-embed { visibility: hidden; } </style> There should be a way of autoplaying by triggering the same function that is attached to the player’s onclick state, but it’s beyond my understanding of the script to work out which function(s) would need calling and in which order.
  16. There should be a way of autoplaying by triggering the same function that is attached to the player's onclick state, but it's beyond my understanding of the script to work out which function(s) would need calling and in which order.
  17. Playing music automatically without the user asking for it and, as the controls would be hidden, with no means of stopping it, can annoy users. Imagine a scenario where someone sneakily views your website at work, the music starts blaring, they can't stop it and they know they could get into trouble for browsing at work. They're not likely to have positive associations with your site.
  18. The bulk of it was posted on here. I adapted it to add a condition to prevent it firing off multiple events and to insert the redirect function to replace a function that posts to Google Analytics.
  19. Thinking laterally.. ..why not change the Thank you message to set the user's expectations: "Thanks for getting in touch.. ..you will be automatically redirected to my blog page in a few seconds. To get there quicker, click this link... "
  20. You'd expect it to load the thank you message, because the redirect only happens once the DIV that holds the message becomes visible. When I tested it on my site there was a gap of a second or so before the redirect happens, I can't think of any reason that the code would be responsible for any delay.
  21. The following code seems to work. Replace “/” with the relative link you want the redirect to go to. If you want to link to an external site you’ll need to enter a full url of the format http://www.somewhere.com/somepage.htm The code should be inserted in the injection point for the form page: <script src="//ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script> <script> var eventposted = 0; $(document).ready(function() { $('input.button').click(function() { window.setInterval(foo, 100); }); }); function foo() { if (($(".form-submission-text").is(':visible')) && (eventposted == 0)) { window.location.href = "/"; } } </script>
  22. I think you could adapt the code in the link above to fire off a page redirect once the form submission DIV is made visible.
×
×
  • Create New...