Hey Slater Squad 👋
Alright - let's go!
Client Transfers & More
Thanks for all your feedback over the last few weeks. We've been busy making some updates based on your feedback!
We'll be doing a livestream this coming Wednesday, 10am EDT to go through these changes - a lot of updates here!
Give your clients control of their code and who has access to it. You can trigger the transfer to give your client control and still retain the ability to update code for as long as you need.
2) Add/remove collaborators from your team.
3) Public file urls are now fully public.
You don’t need to have an account to view code.
4) Cache busting support.
Add a version number to your Slater script anytime you need to ensure your users get your latest code.
5) Improved error handling.
This is most apparent when having issues saving your files to Production.
6) UI improvements.
7) Fixes and improvements to the Webflow Designer App
8) Improved the single script compilation.
We will be going through all these updates on Wednesday 10am EDT during a live session but we'll update you shortly on timings.
Come along on Wednesday 10am EDT to hear more
Why Use Slater?
A few days ago, someone messaged me this exact question.
People are clearly still unsure wtf Slater is and why it's a cheeky tool for any Webflower doing custom code.
So, Witt and I want to show you the following:
1) Why use custom code in Webflow?
2) Why use Slater?
3) How to use Slater
Thomas Carré Website
Thomas Carré is a creative developer that makes funkalicious websites (seriously - check out his portfolio here to see what I'm on about).
We'll be doing a live session this week on how he built this website and how he's using Slater generally.
TBC on timing but stay tuned on Twitter to see when the event will be!
That's all for this week folks!
See you soon,