Stain the Page: How I Prototype with AI

Stain the Page: How I Prototype with AI

Hannah Tipperman

AI is incredible for rapid idea and hypothesis testing by prototyping. It isn't about writing code — it’s about protecting your most valuable resource: cognitive energy. As engineers, we often face the overwhelming task of determining the look, feel, and architecture of an idea through hundreds of tiny decisions. By the time we get to the novel part of the problem we’re trying to solve, our brains are tired. We can burn out before we even truly begin.

To solve this, we can steal a trick from artists and writers.

How To Use Standard HTML Video & Audio Lazy-Loading on the Web Today

How To Use Standard HTML Video & Audio Lazy-Loading on the Web Today

Scott Jehl

HTML video and audio lazy loading is now a web standard and quickly gaining support in all major browsers. Given Squarespace’s role in proposing and implementing it, we’re very excited to see how developers use it on the web. Let’s cover some best practices for using video and audio lazy loading in any website, as well as some gotchas to avoid.

Squarespace & Web Standards: How We Helped Bring HTML Video & Audio Lazy Loading to Today’s Browsers

Squarespace & Web Standards: How We Helped Bring HTML Video & Audio Lazy Loading to Today’s Browsers

Scott Jehl

At Squarespace, many of our core products are built on web standards, and our engineers are constantly pushing the boundaries of the web’s capabilities. Occasionally, those boundaries reveal a limitation: an opportunity for the web’s native capabilities to grow. This post is the story of how we found such an opportunity to work with the standards community to improve the web in a way that we – and everyone who uses it – can benefit.

Unfold's Modern Mobile Release Process and the Subtle Art of Making Them Boring

Unfold's Modern Mobile Release Process and the Subtle Art of Making Them Boring

Alan Cooke

On the Unfold team at Squarespace, our mobile releases don't require much in the way of manual intervention or human oversight. In fact, we don’t have to give releases much thought at all.

But, this was not always true. This post is a look into what these non-eventful mobile releases are like, dig into how much more eventful they used to be, and walk through the work it took us to get here.

Outro: What You Did and What’s Next

Outro: What You Did and What’s Next

Anila Zaidi

The outro recaps what you did – write technical documentation! – and introduces next steps like organizing a collection of documentation, revising existing content, and expanding your technical writing skills by joining the technical writing community.

Part 4: Test, Edit, And Publish Content

Part 4: Test, Edit, And Publish Content

Anila Zaidi

After completing Parts 1, 2, and 3 of this tutorial, your once blank page now has technical writing – you're officially in the home stretch! Technical writing on a page becomes technical documentation only after you test, edit, and publish the content.

Do not underestimate the exponential payoff that comes from testing and revising content. More than one technical writer can claim that revision has either uncovered bugs in software or improved it.

Part 3: Draft Content That’s Accurate, Consistent, And Concise

Part 3: Draft Content That’s Accurate, Consistent, And Concise

Anila Zaidi

In my opinion, creating good headings and organizing them in a way that’s helpful to readers is much more challenging than drafting content. So pat yourself on the back for completing Part 2 of this series and making it to Part 3. 👏 👏 👏

However, there are three things that undo exceptional headings and structure in technical documentation: content that is inaccurate, content that’s inconsistent, and content that’s inflated.

Part 2: Use Good Headings For Structure And Scanning

Part 2: Use Good Headings For Structure And Scanning

Anila Zaidi

Part 1 of this tutorial introduced you to the content types that are most common in technical documentation. You also evaluated a real-life example as a reader, and you may have realized how headings are essential to a good reader experience. It’s because readers on the web do not read – they scan¹ . People actually read 25% slower on the web² and they only read 20% of the content on a page³. (This data is from 2008; I’m scared to know the percentage today.)

Load More