Read on Twitter
NEW PROJECT ANNOUNCEMENT 
Introducing @CookieSlayers: A crowdsourced platform showcasing products, services, and companies who aren't using third-party cookies
A #buildinpublic thread of what I'm building, why I'm creating it, and how I'm putting it all together.
THREAD
Inspired by @GitHub's decision to nuke all tracking cookies back in December of 2020, @CookieSlayers is a directory that amplifies products, services, and companies that have also taken a stand against third-party cookies that track us all over the web. https://fortune.com/2020/12/17/github-ceo-were-nuking-all-tracking-cookies-and-you-should-too/
The truth is that this is something I've been thinking about for a couple of years now. It hadn't made it to the top of my "Incubator" project list because I didn't think people would really care, but seeing people praise GitHub for the move made me realize it might be time now.
The conversation around tracking (and digital privacy rights as a whole) has been historically put on the back burner, but we're finally seeing it being put at the forefront, primarily by high-profile tech giants like Apple and Facebook.
https://www.forbes.com/sites/bernardmarr/2021/02/19/apple-vs-facebook--who-will-win-the-data-privacy-war/ 4/12 4/12
https://www.forbes.com/sites/bernardmarr/2021/02/19/apple-vs-facebook--who-will-win-the-data-privacy-war/ 4/12 4/12
My goal with @CookieSlayers is to contribute to that conversation and encourage people to become a "CookieSlayer," or someone who doesn't use tracking cookies.
By supporting CookieSlayers, we're supporting companies that don't rely on ads or dark business models to make money
By supporting CookieSlayers, we're supporting companies that don't rely on ads or dark business models to make money
CookieSlayers is not about being against cookies, but _tracking_ cookies specifically. Unnecessary cookies that collect as much information as possible with little to no justification for doing so.
This also means LESS (OR NO) COOKIE BANNERS
Because who likes cookie banners?
This also means LESS (OR NO) COOKIE BANNERS
Because who likes cookie banners?
If there are no tracking cookies, it means there's no need to display cookie banners. Simple as that.
As @natfriedman puts it: "âIt may be the world's best cookie banner. But it still sucks. Nobody wants to see it.â
Instead, let's focus on building products people love.
As @natfriedman puts it: "âIt may be the world's best cookie banner. But it still sucks. Nobody wants to see it.â
Instead, let's focus on building products people love.
âThe incentives all point toward people collecting more and more data, even if it's not that useful, because if it's basically free to collect and there's no penalties for collecting it or for misusing it.â
âJohn Bergmayer, Public Knowledge Project (internet advocacy nonprofit)
âJohn Bergmayer, Public Knowledge Project (internet advocacy nonprofit)
Okay, now that you got a good idea of the what & why behind @CookieSlayers, let's jump into the "how."
This is probably the part the #nocode fam is interested in the most.
Continuing
This is probably the part the #nocode fam is interested in the most.
Continuing
Since @CookieSlayers is a directory/listing type of site, I knew the database would have to be easily maintainable. With so many sites on the internet, and an increased interest in digital privacy rights, this would be crucial as the db grows.
With it being crowdsourced, I also wanted to make it as easy as possible to submit new CookieSlayers, ideally in a form-like fashion that would get sent somewhere for review, or directly added to the database assuming it passed some data validation.
Requirements so far:
âą Easy way to manage lots of listings (i.e. CookieSlayers)
âą Easy entry submission to add new listings in a form-like fashion
Enter @Airtable. A popular #nocode tool, Airtable meets these requirements.
Got my database sorted out.
âą Easy way to manage lots of listings (i.e. CookieSlayers)
âą Easy entry submission to add new listings in a form-like fashion
Enter @Airtable. A popular #nocode tool, Airtable meets these requirements.
Got my database sorted out.
For the frontend:
Given it's a directory/resource type of site, we really don't need anything fancy. In fact, it'd be better to use prefab components instead of designing everything from scratch. Not only would it make it easier to launch quickly, would also unify the db design.
Given it's a directory/resource type of site, we really don't need anything fancy. In fact, it'd be better to use prefab components instead of designing everything from scratch. Not only would it make it easier to launch quickly, would also unify the db design.
Enter @softr_io.
Softr literally uses Airtable as the database, so the pieces were falling together easily.
Side note: I had planned on using Softr for my next build anyways, so it seemed like a perfectly logical next step. https://twitter.com/hiramfromthechi/status/1367917865173716995?s=21
Softr literally uses Airtable as the database, so the pieces were falling together easily.
Side note: I had planned on using Softr for my next build anyways, so it seemed like a perfectly logical next step. https://twitter.com/hiramfromthechi/status/1367917865173716995?s=21
Time to start building.
First things first: Let's structure the Airtable db and populate it a bit. Didn't wanna be working with empty datasets while building, because I wanted to be able to see what it would actually look like once it had a decent amount of @CookieSlayers in it.
First things first: Let's structure the Airtable db and populate it a bit. Didn't wanna be working with empty datasets while building, because I wanted to be able to see what it would actually look like once it had a decent amount of @CookieSlayers in it.
Starting simple, with the name, logo, URL, and a description of the product/service/organization.
Then I jumped into Softr and started building the hero section for the homepage.
I'm gonna keep playing around with the copy for this.
Then I jumped into Softr and started building the hero section for the homepage.
I'm gonna keep playing around with the copy for this.
Made the CTA from the hero section to be an explore/view all type of CTA so that users could easily jump to exploring some @CookieSlayers and not be worried about having to pay or sign up or anything like that.
Now to add some "testimonials" to the site.
Not that they're testimonials in the traditional sense of reviewing @CookieSlayers itself, but rather public quotes about the importance of digital rights, privacy, and cookies overall.
Not that they're testimonials in the traditional sense of reviewing @CookieSlayers itself, but rather public quotes about the importance of digital rights, privacy, and cookies overall.
Perhaps one day someone of influence will actually say something about @CookieSlayers that I can add to the site.
P.S. I wanna diversify this panel, so if you know of any other quotes that would be good to add here, email me at hello [at] cookieslayers [dot] com.
P.S. I wanna diversify this panel, so if you know of any other quotes that would be good to add here, email me at hello [at] cookieslayers [dot] com.
In the last section of the homepage, I created a primary CTA regarding submission of another CookieSlayer.
The primary CTA is always in the header (submit a CookieSlayer), but when a user has scrolled all the way to the bottom, it's good to place another reminder to take action.
The primary CTA is always in the header (submit a CookieSlayer), but when a user has scrolled all the way to the bottom, it's good to place another reminder to take action.
That's a wrap for this thread, more on 
