Jump to content

brandonhendrickson

Circle Member
  • Posts

    32
  • Joined

  • Last visited

Reputation Activity

  1. Thanks
    brandonhendrickson got a reaction from paul2009 in Add a (required) form to a digital product   
    Thank you! That's rotten to hear — it makes Squarespace's option of "Digital Products" much less helpful for those of us doing online education. But I very much appreciate you being clear about this.
  2. Like
    brandonhendrickson reacted to paul2009 in Add a (required) form to a digital product   
    You cannot capture custom information as part of the purchase workflow for a "Digital Product".
    A workaround may be to use a "Customer Activity Automation" in Email Campaigns to send an email after someone purchases a Digital Product, asking the customer to complete a form. However, this will require an Email Campaigns subscription.
    For anyone reading this, I should point out that Custom Product Forms are available for Subscription Products, but they must be Service or Physical products. They are also available for Download products.
    Did this help? Please give feedback by clicking an icon below  ⬇️
  3. Like
    brandonhendrickson got a reaction from elledesgner in New Fluid Engine section block update   
    Site URL: https://www.rochestertag.com/
    So... I hate it — like, hate hate it, like can't use it without screaming curses... and I'm honestly confused as to why this isn't the dominant conversation topic in the SS community.
    Can anyone shed light on this?
    My experience: I've made oodles of sites in SS. I love(d) SS, and have been an enthusiastic evangelist.
    When I started my newest site, I found out that I'm required to use FluidEngine. I wasn't excited about this — it promised a learning curve that I didn't want to take on in a busy month — but, whatever. Gotta roll with the punches.
    My experience of FluidEngine so far has been nothing but woe. I have three questions for anyone who can share their experiences.
    1. What's the benefit supposed to be, again? The primary benefit (to judge by all the videos I've watched on YouTube) is that now we can stack words on top of images. This is a neat feature that I do not need to use. So the primary improvement is, for me, no improvement.
    (Am I wrong about this? Is there another, better feature that FluidEngine is supposed to give us?)
     
    2. Now it's more complicated to make a page, right? Even if I were really good at using Fluid Engine (and... maybe I will be, someday? maybe I'll stick with SS?... maybe?), it seems like it would still be significantly more work to make a simple page.
    I get the drift that the old philosophy of Squarespace ("Build it beautiful") was to limit the number of decisions we could make, to nudge our sites into elegance. (Wanted to complicate it? That's what CSS was for.)
    Now it feels like they've flipped the philosophy — we're forced to make tons of decisions just to put up something simple.
    (Am I wrong about this?)
     
    3. It's hard to get the spacing to work on mobile, right? Like... REALLY hard, right? I loved — loved — how effortlessly my sites used to appear in mobile. There were times I had to wrestle with it, but they were rare, and only when I was trying to do something weird.
    But now — please, please tell me if you have a different experience — the spacing for mobile is really hard to work out! Like, IMPOSSIBLE to work out.
    I didn't trust my judgment of this until I saw this video by Will Myers. His solution (a code injection, some custom CSS, and some juggling) is ingenious — and should not be necessary to ensure a site looks good on a phone.
    (It's telling that, during his explanation, he struggles to make it work. Check out 7:20 — "This is something you need to be careful of, because I don't think Squarespace really likes you doing this, it wants to just force the extra space for some reason, I'm not really too sure why.")
    (God, am I wrong about this? Please tell me I'm wrong about this. Whenever I try to imagine the folks at Squarespace — who have up to now been such fastidious designers — saying, "ah, screw spacing, nobody cares about spacing!" my mind explodes.)
    Is anyone else being driven flipping insane by this?
    And does anyone know if there's a way to opt out of Fluid Design, even if for the near-term future?
  4. Love
    brandonhendrickson got a reaction from Tankgurl in New Fluid Engine section block update   
    Site URL: https://www.rochestertag.com/
    So... I hate it — like, hate hate it, like can't use it without screaming curses... and I'm honestly confused as to why this isn't the dominant conversation topic in the SS community.
    Can anyone shed light on this?
    My experience: I've made oodles of sites in SS. I love(d) SS, and have been an enthusiastic evangelist.
    When I started my newest site, I found out that I'm required to use FluidEngine. I wasn't excited about this — it promised a learning curve that I didn't want to take on in a busy month — but, whatever. Gotta roll with the punches.
    My experience of FluidEngine so far has been nothing but woe. I have three questions for anyone who can share their experiences.
    1. What's the benefit supposed to be, again? The primary benefit (to judge by all the videos I've watched on YouTube) is that now we can stack words on top of images. This is a neat feature that I do not need to use. So the primary improvement is, for me, no improvement.
    (Am I wrong about this? Is there another, better feature that FluidEngine is supposed to give us?)
     
    2. Now it's more complicated to make a page, right? Even if I were really good at using Fluid Engine (and... maybe I will be, someday? maybe I'll stick with SS?... maybe?), it seems like it would still be significantly more work to make a simple page.
    I get the drift that the old philosophy of Squarespace ("Build it beautiful") was to limit the number of decisions we could make, to nudge our sites into elegance. (Wanted to complicate it? That's what CSS was for.)
    Now it feels like they've flipped the philosophy — we're forced to make tons of decisions just to put up something simple.
    (Am I wrong about this?)
     
    3. It's hard to get the spacing to work on mobile, right? Like... REALLY hard, right? I loved — loved — how effortlessly my sites used to appear in mobile. There were times I had to wrestle with it, but they were rare, and only when I was trying to do something weird.
    But now — please, please tell me if you have a different experience — the spacing for mobile is really hard to work out! Like, IMPOSSIBLE to work out.
    I didn't trust my judgment of this until I saw this video by Will Myers. His solution (a code injection, some custom CSS, and some juggling) is ingenious — and should not be necessary to ensure a site looks good on a phone.
    (It's telling that, during his explanation, he struggles to make it work. Check out 7:20 — "This is something you need to be careful of, because I don't think Squarespace really likes you doing this, it wants to just force the extra space for some reason, I'm not really too sure why.")
    (God, am I wrong about this? Please tell me I'm wrong about this. Whenever I try to imagine the folks at Squarespace — who have up to now been such fastidious designers — saying, "ah, screw spacing, nobody cares about spacing!" my mind explodes.)
    Is anyone else being driven flipping insane by this?
    And does anyone know if there's a way to opt out of Fluid Design, even if for the near-term future?
  5. Like
    brandonhendrickson got a reaction from glowstudiosinc in how can i shift from Fluid Engine to Classic Editor?   
    Oh my gosh, Fluid Engine is worse than I feared. I ended up biting the bullet and putting a few hours into learning it yesterday, and find out it's incredibly buggy when it comes to how it displays a page on a smart phone.
    Example: it's very common for me to put an element (e.g. a social link) at the bottom of a section, only for it to appear (on a phone) at the top of the section. (Does this also appear in the "mobile view" preview? Yes. Can I edit in the "mobile view" preview? No, confusingly.)
    Another example: there's a long, empty space in one of the sections (about 1 screen tall) that appears in mobile view. Can I get it out? Nope.
    I trust that SS will fix these problems. In the meantime, it'd be nice if I could make a good-looking website using the old SS.
    Squarespace employees who might be reading this: you're putting your product at risk. You're gambling with your company.
  6. Like
    brandonhendrickson got a reaction from jcurtis1 in New Fluid Engine section block update   
    Site URL: https://www.rochestertag.com/
    So... I hate it — like, hate hate it, like can't use it without screaming curses... and I'm honestly confused as to why this isn't the dominant conversation topic in the SS community.
    Can anyone shed light on this?
    My experience: I've made oodles of sites in SS. I love(d) SS, and have been an enthusiastic evangelist.
    When I started my newest site, I found out that I'm required to use FluidEngine. I wasn't excited about this — it promised a learning curve that I didn't want to take on in a busy month — but, whatever. Gotta roll with the punches.
    My experience of FluidEngine so far has been nothing but woe. I have three questions for anyone who can share their experiences.
    1. What's the benefit supposed to be, again? The primary benefit (to judge by all the videos I've watched on YouTube) is that now we can stack words on top of images. This is a neat feature that I do not need to use. So the primary improvement is, for me, no improvement.
    (Am I wrong about this? Is there another, better feature that FluidEngine is supposed to give us?)
     
    2. Now it's more complicated to make a page, right? Even if I were really good at using Fluid Engine (and... maybe I will be, someday? maybe I'll stick with SS?... maybe?), it seems like it would still be significantly more work to make a simple page.
    I get the drift that the old philosophy of Squarespace ("Build it beautiful") was to limit the number of decisions we could make, to nudge our sites into elegance. (Wanted to complicate it? That's what CSS was for.)
    Now it feels like they've flipped the philosophy — we're forced to make tons of decisions just to put up something simple.
    (Am I wrong about this?)
     
    3. It's hard to get the spacing to work on mobile, right? Like... REALLY hard, right? I loved — loved — how effortlessly my sites used to appear in mobile. There were times I had to wrestle with it, but they were rare, and only when I was trying to do something weird.
    But now — please, please tell me if you have a different experience — the spacing for mobile is really hard to work out! Like, IMPOSSIBLE to work out.
    I didn't trust my judgment of this until I saw this video by Will Myers. His solution (a code injection, some custom CSS, and some juggling) is ingenious — and should not be necessary to ensure a site looks good on a phone.
    (It's telling that, during his explanation, he struggles to make it work. Check out 7:20 — "This is something you need to be careful of, because I don't think Squarespace really likes you doing this, it wants to just force the extra space for some reason, I'm not really too sure why.")
    (God, am I wrong about this? Please tell me I'm wrong about this. Whenever I try to imagine the folks at Squarespace — who have up to now been such fastidious designers — saying, "ah, screw spacing, nobody cares about spacing!" my mind explodes.)
    Is anyone else being driven flipping insane by this?
    And does anyone know if there's a way to opt out of Fluid Design, even if for the near-term future?
  7. Like
    brandonhendrickson got a reaction from SE2M in New Fluid Engine section block update   
    Site URL: https://www.rochestertag.com/
    So... I hate it — like, hate hate it, like can't use it without screaming curses... and I'm honestly confused as to why this isn't the dominant conversation topic in the SS community.
    Can anyone shed light on this?
    My experience: I've made oodles of sites in SS. I love(d) SS, and have been an enthusiastic evangelist.
    When I started my newest site, I found out that I'm required to use FluidEngine. I wasn't excited about this — it promised a learning curve that I didn't want to take on in a busy month — but, whatever. Gotta roll with the punches.
    My experience of FluidEngine so far has been nothing but woe. I have three questions for anyone who can share their experiences.
    1. What's the benefit supposed to be, again? The primary benefit (to judge by all the videos I've watched on YouTube) is that now we can stack words on top of images. This is a neat feature that I do not need to use. So the primary improvement is, for me, no improvement.
    (Am I wrong about this? Is there another, better feature that FluidEngine is supposed to give us?)
     
    2. Now it's more complicated to make a page, right? Even if I were really good at using Fluid Engine (and... maybe I will be, someday? maybe I'll stick with SS?... maybe?), it seems like it would still be significantly more work to make a simple page.
    I get the drift that the old philosophy of Squarespace ("Build it beautiful") was to limit the number of decisions we could make, to nudge our sites into elegance. (Wanted to complicate it? That's what CSS was for.)
    Now it feels like they've flipped the philosophy — we're forced to make tons of decisions just to put up something simple.
    (Am I wrong about this?)
     
    3. It's hard to get the spacing to work on mobile, right? Like... REALLY hard, right? I loved — loved — how effortlessly my sites used to appear in mobile. There were times I had to wrestle with it, but they were rare, and only when I was trying to do something weird.
    But now — please, please tell me if you have a different experience — the spacing for mobile is really hard to work out! Like, IMPOSSIBLE to work out.
    I didn't trust my judgment of this until I saw this video by Will Myers. His solution (a code injection, some custom CSS, and some juggling) is ingenious — and should not be necessary to ensure a site looks good on a phone.
    (It's telling that, during his explanation, he struggles to make it work. Check out 7:20 — "This is something you need to be careful of, because I don't think Squarespace really likes you doing this, it wants to just force the extra space for some reason, I'm not really too sure why.")
    (God, am I wrong about this? Please tell me I'm wrong about this. Whenever I try to imagine the folks at Squarespace — who have up to now been such fastidious designers — saying, "ah, screw spacing, nobody cares about spacing!" my mind explodes.)
    Is anyone else being driven flipping insane by this?
    And does anyone know if there's a way to opt out of Fluid Design, even if for the near-term future?
  8. Like
    brandonhendrickson got a reaction from tuanphan in .svg section-background v.7.1   
    Holy crap, this worked for me too! (I know that shouldn't be surprising, but I'm not very good at this, and I was trying to bring in an SVG from a different site — HeroPatterns.com? And I really didn't think it would go well.)
    Here's mine:
    section[data-section-id="6335a2837b42dc14fa98c077"] .section-background { background-image: url("data:image/svg+xml,%3Csvg width='100' height='20' viewBox='0 0 100 20' xmlns='http://www.w3.org/2000/svg'%3E%3Cpath d='M21.184 20c.357-.13.72-.264 1.088-.402l1.768-.661C33.64 15.347 39.647 14 50 14c10.271 0 15.362 1.222 24.629 4.928.955.383 1.869.74 2.75 1.072h6.225c-2.51-.73-5.139-1.691-8.233-2.928C65.888 13.278 60.562 12 50 12c-10.626 0-16.855 1.397-26.66 5.063l-1.767.662c-2.475.923-4.66 1.674-6.724 2.275h6.335zm0-20C13.258 2.892 8.077 4 0 4V2c5.744 0 9.951-.574 14.85-2h6.334zM77.38 0C85.239 2.966 90.502 4 100 4V2c-6.842 0-11.386-.542-16.396-2h-6.225zM0 14c8.44 0 13.718-1.21 22.272-4.402l1.768-.661C33.64 5.347 39.647 4 50 4c10.271 0 15.362 1.222 24.629 4.928C84.112 12.722 89.438 14 100 14v-2c-10.271 0-15.362-1.222-24.629-4.928C65.888 3.278 60.562 2 50 2 39.374 2 33.145 3.397 23.34 7.063l-1.767.662C13.223 10.84 8.163 12 0 12v2z' fill='%23e2a47d' fill-opacity='0.4' fill-rule='evenodd'/%3E%3C/svg%3E");}  
  9. Like
    brandonhendrickson got a reaction from cdavidson in New Fluid Engine section block update   
    Site URL: https://www.rochestertag.com/
    So... I hate it — like, hate hate it, like can't use it without screaming curses... and I'm honestly confused as to why this isn't the dominant conversation topic in the SS community.
    Can anyone shed light on this?
    My experience: I've made oodles of sites in SS. I love(d) SS, and have been an enthusiastic evangelist.
    When I started my newest site, I found out that I'm required to use FluidEngine. I wasn't excited about this — it promised a learning curve that I didn't want to take on in a busy month — but, whatever. Gotta roll with the punches.
    My experience of FluidEngine so far has been nothing but woe. I have three questions for anyone who can share their experiences.
    1. What's the benefit supposed to be, again? The primary benefit (to judge by all the videos I've watched on YouTube) is that now we can stack words on top of images. This is a neat feature that I do not need to use. So the primary improvement is, for me, no improvement.
    (Am I wrong about this? Is there another, better feature that FluidEngine is supposed to give us?)
     
    2. Now it's more complicated to make a page, right? Even if I were really good at using Fluid Engine (and... maybe I will be, someday? maybe I'll stick with SS?... maybe?), it seems like it would still be significantly more work to make a simple page.
    I get the drift that the old philosophy of Squarespace ("Build it beautiful") was to limit the number of decisions we could make, to nudge our sites into elegance. (Wanted to complicate it? That's what CSS was for.)
    Now it feels like they've flipped the philosophy — we're forced to make tons of decisions just to put up something simple.
    (Am I wrong about this?)
     
    3. It's hard to get the spacing to work on mobile, right? Like... REALLY hard, right? I loved — loved — how effortlessly my sites used to appear in mobile. There were times I had to wrestle with it, but they were rare, and only when I was trying to do something weird.
    But now — please, please tell me if you have a different experience — the spacing for mobile is really hard to work out! Like, IMPOSSIBLE to work out.
    I didn't trust my judgment of this until I saw this video by Will Myers. His solution (a code injection, some custom CSS, and some juggling) is ingenious — and should not be necessary to ensure a site looks good on a phone.
    (It's telling that, during his explanation, he struggles to make it work. Check out 7:20 — "This is something you need to be careful of, because I don't think Squarespace really likes you doing this, it wants to just force the extra space for some reason, I'm not really too sure why.")
    (God, am I wrong about this? Please tell me I'm wrong about this. Whenever I try to imagine the folks at Squarespace — who have up to now been such fastidious designers — saying, "ah, screw spacing, nobody cares about spacing!" my mind explodes.)
    Is anyone else being driven flipping insane by this?
    And does anyone know if there's a way to opt out of Fluid Design, even if for the near-term future?
  10. Like
    brandonhendrickson got a reaction from TheEcoporium in New Fluid Engine section block update   
    Site URL: https://www.rochestertag.com/
    So... I hate it — like, hate hate it, like can't use it without screaming curses... and I'm honestly confused as to why this isn't the dominant conversation topic in the SS community.
    Can anyone shed light on this?
    My experience: I've made oodles of sites in SS. I love(d) SS, and have been an enthusiastic evangelist.
    When I started my newest site, I found out that I'm required to use FluidEngine. I wasn't excited about this — it promised a learning curve that I didn't want to take on in a busy month — but, whatever. Gotta roll with the punches.
    My experience of FluidEngine so far has been nothing but woe. I have three questions for anyone who can share their experiences.
    1. What's the benefit supposed to be, again? The primary benefit (to judge by all the videos I've watched on YouTube) is that now we can stack words on top of images. This is a neat feature that I do not need to use. So the primary improvement is, for me, no improvement.
    (Am I wrong about this? Is there another, better feature that FluidEngine is supposed to give us?)
     
    2. Now it's more complicated to make a page, right? Even if I were really good at using Fluid Engine (and... maybe I will be, someday? maybe I'll stick with SS?... maybe?), it seems like it would still be significantly more work to make a simple page.
    I get the drift that the old philosophy of Squarespace ("Build it beautiful") was to limit the number of decisions we could make, to nudge our sites into elegance. (Wanted to complicate it? That's what CSS was for.)
    Now it feels like they've flipped the philosophy — we're forced to make tons of decisions just to put up something simple.
    (Am I wrong about this?)
     
    3. It's hard to get the spacing to work on mobile, right? Like... REALLY hard, right? I loved — loved — how effortlessly my sites used to appear in mobile. There were times I had to wrestle with it, but they were rare, and only when I was trying to do something weird.
    But now — please, please tell me if you have a different experience — the spacing for mobile is really hard to work out! Like, IMPOSSIBLE to work out.
    I didn't trust my judgment of this until I saw this video by Will Myers. His solution (a code injection, some custom CSS, and some juggling) is ingenious — and should not be necessary to ensure a site looks good on a phone.
    (It's telling that, during his explanation, he struggles to make it work. Check out 7:20 — "This is something you need to be careful of, because I don't think Squarespace really likes you doing this, it wants to just force the extra space for some reason, I'm not really too sure why.")
    (God, am I wrong about this? Please tell me I'm wrong about this. Whenever I try to imagine the folks at Squarespace — who have up to now been such fastidious designers — saying, "ah, screw spacing, nobody cares about spacing!" my mind explodes.)
    Is anyone else being driven flipping insane by this?
    And does anyone know if there's a way to opt out of Fluid Design, even if for the near-term future?
  11. Like
    brandonhendrickson got a reaction from MarcWatson in New Fluid Engine section block update   
    Site URL: https://www.rochestertag.com/
    So... I hate it — like, hate hate it, like can't use it without screaming curses... and I'm honestly confused as to why this isn't the dominant conversation topic in the SS community.
    Can anyone shed light on this?
    My experience: I've made oodles of sites in SS. I love(d) SS, and have been an enthusiastic evangelist.
    When I started my newest site, I found out that I'm required to use FluidEngine. I wasn't excited about this — it promised a learning curve that I didn't want to take on in a busy month — but, whatever. Gotta roll with the punches.
    My experience of FluidEngine so far has been nothing but woe. I have three questions for anyone who can share their experiences.
    1. What's the benefit supposed to be, again? The primary benefit (to judge by all the videos I've watched on YouTube) is that now we can stack words on top of images. This is a neat feature that I do not need to use. So the primary improvement is, for me, no improvement.
    (Am I wrong about this? Is there another, better feature that FluidEngine is supposed to give us?)
     
    2. Now it's more complicated to make a page, right? Even if I were really good at using Fluid Engine (and... maybe I will be, someday? maybe I'll stick with SS?... maybe?), it seems like it would still be significantly more work to make a simple page.
    I get the drift that the old philosophy of Squarespace ("Build it beautiful") was to limit the number of decisions we could make, to nudge our sites into elegance. (Wanted to complicate it? That's what CSS was for.)
    Now it feels like they've flipped the philosophy — we're forced to make tons of decisions just to put up something simple.
    (Am I wrong about this?)
     
    3. It's hard to get the spacing to work on mobile, right? Like... REALLY hard, right? I loved — loved — how effortlessly my sites used to appear in mobile. There were times I had to wrestle with it, but they were rare, and only when I was trying to do something weird.
    But now — please, please tell me if you have a different experience — the spacing for mobile is really hard to work out! Like, IMPOSSIBLE to work out.
    I didn't trust my judgment of this until I saw this video by Will Myers. His solution (a code injection, some custom CSS, and some juggling) is ingenious — and should not be necessary to ensure a site looks good on a phone.
    (It's telling that, during his explanation, he struggles to make it work. Check out 7:20 — "This is something you need to be careful of, because I don't think Squarespace really likes you doing this, it wants to just force the extra space for some reason, I'm not really too sure why.")
    (God, am I wrong about this? Please tell me I'm wrong about this. Whenever I try to imagine the folks at Squarespace — who have up to now been such fastidious designers — saying, "ah, screw spacing, nobody cares about spacing!" my mind explodes.)
    Is anyone else being driven flipping insane by this?
    And does anyone know if there's a way to opt out of Fluid Design, even if for the near-term future?
  12. Like
    brandonhendrickson got a reaction from FabiSantiago in how can i shift from Fluid Engine to Classic Editor?   
    Oh my gosh, Fluid Engine is worse than I feared. I ended up biting the bullet and putting a few hours into learning it yesterday, and find out it's incredibly buggy when it comes to how it displays a page on a smart phone.
    Example: it's very common for me to put an element (e.g. a social link) at the bottom of a section, only for it to appear (on a phone) at the top of the section. (Does this also appear in the "mobile view" preview? Yes. Can I edit in the "mobile view" preview? No, confusingly.)
    Another example: there's a long, empty space in one of the sections (about 1 screen tall) that appears in mobile view. Can I get it out? Nope.
    I trust that SS will fix these problems. In the meantime, it'd be nice if I could make a good-looking website using the old SS.
    Squarespace employees who might be reading this: you're putting your product at risk. You're gambling with your company.
  13. Like
    brandonhendrickson got a reaction from Studioplaceofficial in New Fluid Engine section block update   
    Site URL: https://www.rochestertag.com/
    So... I hate it — like, hate hate it, like can't use it without screaming curses... and I'm honestly confused as to why this isn't the dominant conversation topic in the SS community.
    Can anyone shed light on this?
    My experience: I've made oodles of sites in SS. I love(d) SS, and have been an enthusiastic evangelist.
    When I started my newest site, I found out that I'm required to use FluidEngine. I wasn't excited about this — it promised a learning curve that I didn't want to take on in a busy month — but, whatever. Gotta roll with the punches.
    My experience of FluidEngine so far has been nothing but woe. I have three questions for anyone who can share their experiences.
    1. What's the benefit supposed to be, again? The primary benefit (to judge by all the videos I've watched on YouTube) is that now we can stack words on top of images. This is a neat feature that I do not need to use. So the primary improvement is, for me, no improvement.
    (Am I wrong about this? Is there another, better feature that FluidEngine is supposed to give us?)
     
    2. Now it's more complicated to make a page, right? Even if I were really good at using Fluid Engine (and... maybe I will be, someday? maybe I'll stick with SS?... maybe?), it seems like it would still be significantly more work to make a simple page.
    I get the drift that the old philosophy of Squarespace ("Build it beautiful") was to limit the number of decisions we could make, to nudge our sites into elegance. (Wanted to complicate it? That's what CSS was for.)
    Now it feels like they've flipped the philosophy — we're forced to make tons of decisions just to put up something simple.
    (Am I wrong about this?)
     
    3. It's hard to get the spacing to work on mobile, right? Like... REALLY hard, right? I loved — loved — how effortlessly my sites used to appear in mobile. There were times I had to wrestle with it, but they were rare, and only when I was trying to do something weird.
    But now — please, please tell me if you have a different experience — the spacing for mobile is really hard to work out! Like, IMPOSSIBLE to work out.
    I didn't trust my judgment of this until I saw this video by Will Myers. His solution (a code injection, some custom CSS, and some juggling) is ingenious — and should not be necessary to ensure a site looks good on a phone.
    (It's telling that, during his explanation, he struggles to make it work. Check out 7:20 — "This is something you need to be careful of, because I don't think Squarespace really likes you doing this, it wants to just force the extra space for some reason, I'm not really too sure why.")
    (God, am I wrong about this? Please tell me I'm wrong about this. Whenever I try to imagine the folks at Squarespace — who have up to now been such fastidious designers — saying, "ah, screw spacing, nobody cares about spacing!" my mind explodes.)
    Is anyone else being driven flipping insane by this?
    And does anyone know if there's a way to opt out of Fluid Design, even if for the near-term future?
  14. Like
    brandonhendrickson got a reaction from FabiSantiago in New Fluid Engine section block update   
    Site URL: https://www.rochestertag.com/
    So... I hate it — like, hate hate it, like can't use it without screaming curses... and I'm honestly confused as to why this isn't the dominant conversation topic in the SS community.
    Can anyone shed light on this?
    My experience: I've made oodles of sites in SS. I love(d) SS, and have been an enthusiastic evangelist.
    When I started my newest site, I found out that I'm required to use FluidEngine. I wasn't excited about this — it promised a learning curve that I didn't want to take on in a busy month — but, whatever. Gotta roll with the punches.
    My experience of FluidEngine so far has been nothing but woe. I have three questions for anyone who can share their experiences.
    1. What's the benefit supposed to be, again? The primary benefit (to judge by all the videos I've watched on YouTube) is that now we can stack words on top of images. This is a neat feature that I do not need to use. So the primary improvement is, for me, no improvement.
    (Am I wrong about this? Is there another, better feature that FluidEngine is supposed to give us?)
     
    2. Now it's more complicated to make a page, right? Even if I were really good at using Fluid Engine (and... maybe I will be, someday? maybe I'll stick with SS?... maybe?), it seems like it would still be significantly more work to make a simple page.
    I get the drift that the old philosophy of Squarespace ("Build it beautiful") was to limit the number of decisions we could make, to nudge our sites into elegance. (Wanted to complicate it? That's what CSS was for.)
    Now it feels like they've flipped the philosophy — we're forced to make tons of decisions just to put up something simple.
    (Am I wrong about this?)
     
    3. It's hard to get the spacing to work on mobile, right? Like... REALLY hard, right? I loved — loved — how effortlessly my sites used to appear in mobile. There were times I had to wrestle with it, but they were rare, and only when I was trying to do something weird.
    But now — please, please tell me if you have a different experience — the spacing for mobile is really hard to work out! Like, IMPOSSIBLE to work out.
    I didn't trust my judgment of this until I saw this video by Will Myers. His solution (a code injection, some custom CSS, and some juggling) is ingenious — and should not be necessary to ensure a site looks good on a phone.
    (It's telling that, during his explanation, he struggles to make it work. Check out 7:20 — "This is something you need to be careful of, because I don't think Squarespace really likes you doing this, it wants to just force the extra space for some reason, I'm not really too sure why.")
    (God, am I wrong about this? Please tell me I'm wrong about this. Whenever I try to imagine the folks at Squarespace — who have up to now been such fastidious designers — saying, "ah, screw spacing, nobody cares about spacing!" my mind explodes.)
    Is anyone else being driven flipping insane by this?
    And does anyone know if there's a way to opt out of Fluid Design, even if for the near-term future?
  15. Love
    brandonhendrickson got a reaction from jred in New Fluid Engine section block update   
    Site URL: https://www.rochestertag.com/
    So... I hate it — like, hate hate it, like can't use it without screaming curses... and I'm honestly confused as to why this isn't the dominant conversation topic in the SS community.
    Can anyone shed light on this?
    My experience: I've made oodles of sites in SS. I love(d) SS, and have been an enthusiastic evangelist.
    When I started my newest site, I found out that I'm required to use FluidEngine. I wasn't excited about this — it promised a learning curve that I didn't want to take on in a busy month — but, whatever. Gotta roll with the punches.
    My experience of FluidEngine so far has been nothing but woe. I have three questions for anyone who can share their experiences.
    1. What's the benefit supposed to be, again? The primary benefit (to judge by all the videos I've watched on YouTube) is that now we can stack words on top of images. This is a neat feature that I do not need to use. So the primary improvement is, for me, no improvement.
    (Am I wrong about this? Is there another, better feature that FluidEngine is supposed to give us?)
     
    2. Now it's more complicated to make a page, right? Even if I were really good at using Fluid Engine (and... maybe I will be, someday? maybe I'll stick with SS?... maybe?), it seems like it would still be significantly more work to make a simple page.
    I get the drift that the old philosophy of Squarespace ("Build it beautiful") was to limit the number of decisions we could make, to nudge our sites into elegance. (Wanted to complicate it? That's what CSS was for.)
    Now it feels like they've flipped the philosophy — we're forced to make tons of decisions just to put up something simple.
    (Am I wrong about this?)
     
    3. It's hard to get the spacing to work on mobile, right? Like... REALLY hard, right? I loved — loved — how effortlessly my sites used to appear in mobile. There were times I had to wrestle with it, but they were rare, and only when I was trying to do something weird.
    But now — please, please tell me if you have a different experience — the spacing for mobile is really hard to work out! Like, IMPOSSIBLE to work out.
    I didn't trust my judgment of this until I saw this video by Will Myers. His solution (a code injection, some custom CSS, and some juggling) is ingenious — and should not be necessary to ensure a site looks good on a phone.
    (It's telling that, during his explanation, he struggles to make it work. Check out 7:20 — "This is something you need to be careful of, because I don't think Squarespace really likes you doing this, it wants to just force the extra space for some reason, I'm not really too sure why.")
    (God, am I wrong about this? Please tell me I'm wrong about this. Whenever I try to imagine the folks at Squarespace — who have up to now been such fastidious designers — saying, "ah, screw spacing, nobody cares about spacing!" my mind explodes.)
    Is anyone else being driven flipping insane by this?
    And does anyone know if there's a way to opt out of Fluid Design, even if for the near-term future?
  16. Like
    brandonhendrickson got a reaction from ilseS in New Fluid Engine section block update   
    Site URL: https://www.rochestertag.com/
    So... I hate it — like, hate hate it, like can't use it without screaming curses... and I'm honestly confused as to why this isn't the dominant conversation topic in the SS community.
    Can anyone shed light on this?
    My experience: I've made oodles of sites in SS. I love(d) SS, and have been an enthusiastic evangelist.
    When I started my newest site, I found out that I'm required to use FluidEngine. I wasn't excited about this — it promised a learning curve that I didn't want to take on in a busy month — but, whatever. Gotta roll with the punches.
    My experience of FluidEngine so far has been nothing but woe. I have three questions for anyone who can share their experiences.
    1. What's the benefit supposed to be, again? The primary benefit (to judge by all the videos I've watched on YouTube) is that now we can stack words on top of images. This is a neat feature that I do not need to use. So the primary improvement is, for me, no improvement.
    (Am I wrong about this? Is there another, better feature that FluidEngine is supposed to give us?)
     
    2. Now it's more complicated to make a page, right? Even if I were really good at using Fluid Engine (and... maybe I will be, someday? maybe I'll stick with SS?... maybe?), it seems like it would still be significantly more work to make a simple page.
    I get the drift that the old philosophy of Squarespace ("Build it beautiful") was to limit the number of decisions we could make, to nudge our sites into elegance. (Wanted to complicate it? That's what CSS was for.)
    Now it feels like they've flipped the philosophy — we're forced to make tons of decisions just to put up something simple.
    (Am I wrong about this?)
     
    3. It's hard to get the spacing to work on mobile, right? Like... REALLY hard, right? I loved — loved — how effortlessly my sites used to appear in mobile. There were times I had to wrestle with it, but they were rare, and only when I was trying to do something weird.
    But now — please, please tell me if you have a different experience — the spacing for mobile is really hard to work out! Like, IMPOSSIBLE to work out.
    I didn't trust my judgment of this until I saw this video by Will Myers. His solution (a code injection, some custom CSS, and some juggling) is ingenious — and should not be necessary to ensure a site looks good on a phone.
    (It's telling that, during his explanation, he struggles to make it work. Check out 7:20 — "This is something you need to be careful of, because I don't think Squarespace really likes you doing this, it wants to just force the extra space for some reason, I'm not really too sure why.")
    (God, am I wrong about this? Please tell me I'm wrong about this. Whenever I try to imagine the folks at Squarespace — who have up to now been such fastidious designers — saying, "ah, screw spacing, nobody cares about spacing!" my mind explodes.)
    Is anyone else being driven flipping insane by this?
    And does anyone know if there's a way to opt out of Fluid Design, even if for the near-term future?
  17. Like
    brandonhendrickson got a reaction from AC57 in New Fluid Engine section block update   
    Site URL: https://www.rochestertag.com/
    So... I hate it — like, hate hate it, like can't use it without screaming curses... and I'm honestly confused as to why this isn't the dominant conversation topic in the SS community.
    Can anyone shed light on this?
    My experience: I've made oodles of sites in SS. I love(d) SS, and have been an enthusiastic evangelist.
    When I started my newest site, I found out that I'm required to use FluidEngine. I wasn't excited about this — it promised a learning curve that I didn't want to take on in a busy month — but, whatever. Gotta roll with the punches.
    My experience of FluidEngine so far has been nothing but woe. I have three questions for anyone who can share their experiences.
    1. What's the benefit supposed to be, again? The primary benefit (to judge by all the videos I've watched on YouTube) is that now we can stack words on top of images. This is a neat feature that I do not need to use. So the primary improvement is, for me, no improvement.
    (Am I wrong about this? Is there another, better feature that FluidEngine is supposed to give us?)
     
    2. Now it's more complicated to make a page, right? Even if I were really good at using Fluid Engine (and... maybe I will be, someday? maybe I'll stick with SS?... maybe?), it seems like it would still be significantly more work to make a simple page.
    I get the drift that the old philosophy of Squarespace ("Build it beautiful") was to limit the number of decisions we could make, to nudge our sites into elegance. (Wanted to complicate it? That's what CSS was for.)
    Now it feels like they've flipped the philosophy — we're forced to make tons of decisions just to put up something simple.
    (Am I wrong about this?)
     
    3. It's hard to get the spacing to work on mobile, right? Like... REALLY hard, right? I loved — loved — how effortlessly my sites used to appear in mobile. There were times I had to wrestle with it, but they were rare, and only when I was trying to do something weird.
    But now — please, please tell me if you have a different experience — the spacing for mobile is really hard to work out! Like, IMPOSSIBLE to work out.
    I didn't trust my judgment of this until I saw this video by Will Myers. His solution (a code injection, some custom CSS, and some juggling) is ingenious — and should not be necessary to ensure a site looks good on a phone.
    (It's telling that, during his explanation, he struggles to make it work. Check out 7:20 — "This is something you need to be careful of, because I don't think Squarespace really likes you doing this, it wants to just force the extra space for some reason, I'm not really too sure why.")
    (God, am I wrong about this? Please tell me I'm wrong about this. Whenever I try to imagine the folks at Squarespace — who have up to now been such fastidious designers — saying, "ah, screw spacing, nobody cares about spacing!" my mind explodes.)
    Is anyone else being driven flipping insane by this?
    And does anyone know if there's a way to opt out of Fluid Design, even if for the near-term future?
  18. Like
    brandonhendrickson got a reaction from creedon in New Fluid Engine section block update   
    Site URL: https://www.rochestertag.com/
    So... I hate it — like, hate hate it, like can't use it without screaming curses... and I'm honestly confused as to why this isn't the dominant conversation topic in the SS community.
    Can anyone shed light on this?
    My experience: I've made oodles of sites in SS. I love(d) SS, and have been an enthusiastic evangelist.
    When I started my newest site, I found out that I'm required to use FluidEngine. I wasn't excited about this — it promised a learning curve that I didn't want to take on in a busy month — but, whatever. Gotta roll with the punches.
    My experience of FluidEngine so far has been nothing but woe. I have three questions for anyone who can share their experiences.
    1. What's the benefit supposed to be, again? The primary benefit (to judge by all the videos I've watched on YouTube) is that now we can stack words on top of images. This is a neat feature that I do not need to use. So the primary improvement is, for me, no improvement.
    (Am I wrong about this? Is there another, better feature that FluidEngine is supposed to give us?)
     
    2. Now it's more complicated to make a page, right? Even if I were really good at using Fluid Engine (and... maybe I will be, someday? maybe I'll stick with SS?... maybe?), it seems like it would still be significantly more work to make a simple page.
    I get the drift that the old philosophy of Squarespace ("Build it beautiful") was to limit the number of decisions we could make, to nudge our sites into elegance. (Wanted to complicate it? That's what CSS was for.)
    Now it feels like they've flipped the philosophy — we're forced to make tons of decisions just to put up something simple.
    (Am I wrong about this?)
     
    3. It's hard to get the spacing to work on mobile, right? Like... REALLY hard, right? I loved — loved — how effortlessly my sites used to appear in mobile. There were times I had to wrestle with it, but they were rare, and only when I was trying to do something weird.
    But now — please, please tell me if you have a different experience — the spacing for mobile is really hard to work out! Like, IMPOSSIBLE to work out.
    I didn't trust my judgment of this until I saw this video by Will Myers. His solution (a code injection, some custom CSS, and some juggling) is ingenious — and should not be necessary to ensure a site looks good on a phone.
    (It's telling that, during his explanation, he struggles to make it work. Check out 7:20 — "This is something you need to be careful of, because I don't think Squarespace really likes you doing this, it wants to just force the extra space for some reason, I'm not really too sure why.")
    (God, am I wrong about this? Please tell me I'm wrong about this. Whenever I try to imagine the folks at Squarespace — who have up to now been such fastidious designers — saying, "ah, screw spacing, nobody cares about spacing!" my mind explodes.)
    Is anyone else being driven flipping insane by this?
    And does anyone know if there's a way to opt out of Fluid Design, even if for the near-term future?
  19. Like
    brandonhendrickson got a reaction from tinabee in how can i shift from Fluid Engine to Classic Editor?   
    Oh my gosh, Fluid Engine is worse than I feared. I ended up biting the bullet and putting a few hours into learning it yesterday, and find out it's incredibly buggy when it comes to how it displays a page on a smart phone.
    Example: it's very common for me to put an element (e.g. a social link) at the bottom of a section, only for it to appear (on a phone) at the top of the section. (Does this also appear in the "mobile view" preview? Yes. Can I edit in the "mobile view" preview? No, confusingly.)
    Another example: there's a long, empty space in one of the sections (about 1 screen tall) that appears in mobile view. Can I get it out? Nope.
    I trust that SS will fix these problems. In the meantime, it'd be nice if I could make a good-looking website using the old SS.
    Squarespace employees who might be reading this: you're putting your product at risk. You're gambling with your company.
  20. Like
    brandonhendrickson got a reaction from Turbine in how can i shift from Fluid Engine to Classic Editor?   
    Oh my gosh, Fluid Engine is worse than I feared. I ended up biting the bullet and putting a few hours into learning it yesterday, and find out it's incredibly buggy when it comes to how it displays a page on a smart phone.
    Example: it's very common for me to put an element (e.g. a social link) at the bottom of a section, only for it to appear (on a phone) at the top of the section. (Does this also appear in the "mobile view" preview? Yes. Can I edit in the "mobile view" preview? No, confusingly.)
    Another example: there's a long, empty space in one of the sections (about 1 screen tall) that appears in mobile view. Can I get it out? Nope.
    I trust that SS will fix these problems. In the meantime, it'd be nice if I could make a good-looking website using the old SS.
    Squarespace employees who might be reading this: you're putting your product at risk. You're gambling with your company.
  21. Like
    brandonhendrickson got a reaction from Turbine in how can i shift from Fluid Engine to Classic Editor?   
    I'm a longtime Squarespace user, and I'm looking to throw together a quick one-page site for a not-for-profit that I run.
    I logged on this morning to make it, and found that... everything has changed? I'm referring, I gather, to "Fluid Engine". I had already been adept at using 7.1, but suddenly lots of stuff looks different, and making anything is hard.
    I'm sure that once I get used to it it'll be wonderful blah blah blah... but in the meantime I'd really just like to make a quick new website, and not have to re-teach myself the fundamentals of Squarespace.
    Is it possible for me to "turn off" Fluid Engine?
  22. Like
    brandonhendrickson got a reaction from kevinpatrickrobbins in how can i shift from Fluid Engine to Classic Editor?   
    I'm a longtime Squarespace user, and I'm looking to throw together a quick one-page site for a not-for-profit that I run.
    I logged on this morning to make it, and found that... everything has changed? I'm referring, I gather, to "Fluid Engine". I had already been adept at using 7.1, but suddenly lots of stuff looks different, and making anything is hard.
    I'm sure that once I get used to it it'll be wonderful blah blah blah... but in the meantime I'd really just like to make a quick new website, and not have to re-teach myself the fundamentals of Squarespace.
    Is it possible for me to "turn off" Fluid Engine?
  23. Like
    brandonhendrickson got a reaction from SatsumaStreet in how can i shift from Fluid Engine to Classic Editor?   
    Oh my gosh, Fluid Engine is worse than I feared. I ended up biting the bullet and putting a few hours into learning it yesterday, and find out it's incredibly buggy when it comes to how it displays a page on a smart phone.
    Example: it's very common for me to put an element (e.g. a social link) at the bottom of a section, only for it to appear (on a phone) at the top of the section. (Does this also appear in the "mobile view" preview? Yes. Can I edit in the "mobile view" preview? No, confusingly.)
    Another example: there's a long, empty space in one of the sections (about 1 screen tall) that appears in mobile view. Can I get it out? Nope.
    I trust that SS will fix these problems. In the meantime, it'd be nice if I could make a good-looking website using the old SS.
    Squarespace employees who might be reading this: you're putting your product at risk. You're gambling with your company.
  24. Like
    brandonhendrickson got a reaction from SatsumaStreet in how can i shift from Fluid Engine to Classic Editor?   
    I'm a longtime Squarespace user, and I'm looking to throw together a quick one-page site for a not-for-profit that I run.
    I logged on this morning to make it, and found that... everything has changed? I'm referring, I gather, to "Fluid Engine". I had already been adept at using 7.1, but suddenly lots of stuff looks different, and making anything is hard.
    I'm sure that once I get used to it it'll be wonderful blah blah blah... but in the meantime I'd really just like to make a quick new website, and not have to re-teach myself the fundamentals of Squarespace.
    Is it possible for me to "turn off" Fluid Engine?
  25. Like
    brandonhendrickson got a reaction from valerie.cline in how can i shift from Fluid Engine to Classic Editor?   
    Oh my gosh, Fluid Engine is worse than I feared. I ended up biting the bullet and putting a few hours into learning it yesterday, and find out it's incredibly buggy when it comes to how it displays a page on a smart phone.
    Example: it's very common for me to put an element (e.g. a social link) at the bottom of a section, only for it to appear (on a phone) at the top of the section. (Does this also appear in the "mobile view" preview? Yes. Can I edit in the "mobile view" preview? No, confusingly.)
    Another example: there's a long, empty space in one of the sections (about 1 screen tall) that appears in mobile view. Can I get it out? Nope.
    I trust that SS will fix these problems. In the meantime, it'd be nice if I could make a good-looking website using the old SS.
    Squarespace employees who might be reading this: you're putting your product at risk. You're gambling with your company.
×
×
  • Create New...

Squarespace Webinars

Free online sessions where you’ll learn the basics and refine your Squarespace skills.

Hire a Designer

Stand out online with the help of an experienced designer or developer.