WordPressBuilder ai: WordPress, passet af AI

Ana: Why isn't anything happening yet? Hanne: Because it asks me first. Searching WordPress for the right setting? That takes time. With WordPressBuilder, describe the change – our AI Kenji plans it for you. Type the change, “Plan” – read Kenji's plan; only “Run” carries it out. Hanne: With your coffee, I'd rather ask too. Your words, Kenji's plan, your yes. Hanne: This attempt had better stay here. Hanne: I'll do the same with the website. Tried a change on the live site – and it broke? WordPressBuilder gives you a sandbox – a copy of your site to try things in. In the sandbox, the menu is now in capitals – the live site is still unchanged. On the sandbox, “Restore …”, then “Files only (recommended)” – your tested files go live. Hanne: Not every attempt has to go in the shop window. Test in the sandbox. Go live when it's right. Hanne: I've taken precautions for the mug. Ana: And for the website? One update – and suddenly your website is broken? WordPressBuilder backs up first – and rolls back if your site goes down. Start the update, then “Back up and update” – backup first, then everything's up to date. Hanne: Precautions suit them both. Updates with a safety net. Hanne: The mug travels. Does the paperwork too? Ana: Look at the paid order. Typing every shop order into an invoice by hand? With WordPressBuilder, every paid order becomes an invoice – and the buyer a customer. Set the order to “Processing (paid)”, “Run” – its invoice appears under “Invoices”. “Open Invoice” – there's the document, and the buyer is now a customer. Hanne: You're staying here for now. Ordered, paid, invoiced – without typing a thing.