
The 404 before launch — getting the site live
2:05The privacy policy URL 404s, which means the site isn't actually deployed. Fixing it, and how Netlify redeploys off a connected GitHub repo on every change.
Transcript preview
Leave it on none, fill the two, ok. This is... ahh. Claude can be a little dumb, I'm telling you. Just two minutes ago I was appreciating it. It's alright by the way, you know. I don't think it's able to control that. Another issue, ahh, ahh, ok. So category is fine, bigger problem just found it now, returns 404, ok. So I think this is not live yet. Can you deploy it please? So deploying basically works directly for me. And for Netlify you will have to make sure you have a GitHub repository connected. Which on any change can deploy. I think Netlify you can just ask Claude, not think, we just did, right. We deployed from scratch. So if you make any changes locally it should be able to deploy that as well. So not a big issue. Let's just wait for it to be deployed. Meanwhile I'm just going to make sure I provide these properly and save that again. Because I don't think it was saved previously. That is done. Distribution, fee of charge, public, ahh, public. Privacy, we have few things which we need to do. So I'm going to just take a screenshot.…
The full lesson — video and transcript — is part of Vibe Coding.
Get Vibe Coding →