Remote CSS Delivery

Remote CSS Delivery

Remote CSS Delivery

How template CSS gets delivered remotely, and how to manage it yourself.

How template CSS gets delivered remotely, and how to manage it yourself.

How template CSS gets delivered remotely, and how to manage it yourself.

Applies to

Abode

Abode

Cove

Cove

Handshake

Handshake

Kintsugi

Kintsugi

Learnable

Learnable

Marigold

Marigold

Nautilus

Nautilus

Opponent

Opponent

Parable

Parable

Quantum

Quantum

Retrograde

Retrograde

Sidecar

Sidecar

Tandem

Tandem

Venture

Venture

How it works

In the latest template update where I updated and redesigned all templates in Fluid Engine, I also changed all template CSS to be remotely applied. This allows me to quickly make any changes to the core template's code in case Squarespace makes any updates that negatively affect your site. This means that your Custom CSS window will be mostly empty, except for some variables that allow you to control parts of the code without writing any of it.

Want to self-host your own template CSS? Follow this Template Doc.

What you may consider doing instead of self-hosting is simply pretending that the CSS I've added doesn't exist at all! You'd treat all code changes as if you're modifying the default site code—so instead of changing CSS that's already in the window, you'd add new code, but that's more specific to override what's in the imported code.

The main thing to remember is to make it more specific, and the best way is to add "body" before any declarations. For example, if you want to make the H1 red and all-caps:
body h1 {
color: red!important;
text-transform: uppercase!important;}

In the latest template update where I updated and redesigned all templates in Fluid Engine, I also changed all template CSS to be remotely applied. This allows me to quickly make any changes to the core template's code in case Squarespace makes any updates that negatively affect your site. This means that your Custom CSS window will be mostly empty, except for some variables that allow you to control parts of the code without writing any of it.

Want to self-host your own template CSS? Follow this Template Doc.

What you may consider doing instead of self-hosting is simply pretending that the CSS I've added doesn't exist at all! You'd treat all code changes as if you're modifying the default site code—so instead of changing CSS that's already in the window, you'd add new code, but that's more specific to override what's in the imported code.

The main thing to remember is to make it more specific, and the best way is to add "body" before any declarations. For example, if you want to make the H1 red and all-caps:
body h1 {
color: red!important;
text-transform: uppercase!important;}

In the latest template update where I updated and redesigned all templates in Fluid Engine, I also changed all template CSS to be remotely applied. This allows me to quickly make any changes to the core template's code in case Squarespace makes any updates that negatively affect your site. This means that your Custom CSS window will be mostly empty, except for some variables that allow you to control parts of the code without writing any of it.

Want to self-host your own template CSS? Follow this Template Doc.

What you may consider doing instead of self-hosting is simply pretending that the CSS I've added doesn't exist at all! You'd treat all code changes as if you're modifying the default site code—so instead of changing CSS that's already in the window, you'd add new code, but that's more specific to override what's in the imported code.

The main thing to remember is to make it more specific, and the best way is to add "body" before any declarations. For example, if you want to make the H1 red and all-caps:
body h1 {
color: red!important;
text-transform: uppercase!important;}

Still have a question?

Check out the FAQ page, or send a message via the Contact page.