Episode 4: Live website deployment, email capture setup, and

We deployed the website we designed in episode 2! It’s live! Go look!

The deployment took about 20 minutes and was honestly anticlimactic in the best way. I overprepared expecting a disaster. Bojana was mentally preparing for the worst episode yet. And then Claude just...did it. First try. We were both a little stunned.

I asked Claude Code to look through my laptop and tell me what I was missing to deploy the website. It downloaded everything for me: Vercel, GitHub identity, all the developer tools. It even handled switching our Substack domain to the new website domain AND set up automatic rerouting so no old links would break. I would not have even thought of that.

The whole prep took maybe 30 minutes in the background while I was doing other work. I literally just told it “I need to deploy this website live in front of an audience. How do I prepare? It’s high stakes.” Claude treated me the same way that the Bay area crowd treats someone who is non-technical. Overly slow, step by step, assuming you know nothing? Like that.

“Hey, I can’t type this because it’s your login. Can you go in and copy paste this into the terminal and click enter?” Yes, Claudia. Thank you.

If you’re a non-technical person dreading deployment: it’s fine. I promise. Just ask Claude Code what you need and it walks you through everything.

Bojana tested the email subscribe button live and it broke immediately. Some things never change. But I told Claude to fix it and it was working within a minute. It connects directly to our Substack so when someone subscribes on the website, they go straight into our Substack list.

We also asked the live audience to stress test it for us. Because why hire QA when you have LinkedIn Live attendees?

We set up the workflow that's going to save us every week. I take the LinkedIn Live transcript, upload it to the same Claude Code chat we've been using since we designed the website, and it writes a blog post for the site.

The blog is where we break down everything from the live step by step, so if you missed something or want to actually follow along and do it yourself, that's where you go.

This Substack is a safe place. It’s where we can both be creative and honest. Our website’s blog, on the other hand, is mostly there for the SEO play. So the strategy (for both content and SEO) will be different.

The blog can’t just pull the same text from Substack. Duplicate content is an SEO nightmare and Bojana will not allow it. She wants keyword-optimized URLs (not blog-episode-one, but something like building-a-content-repurposing-tool). She wants proper title tags. She wants the favicon and tab title fixed. She checked mobile responsiveness on the spot (it was responsive, shockingly). She also wants each blog post written in a real tone of voice, not “SEO article from 2015.”

We started out with the basics and will create a dedicated episode to developing an actual SEO strategy that goes beyond the “Make sure to optimize this for SEO” prompt (apologies to all SEO specialists for this).

Claude was still working on the first blog post when we ran out of time, but the workflow is set and we can now follow it weekly! And hopefully supercharge it with an actual agent soon (there may or may not be a Mac Mini delivery arriving at my house tomorrow 👀).

And yes, I decided to jump into the OpenClaw hype literally days before Anthropic announced their subscription plan won’t cover third-party tool usage anymore. Jump on trends early, besties.

Also, fun fact from last week’s Anthropic leak: when you curse at Claude or say mean things, it registers as a negative command. It KNOWS. So be nice. Bojana’s been saying please and thank you since day one. I have not. I’m reconsidering.

We had a few comments during the event asking where to begin as a non-technical person using Claude Code. Here’s what we said:

Just download it and start prompting. Use Terminal on Mac. Start with the Pro plan ($20/month). If something breaks, screenshot the error and paste it into Claude Chat in the browser. It will tell you what went wrong.

If you have workflows in ChatGPT from last year, ask ChatGPT to summarize what you do in that project, then take that summary to Claude Code and say “help me replicate this.” That way you’re not starting from zero.

Trial and error. That’s it. Eight out of ten times, Claude will surprise you by being able to do way more than you think.

- Vercel (the deployment platform we used for the website)

- Github (if you don’t have an account yet, make one! you’ll need it for everything you build with AI)

- Ben’s Bites (newsletter that did a great TLDR of the Anthropic code leak, and that I read every week for the past 3 years)

- Two girls, one Claude (it’s live! go break it for us)

This week, we’re covering Claude /skills! What they are, how to create them, how they’re different from just prompting Claude Code/Cowork, and which skills I use weekly for my agency work and life admin.

RSVP for the next LinkedIn Live!

---

*You’re getting this email because you RSVP’d for a Two Girls, One Claude LinkedIn Live or subscribed to our Substack. We send one email per week after each episode with a recap, the recording, and any resources we promised. Share with your friends!*