Comments URL: https://news.ycombinator.com/item?id=21474129

Points: 6

# Comments: 4

It's true that certain blocks still use YUI, but this is system functionality that's not part of our public API. In new templates, a Squarespace developer won't see or touch YUI code.

We're no longer creating new features with YUI. We write new frontend editor functionality with modern libraries like React.

> Why would a developer want to see a cached version of a page?

Squarespace is a CMS. There's an online content editor where users can add text and images. The content is rendered using a template which contains the HTML/CSS/Template code that defines the layout for the content. The squarespace dev server makes it easier for the developer to work on the template code using content from the live site. I don't think you'd run into a situation where it looked fine locally but broke in production, because the content will be the same.

> why not just make it a portable executable for each platform

NPM has great cross-platform support, and it's used by lots of web developers. That's why we chose NPM. It allowed us to build a cross-platform tool without having to maintain lots of separate installers for various platforms.

Also we wanted to take advantage of the same java based template and less compilers that we use in production (that are open source), which is a large part of why we used java. I'll admit it's not a natural choice for an NPM package, but it's working well for us so far.

I spent years building tools for this market between professional devs and non-developers. (Backlift.com and then Brace.io) It's really tough. Most people learning to code are trying to gain transferrable skills that can help them land a job. For them, learning git is a fruitful tangent along the path to shipping. Those that aren't interested in building those transferrable skills probably don't self-identify as developers. Making developer tools for non-developers is tough.

If you want to check a company's status, just go to the website. This seems like a cynical tool.

Want to send feedback? There's a form at the bottom of formspree.io and we've got people in the community that are now responding to those customer service inquiries.

Several have asked about the 10m delays. We switched email providers so we could improve our email deliverability and spam filtering. But the new provider is throttling us while they get a sense of our email traffic. I've been told that it should be back to normal soon. These are growing pains.

Frankly I'm pleasantly surprised to see the project gaining momentum. The alternative would have been to shut it down.

Comments URL: https://news.ycombinator.com/item?id=7965652

Points: 75

# Comments: 26

Most DNS hosts offer some mechanism for forwarding traffic from your apex domain to the www subdomain using a 301 (permanent) redirect. Then the www subdomain can be configured with a CNAME record.

For example, at Brace (http://brace.io) we offer a guide for configuring this if your domain is on godaddy. See step 3 at http://blog.brace.io/2014/01/19/custom-domains-godaddy/. (not an endorsement of godaddy)

(edited for clarity)

Here are a few resources from our blog that explain the www redirect approach:

- http://blog.brace.io/2014/01/17/cnames-aliases/#cnameconfig

- http://blog.brace.io/2014/01/19/custom-domains-godaddy/ (step 3)

(edited: added resources)