This is a note for those who have joined our Slater early-release Slack channel. First, off thank you, it's great to see so many friends from Twitter. If we haven't met yet, I look forward to learning what you're building.
I know there's a lot to unpack from my tweet over the weekend. I'll get into the direction of EA in another post, but the gist is that we are pivoting to a product focus. Yes, we have been working towards this over the last ten years and consistently working on it for the last three years. Currently, we have four products in various stages, and Slater is the first one we are releasing into the world.
Slater is a coding environment specifically designed for Webflow. Our mission: Create a bridge for people from different backgrounds, whether they are a Webflow developer or a traditional developer. We believe that you can do more with Webflow with just a little bit of code.
Our roadmap will focus on a spectrum of technology capacities, from established JS developers to aspiring ones to beginners.
Advanced Developers
For established JavaScript developers, we understand the challenges of developing in Webflow. That's why we're solving for workflow and management with Slater. Today, our product includes:
Intermediate Developers
If you're an aspiring JavaScript developer (and aren't we all), we're currently in active development on a range of features, including:
Those Just Getting Started
If you're a beginner JavaScript developer, we have a range of offerings to help you develop your skills, including:
We are starting with building a community. We will do that in multiple ways, from our Slack channel to updates on EA Twitter to a video series to weekly email newsletters.
We're sending out surveys to better understand what everyone is working on, and we'll be reporting back. One of the big things we see is a lot of people are very interested in learning JS — so awesome!
Our first group of users will be the established JavaScript devs. Slater is a technical product, and we want to start where we have solved the bulk of these needs.
First, we don't have all the answers, and we will be learning with this community. We will share updates regularly, and some things we publish won't be totally polished. We've made the choice that we'd rather learn from something that's good enough than sit on something that might be great or total garbage.
More soon. Thank you.
– Mason