Vibe Coding mudou minha maneira de construir sites - DVC004

Author: Promovaweb Automação e IA · Watch on YouTube

Video authored by the channel shown, not by IANIA; all rights belong to the creator. Transcript and summary generated automatically; the original-language content is preserved.

Original language: English

Original video: Vibe Coding mudou minha maneira de construir sites - DVC004 · Channel: Promovaweb Automação e IA · 20:38 · Watch on YouTube

Topics: AI agents, Software engineering with AI, Open source and software ecosystems

Summary

The speaker describes migrating a company website from WordPress to Astro and argues that the main difference is not the underlying technology but the more flexible, AI-assisted workflow. Agents and scripts can migrate content, build and refine pages, automate tasks such as SEO and responsiveness, and deploy the site with less manual setup. He suggests WordPress can still serve as a backend through its API, while Astro may suit people who want to build and maintain their own frontend. He encourages viewers to try Astro and frames the choice as a matter of workflow and fit rather than declaring WordPress obsolete.

Key points

The speaker is migrating a WordPress site with more than 200 posts and around 25 pages to Astro.
He says AI agents can retrieve and clean WordPress content, turning it into Markdown as part of the migration.
His central argument is that the appeal lies in the workflow, not simply in switching from PHP or WordPress to another technology.
Astro, Tailwind, command-line tools, and AI agents offer a workflow he considers more adaptable and automated.
A headless approach can retain WordPress for writing and managing content while Astro builds the frontend using the WordPress API.
He says users who need a familiar editing interface may still need a CMS such as WordPress or an editor such as Decap.
The speaker describes using skills and agents for tasks including page speed, SEO, link building, content editing, and responsive testing.
He advises people who are satisfied with their current WordPress workflow that they do not need to migrate, while suggesting Astro may appeal to people starting from scratch.

Chapters

Start	Chapter	Summary
00:01	Why some users are moving away from WordPress	The speaker introduces a WordPress-to-Astro migration and describes how AI-assisted site building is changing some users’ expectations of website workflows.
03:18	Automating the migration and building process	He explains how agents can deploy a site and migrate WordPress posts and pages, and argues that the shift is primarily about workflow.
06:02	Astro skills, agents, and headless WordPress	The speaker describes automated Astro tools and explains that WordPress can remain in use as a backend while Astro serves the frontend.
09:25	Editors, decoupled architecture, and practical use	He discusses editorial interfaces, the separation of frontend and backend, and how his own site-building work led him to offer migration services.
12:06	Content automation and a different development experience	The speaker shares examples of automating content and site features, then emphasizes the flexibility of building with Astro rather than relying on a traditional plugin workflow.
16:54	Who should try Astro and how to get started	He recommends that people choose based on their needs, invites viewers to experiment with Astro, and closes with details about training and community programs.

Quotes

It’s this process that has changed. — 03:48

But it’s undeniable that this workflow is outdated — 07:43

I think you should consider using WordPress as a backend for Astro. — 08:50

it’s the flow, it’s this experience I’m having of having a freedom I never had to build a site. — 15:52

I switched from plugins to skills and it’s a new life — 17:26

Concepts and entities

Astro, WordPress, Headless WordPress, Claude, Codex, Cloudflare Pages, Tailwind, Decap, GitHub Codespaces, Promov

Full transcript (original language)

00:01 Hey everyone, how’s it going? I’ve got a job here to migrate a website from WordPress to Astro, you know? So, I’m already halfway through it. I want to share a bit of my journey with you, and later I’ll make another video with more details on the nitty-gritty, okay folks ? First off, guys, there’s a migration movement happening away from WordPress. I’m not sure why, honestly. WordPress is a stable platform; many people have had sites on it for years and have

00:33 great success with it. But I’ve noticed that “Vibe Coding” and people who are skilled at manipulating an agent, manipulating Cursor—be it Desktop or Cloud—end up opting for that level of control. Do you know what I hear the most, guys? When someone comes to me for a consultation on Vibe Coding, or even marketing, it’s about their website. Because WordPress helped us

01:04 out for a long time. You didn’t need to know design or programming, you could build a landing page, do it your own way, or even buy a ready-made template and import it; it had its ways of helping us out. When Vibe Coding arrived, letting me reach a different grade of work, a new level, it seems like WordPress lost its appeal for a good portion of the folks I assist here . I know I live in a bubble, the dev and entrepreneur bubble, but

01:38 entrepreneurs have less patience for hiring a server, setting it up, choosing a theme, or picking a plugin. It feels like, guys, that it’s a business, like I’m wasting time doing that. And look, I’ve heard this twice now and it surprised me; I said: “Guys, we’ve been doing this for 20 years, right?” It’s the most standard, most common thing to open a theme store, find a theme I like, and be able to visualize my website there, right? And the same goes for plugins, right? For Elementor, a security plugin, a backup

02:10 plugin. This is all routine, but it feels like I’m falling behind, like it’s a waste of time to do this. And this is really funny, guys. It’s really funny because I know that’s not the case, right? I know that’s not the case here, but a lot of people are on this wave of creating with Visual Code and literally want to take a screenshot, put it into Claude, into Codex, and say : “Hey, I want the site to look like this”; they don’t even bother buying a template anymore. And when you look at WordPress, which has its MCP, it has

02:44 WordPress Studio, it has the option to use AI for it, you have Elementor which now also has all these AI features, but when you look at Astro, which is basically React, right? Claude and Codex will chew through that and give me perfect code. I’ll have Tailwind, which gives me countless possibilities to build a design, right, utility-first , the way it’s meant to work, you know? So, you notice that these folks are choosing to go down this path and WordPress has become a problem, because I can’t work like that with WordPress;

03:18 I mean, I could, but the process is different. Because, guys, look, Cloudflare just launched Cloudflare, Cle Cloudflare Pages; it’s still well-documented that the support is a bit problematic, but in a week or two, they’ll sort that out. Once I have Cloudflare, I’ll just go there and ask Claude, “Claude, look, use the CF command, and deploy my site here to my Cloudflare account.” It’s over, folks. It’s over, because you build it here,

03:48 compile it here, and publish it there. Done, right? And that’s when you’re not sending it to compile there; you can actually have it compile directly on Cloudflare so it doesn’t even take up your machine’s memory. It’s this process that has changed. So, it’s not a matter of the technology itself, PHP, or WordPress, that’s not it, right? It’s a matter of workflow. Me being able to take a screenshot, or take some text; I’m building a site here, I’m converting a company’s site. A company asked me to convert their site from

04:19 WordPress to Astro and I told it to browse it. Guys, there are over 200 posts, and I think there are 25 pages. It did all that in less than an hour. In less than an hour, it grabbed all the posts, went to the WordPress API, compared what it grabbed with what’s in the API, and cleaned up the tags, because WordPress is very messy when it comes to HTML. It’s plugin upon plugin, upon plugin. It’s div, div, div, div, so it’s dense code to be processed. But it went there, grabbed it easily, worked very well, and gave me a clean

04:51 text, a wonderful little Markdown file. Folks, that’s a whole different life, right? It’s another level of work, it’s a different way of doing things. I think many people are becoming enchanted with the method, not the tool itself. Because when I look at the WordPress community—and folks, this isn’t a criticism, okay? There’s a great disdain for the Jamstack, right? For this way of building sites with JavaScript, with some framework, with Tailwind, putting the Markdowns there to serve as the post database. There is

05:28 a lot of prejudice regarding that, folks. They literally ignore the fact of doing it that way. But look, I have my doubts. If you take a willing person and say, “Hey, let’s take tomorrow, a Saturday morning, and build this site with everything WordPress has to offer technologically today in the world of AI.” And let’s take Astro here, nice and simple. Let’s take a blank theme, blank in WordPress, blank in Astro, and let’s build the site, the same page, let’s use the same reference. I doubt, folks, that a willing person wouldn’t

06:02 say: “Man, Luis, this workflow is much cooler to work with; it’s not better or worse, okay folks?” It’s more adaptable , it’s more practical. I run it on the CLI, I run it on the desktop, I run it on the local server, I don’t have to subscribe to anything, I don’t have to buy anything, I don’t need a server, I don’t have to worry about cache, cache plugins, none of that. It’s all automatic, ready to go. Look, I have a framework here that I teach in my classes, a framework for Astro. There are over 100 skills in this framework. They aren’t invoked automatically. You can invoke them explicitly, but there’s

06:37 a skill for page speed, a skill for SEO , link building, everything, folks, that you can imagine, that takes care of the footer, the header, the menus, that handles responsiveness. And, wow, it does so much, folks, in a highly automated flow, because one skill calls another, which calls another, which calls another, the work is done and it launches a subagent here, a subagent there. I run two or three agents on the same site here using Herder, working in different areas, constantly compiling the site, linting, formatting,

07:10 componentizing, and optimizing to generate the purest possible HTML for the front end, with as little CSS as possible, avoiding that div bloat, nothing like that. So, I think anyone with a little bit of an open mind is feeling the same thing I am, guys: “Man , doing this is a whole new life.” Next year, I’ll hit 20 years of WordPress, right? And I want to tell you, guys, I don’t like to go around saying, “Oh, the technology is dead, the technology is over.” That’s not my style, that’s not it. There’s a crowd that will

07:43 stick with WordPress their whole lives, we understand that; it’s their workflow , right? But it’s undeniable that this workflow is outdated, right? That this workflow isn’t how we’re building things today, right? It’s undeniable, guys. I can take the OpenAI bot here and ask it. You can ask the Grok bot, “ Hey, check my repository, do this and that, and push it.” It actually does it , guys, because the process is highly automated and connected to things. I

08:17 can open GitHub, start a GitHub Codespace, and make a total change to my site right there online in the browser. So, that’s it; it’s this workflow that I think many people in the WordPress universe haven’t realized yet, that there is another alternative. And that, guys, is because I don’t even need to discard WordPress. I’m migrating the site here, querying the WordPress API the whole time. So, it is perfectly possible to build a site using WordPress. We call it Headless WordPress, right? Look, this headless

08:50 mode has been around for quite a while now, right? And I think it’s a good approach. No, I see no reason to remove WordPress, to throw WordPress out; I don’t see any reason for that, right? In fact, I think you should consider using WordPress as a backend for Astro. The switch to Astro is very drastic. The audience using Astro today is you, the entrepreneur who is already into vibe coding, already building some system, and you’ve gotten used to working this way; it will fit perfectly into your workflow. Now, folks, the

09:25 editor, right? In my case, look, for many years we had an editor there, but this guy isn’t going to use it, folks, it’s hard for him. There is Decap, right? I’ll even make a video with you about Decap. You run it locally here or on the web, a dashboard very similar to WordPress, just so you have an interface. So you still keep running your site locally on your machine, right? You build the whole thing, it saves to a database—which can be any type of database, even an SQLite file right there on the machine, even better

09:57 , so it commits and puts it in the repository all set. Look, it’s a different workflow. And I felt this firsthand because I built the Promov site, folks, but let’s just say, I built the Promov one from scratch and I was building it very gradually, right? It was very gradual, it was with the little time I had available to work on it. I was much more focused on working on the system, the LMS, than on the site itself. So I didn’t, maybe I didn’t notice that change. Now that I’ve taken it on, I have Devil Side Studio here, where I can provide migration, startup, and maintenance

10:30 services for you. When I said that, André came along and said: “Luiz, will you migrate the site for me?” I said: “ Man, let’s migrate it, let’s set up that project.” The first stage, a complete migration to leave WordPress and move to Astro. The second stage is a redesign of the site. It’s a different life, folks. It’s another, it’s something else. And again, okay, guys? It’s not for everyone. Someone will show up in the comments saying: “ Gee, Luiz, but I won’t be able to edit the post.” You won’t, folks. It’s not for that user. For that guy, you’ll have to give him a backend, you’ll have to give him a CMS. Keep using WordPress with him, but today I no

11:04 longer see a reason not to use a technology like this for the frontend. Okay? So, understand what decoupled means. I have two situations here. One thing happens on the frontend, another thing is the backend. I prefer to use everything together, but you can definitely use WordPress, keep writing posts in WordPress, pages in WordPress, creating your custom post types there normally, normally. You just won’t use Elementor, you won’t use those types of visual plugins, you won’t have a theme to manage. I will access your WordPress

11:36 via API. I will build it here at build time. I’ll assemble the entire site with all the posts and pages that I’ll fetch from your WordPress. So it is possible to keep WordPress in the mix, but I don’t think the front end looks good there anymore. And I’m feeling this firsthand, guys. I said, I just finished my shift, and I thought: “Man, I’m going to tell everyone about this because I’m really excited about it.” Excited because, again, my Promov site is a very unique case. I didn’t realize that, right? That’s where I’ll make a

12:06 video for you showing everything I have , okay? It’s not open source, is it? It’s my site, I didn’t make it open source. There’s a lot of my information there, some strategic things too, but look, I automate 80%of it. 80%of it is a lot, guys, it’s a lot to be able to have the flexibility to open my Codex. I use Codex for everything. I asked Codex, look, go to the cloud, take the meeting I had this morning, I touched on a subject there, I want to create a post about it. And five minutes later, the text is written, it has already

12:40 found a thumbnail for me on Unsplash, placed it, cropped the images, launched it, and pulled a glossary from it, right? We now have a large glossary on the site, guys. It already did the link building, it’s something else. Saved that to my collection, sent it to my hub so it can now be part of my knowledge base, it’s a whole new life, right? So it’s not that I can’t do it in WordPress, but I can’t do it this way. WordPress will have its own way of doing things, and that’s fine. And again, okay guys? Many people will use

13:12 it—I don’t see it as “Oh, WordPress is going to die.” Look, I’d bet it won’t lose even half, less than half will want to leave WordPress, but the half that does leave, the people who leave WordPress, it’s because they saw this new workflow. We had this same movement with NHN. It reached a point where she said: “Luiz, I’m ready to leave this environment here, you know, on the tracks, this closed-off environment.” And now I’ve come to Vibe Coding. I’ve come to build my own solution, no longer on top of

13:44 WordPress or on a CMS, but on my own code, a base that I will maintain, you know? I have the team leaving the studio because of this. We have the Vibe Code course at Promov because of this, and the founders ’program, for us to talk about business, sales, and all of that. So, we built these products based on that to help you in your day-to-day. Because many people have moved away from the reality of having a base, a framework, or a system to build upon, to having their own, without dependencies, without a vendor

14:17 providing…no, I no longer have WordPress giving me a structure; I am building the structure. This site I’m building, folks, it has so many JSON files with settings, crucial information, price tables, terms, all of that makes up the site. In WordPress , you have to open a panel, find the page, click edit, and then click save. Not there; the agent chews through it very quickly to change a price table. I have a CSV file with over 500 lines

14:48 that creates a wonderful table, right? But man, I keep imagining how I would build this in WordPress, how I would generate that table in WordPress, right ? The Promov glossary is an example. How would I build that glossary? Working that way, with a well-crafted layout, link building, and content in a post; when it sees there’s an entry for that term, it creates a link, it

15:18 relates that post to that entry, and I have all of that, a graph of it all. Guys, it’s something else, it’s wonderful. So, I think I really considered at the beginning that it was going to be a technology issue. I left PHP and came to TypeScript to build things in Astro, but it’s not about PHP, it’s not about not having a server or being serverless, it’s not about that. That’s important too, folks, okay? But that’s not it;

15:52 it’s the flow, it’s this experience I’m having of having a freedom I never had to build a site. I never had. Look, guys, I’m from the era before WordPress when we used to build sites in Dreamweaver using HTML, right? Still , it’s comparable, of course, right? In Dreamweaver, I had a template, it was pretty cool working inside it there, right? But it’s more or less what we do with Astro today, only much faster, much more powerful, much better looking , much more practical. I can work on responsiveness exactly the way I want.

16:23 Wow, it’s a whole different thing, guys . I have a foldable phone here. Wow, I have to make it compatible with a regular phone, a foldable phone, a tablet, a low-resolution computer, and a high-resolution computer. It’s great, I have a skill that does this for me. It takes a screenshot, checks, monitors , and controls how it was before and how it is now. I have a little robot there that does this all the time, right? So it is, it’s a different thing , guys. Wow, it’s a whole new life. I think what WordPress will have to work

16:54 on in the coming months is the workflow . Whoever is comfortable with their current workflow, keep going. Certainly keep going. There’s no reason to migrate, I think. But for you starting from scratch, you who are entering the market now, “Hey Luiz, I’m going to have my first site.” Certainly, the Astro workflow is much more attractive, much more practical. Companies are increasingly going down this path, rather than a WordPress workflow, which has a server, a bunch of plugins, you have to choose a theme, you have to

17:26 optimize, and there’s a plugin that optimizes, a plugin that does links, a plugin that checks links, a plugin that …Nobody can take that anymore, right, guys? I, I, I got tired of that, right? And it’s precisely that, right? I switched from plugins to skills and it’s a new life, a different thing, I don’t need to buy anything. I build my own whenever I want here, right? And I have so many, I even joke about it, right? Just like the fridge from the Dinosaurs family, right? When you open it, a bunch of little hands come out, right? Skills are exactly like that, okay? At any given moment, a skill is handling a specific part. Check the link here, check the link there, check

17:57 a field here, check…Wow, everything. Do it in the text, correct the text, remove the slop from the text, wow, it does everything. So, I think that’s it, right? Sharing my experience with you here, what I, after working here yesterday and all day today with this, I leave, you know, finishing this stage of the site, I leave with this conclusion. The workflow is dictating it to me, right? The workflow is much friendlier. For me to pass this on to André, for André to be able to continue, it will be much more practical for him to do it from his

18:30 phone, from his computer. I have Walmart here, where where I work, right ? Or I work at Walmart, right? I create content on Macs, but I work with Walmart. It’s a whole different thing, guys. It’s a whole different thing. It stays open here the whole time. This isn’t even André’s site, it’s another site I’m also building. But it’s really cool, guys. It’s really cool. Give Astro a chance, do a lab. For you who are a Promov student, we are in the middle of recording the Astro course. It will be six classes, right? We are, we recorded the third, we’re going to, we’re going to the fourth class, right?

19:00 I’m showing how you take a theme, how you get to know its guts, how you write content, do the design, mess with the colors, understand the collections you can have of information that you can use on the site. We’ll be deploying this site in a little bit, which isn’t hard to do, but there are some tricks to host a site over on Cloudflare, right? So, for you who are a student, there’s material, okay guys? There’s material, short, quick immersion. so you can quickly get your site online. I have a student here who hasn’t even

19:33 finished the immersion yet and is already putting their site online, right? Because it’s a very different workflow, okay guys? Watch the immersion with that perspective. I’m showing you not just the technology, but the workflow, which is totally different and it’s top-notch, guys, it’s really cool. Like the video, subscribe to the channel, and comment on what you thought of our chat about Astro, right? Don’t forget to scan the QR codes that appear on the screen so you can hire Devside Studio or Founders , which is your new training program, with enrollment open. Call Diavan there

20:06 to introduce you. I am sure that you will greatly accelerate your projects and get them off the ground. You will be accompanied by people who are creating and launching things as well. It is not a gathering for people who are just thinking about doing something . The idea of the Founders is for the person who is ready to take action, right? Look, Luís, I am ready, man. I just want to validate, I want to hear from you, I want your help, I want to talk to the group here so we can get this project started, right? There is

20:38 always someone to help, always someone in the community willing to give you feedback, to sign up for your system, and to use it once you show it. It is really cool, guys! It is not a programming course, it is a business course. At Founders, we talk about business, okay? So, if you are building a SaaS, an agent, or a system, come to Founders; I am sure you will really enjoy this chat, learn a lot, and gain many insights to apply to your system. Best regards, everyone. See you next time.