brusselsprouts

Hi, all - wondering if it's possible to display tags for a blog post in addition to/separately from other metadata (e.g. category, date), and elsewhere on the page. Context: I'm using the Brine template. Under "Site Styles," you can set "primary" and "secondary" metadata to display on any given post — and you can only display two metadata types. By default, those two pieces of metadata display under the blog post title, as below (here, I'm displaying Categories and Date). Question: What I'm wondering is — is it possible to, in addition to the "Primary" and "Secondary" metadata you can set in Site Styles, display a third metadata type (e.g. tags), elsewhere on the page (e.g. at the bottom of the post)? I'd love to be able to have a display at the bottom of a post, near the previous/next links and social share buttons, that lists the post tags (e.g. Tagged under: Thing 1, Thing 2, Thing 3). Is it possible?

Hi, folks - I'm building a site using a Brine child theme. I wanted to make my folder links in my topline nav link to pages (which should be easy to do!) and found that several folks had crafted solutions to this, so that's great! I went with the simple HTML workaround described here, and it's working great. However: I then noticed that on mobile, the folders I've added links to don't expand — they just go to the page I've linked to. (For example: say I have a folder called "Projects." I renamed that folder < a href="/projects" > Projects < /a > ...so that it now links to my "all projects" landing page. On desktop, a user could either mouse over "Projects" to see a list of projects, or click on "Projects" to go to that landing page. However, on mobile, the user can only tap "Projects," which takes you straight to the landing page, and doesn't allow you to see the list of projects that appear in the dropdown on desktop.) My question, then: is there a workaround to make a folder link on desktop but NOT on mobile? I know there are some Javascript-based solutions to the "add a link to your folder" issue (e.g. https://answers.squarespace.com/questions/23951/can-i-link-a-folder-to-a-specific-page.html). Since, well, I'm a complete Javascript noob: is there anything like a @media query for JS? i.e. could I modify that script to say, "if we're collapsed for mobile view, no link!" — or might there be any other ways to address this? Thanks, all!

I'm a freelance designer/developer who's still learning some of the ropes. I'm fairly experienced with Wordpress (but still have lots to learn there too!) but am currently working with a client to redesign their Squarespace site. I've learned that unlike with Wordpress or Drupal, there's no support to create a staging site in Squarespace to make major changes without changing (and potentially breaking) the live site. From browsing this forum, I know I'm not the only one who finds that frustrating. Anyway: my client has an existing Squarespace site, and they want a thoroughly redesigned site, also in Squarespace. They'll need a new template, of course, but also some new content (I'm working with them to create some new landing pages), and a completely reorganized navigation structure. Given that, and given Squarespace's limitations for developers, my question is: does it make more sense / is it more of a best practice to: (a) develop the new template design using a different trial site and/or the local development server (which I've played with a little bit), duplicating or creating new individual pages, and then, when it's time to go live, putting a cover page up and doing everything else on the live site while it's down? (like what's described here: https://answers.squarespace.com/questions/67379/how-can-i-redesign-a-clients-site-without-going-live.html) I'm concerned this would put my client's live site down for a while, so I can test everything * with their content * and get their feedback. And it just... feels scary, and kind of insane, compared to how I'd do it in WP, you know? OR, (b) clone all their content, e.g. using the imperfect-but-doable export to WP > export back from WP to SS workaround, developing the redesign on the clone site, and then, when it's time to go live, switching the client's domain to point to the live site? This mostly seems like the safer option, and this is where I'm leaning, but I'm worried I'll end up spending a lot of time spot-checking content, re-uploading blog posts' thumbnail images manually, etc. (And, reader, they have a lot of blog posts.) And it feels like there should be a better way??? OR is there a more sane © that I haven't learned about yet? tl;dr do I need to use clunky import/export workarounds to create a clone site in order to develop a redesign for a client without breaking their live site, or is there a better way? I tried to convince them to move to WP, but it didn't work, so now I'm here. Any guidance appreciated!