<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Oberon Lai</title>
    <description>The latest articles on DEV Community by Oberon Lai (@shippress).</description>
    <link>https://dev.to/shippress</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4212432%2Fcea2d723-418f-46ee-91d2-4d0005006067.png</url>
      <title>DEV Community: Oberon Lai</title>
      <link>https://dev.to/shippress</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shippress"/>
    <language>en</language>
    <item>
      <title>Your AI built a WooCommerce shop. Here's what to check before the first real order</title>
      <dc:creator>Oberon Lai</dc:creator>
      <pubDate>Thu, 29 Oct 2026 12:22:50 +0000</pubDate>
      <link>https://dev.to/shippress/your-ai-built-a-woocommerce-shop-heres-what-to-check-before-the-first-real-order-20o3</link>
      <guid>https://dev.to/shippress/your-ai-built-a-woocommerce-shop-heres-what-to-check-before-the-first-real-order-20o3</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Disclosure: I build ShipPress, the Mac app in the example near the end. The checks work on any WooCommerce site your AI agent touched, with or without it.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;I asked an AI agent to switch a demo shop to Japanese yen and put a copper pan on sale. It did both and gave me a neat table of the new prices. Then I opened the Shop page and every card still showed the old euro prices.&lt;/p&gt;

&lt;p&gt;Nothing was broken. The shop page had the products typed into it as static blocks, and the agent had changed the real products in WooCommerce. This is the most common gap I see when an AI builds a shop, and it's one of five I now check every time.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Are the product cards live or just text?
&lt;/h2&gt;

&lt;p&gt;Starter themes and AI-generated pages often lay out a "shop" as columns of images, headings and prices. It looks like a product grid, but it's plain content. When you change a price in WooCommerce, the page doesn't follow.&lt;/p&gt;

&lt;p&gt;Quick test: change one price in WooCommerce, then reload the page. If the old price stays, the cards are text. You can also look in the page content for a hard-coded price:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;wp post list &lt;span class="nt"&gt;--post_type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;page &lt;span class="nt"&gt;--fields&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;ID,post_title
wp post get 12 &lt;span class="nt"&gt;--field&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;post_content | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-nE&lt;/span&gt; &lt;span class="s2"&gt;"€|£|¥|&lt;/span&gt;&lt;span class="se"&gt;\\\$&lt;/span&gt;&lt;span class="s2"&gt;[0-9]"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If that finds prices, replace the section with a block that reads from the store, such as Product Collection (or the older &lt;code&gt;[products]&lt;/code&gt; shortcode). With an agent, be explicit: "replace the product grid on the Shop page with a live product list from the store". If you only say "update the shop page", you may get new static text with new prices.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Did the currency change everywhere?
&lt;/h2&gt;

&lt;p&gt;Changing the store currency is one setting:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;wp option get woocommerce_currency
wp option update woocommerce_currency JPY
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It doesn't convert your prices. A €34 pan becomes a ¥34 pan. Check that the agent set new prices too, and set the decimals. Yen has none, so &lt;code&gt;woocommerce_price_num_decimals&lt;/code&gt; should be 0 or you'll see ¥26,000.00. List the products and read the numbers:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;wp &lt;span class="nb"&gt;wc &lt;/span&gt;product list &lt;span class="nt"&gt;--user&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;1 &lt;span class="nt"&gt;--fields&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nb"&gt;id&lt;/span&gt;,name,regular_price,sale_price,stock_quantity
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Do the same for anything priced outside the product, such as shipping rates and free-shipping thresholds.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Sale prices, stock and new products
&lt;/h2&gt;

&lt;p&gt;Agents are good at bulk edits, but read the result rather than the summary. In the list above, check that:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the sale price is lower than the regular price, and the sale dates (if any) are the ones you meant&lt;/li&gt;
&lt;li&gt;stock is managed where you expect it, not "in stock" with no quantity&lt;/li&gt;
&lt;li&gt;new products are published, not drafts, and have a category and an image&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  4. Is any payment method switched on?
&lt;/h2&gt;

&lt;p&gt;A fresh WooCommerce install has no payment gateway enabled, so checkout says there are no payment methods available. Agents rarely mention this because nothing errors until a customer reaches checkout.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;wp &lt;span class="nb"&gt;wc &lt;/span&gt;payment_gateway list &lt;span class="nt"&gt;--user&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;1 &lt;span class="nt"&gt;--fields&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nb"&gt;id&lt;/span&gt;,title,enabled
wp &lt;span class="nb"&gt;wc &lt;/span&gt;payment_gateway update cod &lt;span class="nt"&gt;--enabled&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nb"&gt;true&lt;/span&gt; &lt;span class="nt"&gt;--user&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Cash on delivery is fine for a test. Before launch, set up your real gateway in its sandbox mode first.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Place a test order and find it in the admin
&lt;/h2&gt;

&lt;p&gt;Do it the way a customer would: add to cart, check the cart total uses the sale price, go through checkout, place the order. Then open WooCommerce › Orders and confirm the order is there with the right total and status. If you have email set up, check the order emails arrived. Many hosts block PHP mail, so "order received" on screen doesn't prove the email went out.&lt;/p&gt;

&lt;p&gt;One more thing before you plan hosting. A shop can't go out as a static copy. Cart, checkout and customer accounts need PHP and a database answering every request, so the shop needs a real WordPress host.&lt;/p&gt;

&lt;h2&gt;
  
  
  How this looks in ShipPress
&lt;/h2&gt;

&lt;p&gt;ShipPress is a free Mac app I make. It lets your own AI coding tool (Claude Code, Codex, Cursor CLI and others, on your account) build a real WordPress site on your Mac. In the video I pick a store design from the E-commerce filter, so WooCommerce comes installed with sample products. Then I ask the AI in chat to switch to yen, reprice everything, put the copper pan on sale and add an iron tamagoyaki pan.&lt;/p&gt;

&lt;p&gt;The Shop page still showed euros, for the reason in check 1. One more message swapped the static grid for a live product list. Checkout then said there were no payment methods (check 4), so I asked for Cash on delivery. The test order shows up under WooCommerce › Orders as processing, ¥26,000. When you click Go live, it points a shop to a WordPress host rather than the static copy.&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/GhXr3ZQtFOw" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;The written steps: &lt;a href="https://shippress.codotx.com/docs-woocommerce-store?ref=devto-en" rel="noopener noreferrer"&gt;https://shippress.codotx.com/docs-woocommerce-store?ref=devto-en&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The short version
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Change one price and reload the shop page. If it doesn't change, the cards are text.&lt;/li&gt;
&lt;li&gt;Currency change doesn't convert prices. Check decimals and shipping too.&lt;/li&gt;
&lt;li&gt;Read the product list yourself: sale below regular, stock, published.&lt;/li&gt;
&lt;li&gt;Turn on a payment method before the first test order.&lt;/li&gt;
&lt;li&gt;Place a real test order and find it in WooCommerce › Orders.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What's the strangest thing an AI agent has done to one of your WooCommerce stores? Mine was the shop page that kept showing euros after every product had moved to yen.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;ShipPress (free, Mac): &lt;a href="https://shippress.codotx.com/?ref=devto-en" rel="noopener noreferrer"&gt;https://shippress.codotx.com/?ref=devto-en&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Issues and feedback: &lt;a href="https://github.com/oberonlai/shippress-releases/issues" rel="noopener noreferrer"&gt;https://github.com/oberonlai/shippress-releases/issues&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Oberon Lai&lt;/p&gt;

</description>
      <category>woocommerce</category>
      <category>wordpress</category>
      <category>ai</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Moving a locally built AI WordPress site to your own host: static copy or full move?</title>
      <dc:creator>Oberon Lai</dc:creator>
      <pubDate>Thu, 29 Oct 2026 11:19:53 +0000</pubDate>
      <link>https://dev.to/shippress/moving-a-locally-built-ai-wordpress-site-to-your-own-host-static-copy-or-full-move-3h41</link>
      <guid>https://dev.to/shippress/moving-a-locally-built-ai-wordpress-site-to-your-own-host-static-copy-or-full-move-3h41</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Disclosure: I build ShipPress, the Mac app I use for the example near the end. Everything before that section works with any local WordPress setup and any AI coding agent.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Your AI agent built the site on your laptop, and every page looks right at &lt;code&gt;localhost&lt;/code&gt;. Then you try to put it online and the reservation form returns a 404, the search box goes nowhere and half the links still point at &lt;code&gt;http://localhost:8080&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;I've moved a fair few of these sites now, mostly small business sites built with Claude Code or Codex. The first decision is whether you need WordPress running on the live site at all. Everything else follows from that answer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Find out what you actually built
&lt;/h2&gt;

&lt;p&gt;AI agents tend to add things you didn't ask for. Before you choose how to move the site, open it and list anything that needs PHP after the page has loaded:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a contact or booking form&lt;/li&gt;
&lt;li&gt;comments&lt;/li&gt;
&lt;li&gt;a shop (WooCommerce)&lt;/li&gt;
&lt;li&gt;member logins&lt;/li&gt;
&lt;li&gt;a search box&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A quick way to catch forms is to search the theme and the rendered pages for where they send their data:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-rnE&lt;/span&gt; &lt;span class="s2"&gt;"admin-post&lt;/span&gt;&lt;span class="se"&gt;\.&lt;/span&gt;&lt;span class="s2"&gt;php|admin-ajax&lt;/span&gt;&lt;span class="se"&gt;\.&lt;/span&gt;&lt;span class="s2"&gt;php|wp-comments-post&lt;/span&gt;&lt;span class="se"&gt;\.&lt;/span&gt;&lt;span class="s2"&gt;php"&lt;/span&gt; wp-content/themes/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Agents love &lt;code&gt;admin-post.php&lt;/code&gt; for forms because it's the documented WordPress way to handle a custom POST. That's fine on a live WordPress install. On a static copy the file doesn't exist, so the form posts into nothing.&lt;/p&gt;

&lt;p&gt;If your list is empty (or only has search), a static copy will probably do. If it has a shop, logins, comments or forms you want to keep as they are, move the full site.&lt;/p&gt;

&lt;h2&gt;
  
  
  Option A: A static copy
&lt;/h2&gt;

&lt;p&gt;A static copy is every page saved as plain HTML, plus the CSS, JavaScript and images it uses. You can host it on Netlify, GitHub Pages, Cloudflare Pages or any web server. There's no database to patch, which is a big part of the appeal.&lt;/p&gt;

&lt;p&gt;The usual route is a static export plugin (Simply Static is a common choice) or a crawler such as &lt;code&gt;wget --mirror&lt;/code&gt;. Whichever you use, check these before you upload:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Permalinks.&lt;/strong&gt; If the site still uses plain links like &lt;code&gt;/?p=123&lt;/code&gt;, a static host sees every page as the same file. Go to Settings › Permalinks, choose Post name and save, then export again. Pages come out as &lt;code&gt;menu/index.html&lt;/code&gt;, &lt;code&gt;about/index.html&lt;/code&gt; and so on, which every static host understands.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Local addresses.&lt;/strong&gt; Search the exported folder for &lt;code&gt;localhost&lt;/code&gt; and &lt;code&gt;127.0.0.1&lt;/code&gt;. Also search for the escaped form &lt;code&gt;localhost:8080\/&lt;/code&gt;, which hides inside inline JSON and block markup:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-rlE&lt;/span&gt; &lt;span class="s2"&gt;"localhost|127&lt;/span&gt;&lt;span class="se"&gt;\.&lt;/span&gt;&lt;span class="s2"&gt;0&lt;/span&gt;&lt;span class="se"&gt;\.&lt;/span&gt;&lt;span class="s2"&gt;0&lt;/span&gt;&lt;span class="se"&gt;\.&lt;/span&gt;&lt;span class="s2"&gt;1"&lt;/span&gt; ./static-export/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Media.&lt;/strong&gt; Make sure every size in each image's &lt;code&gt;srcset&lt;/code&gt; was saved as well as the original. Open a few pages on a phone-sized window and watch the network tab for 404s. Background images set in CSS are the ones crawlers miss most often.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Forms.&lt;/strong&gt; Anything posting to &lt;code&gt;admin-post.php&lt;/code&gt;, &lt;code&gt;admin-ajax.php&lt;/code&gt; or &lt;code&gt;wp-comments-post.php&lt;/code&gt; needs a replacement. Your static host may offer form handling, or you can point the form at a form service. Otherwise, swap it for a plain &lt;code&gt;mailto:&lt;/code&gt; link or your booking provider's widget.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Search.&lt;/strong&gt; WordPress search is a query (&lt;code&gt;/?s=udon&lt;/code&gt;) that PHP answers. On a static copy you need a client-side index (Pagefind or Lunr) or you remove the search box.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;404, robots and sitemap.&lt;/strong&gt; Check that you have a &lt;code&gt;404.html&lt;/code&gt; and that &lt;code&gt;robots.txt&lt;/code&gt; doesn't still say &lt;code&gt;Disallow: /&lt;/code&gt; from development.&lt;/p&gt;

&lt;h2&gt;
  
  
  Option B: Move the full WordPress site
&lt;/h2&gt;

&lt;p&gt;If the site needs PHP, it needs a WordPress host. The move has three parts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Files.&lt;/strong&gt; You only need &lt;code&gt;wp-content&lt;/code&gt; (themes, plugins, uploads). Install a fresh WordPress on the host and let it keep its own &lt;code&gt;wp-config.php&lt;/code&gt; with its own database login.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Database.&lt;/strong&gt; Export it and import it on the host:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;wp db &lt;span class="nb"&gt;export &lt;/span&gt;site.sql
&lt;span class="c"&gt;# on the host, after uploading the file&lt;/span&gt;
wp db import site.sql
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Watch out if your local setup uses SQLite. Many quick local tools do, and most hosts run MySQL or MariaDB, so you need to convert the database before you import. A plugin-based migration tool can do this for you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Addresses.&lt;/strong&gt; Replace the local URL everywhere, including serialised data, which a plain find-and-replace in a text editor will corrupt:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;wp search-replace &lt;span class="s1"&gt;'http://localhost:8080'&lt;/span&gt; &lt;span class="s1"&gt;'https://example.co.uk'&lt;/span&gt; &lt;span class="nt"&gt;--all-tables&lt;/span&gt; &lt;span class="nt"&gt;--precise&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Then check these four things on the live site:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Permalinks:&lt;/strong&gt; visit Settings › Permalinks and click Save once so the host writes its rewrite rules. If inner pages 404 while the home page works, this is nearly always the cause.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Media:&lt;/strong&gt; confirm &lt;code&gt;wp-content/uploads&lt;/code&gt; arrived with the right file permissions and that image URLs use &lt;code&gt;https&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Forms:&lt;/strong&gt; send a real test. Many hosts block PHP's &lt;code&gt;mail()&lt;/code&gt;, so a form can show "thanks" and quietly send nothing. Set up SMTP if it does.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Search:&lt;/strong&gt; search for a word you know is on a page. If results are empty, the import probably missed tables or the table prefix differs from &lt;code&gt;wp-config.php&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Leave out what only made sense locally: SQLite plugins, local sign-in helpers and any files your AI tool used for its own notes or history.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I do it with ShipPress
&lt;/h2&gt;

&lt;p&gt;ShipPress is a free Mac app I make that lets your AI coding tool (Claude Code, Codex, Cursor CLI and others, on your own account) build a WordPress site locally. Each site is a normal WordPress folder in your home folder, with the database as a single SQLite file in &lt;code&gt;wp-content/database&lt;/code&gt;. You can always take it and leave.&lt;/p&gt;

&lt;p&gt;For a static copy, &lt;strong&gt;Go live&lt;/strong&gt; has a link at the bottom of the Free address tab: "Only want the files? Download the static copy". It saves every page, then checks the result before you upload anything. It looks for plain permalinks, leftover local addresses, a shop, links to wp-admin and forms that post to PHP. In the video it caught &lt;code&gt;?p=123&lt;/code&gt; addresses, and the fix was the Permalinks step above. The output has &lt;code&gt;index.html&lt;/code&gt;, one folder per page, a 404 page, &lt;code&gt;robots.txt&lt;/code&gt;, a sitemap and a headers file. When a page has a search box, it also adds a small search index that runs in the browser.&lt;/p&gt;

&lt;p&gt;For the full site, the WordPress host tab connects to a host once. InstaWP, Hostinger and Pressable connect directly, xCloud and Kinsta take an API key, and Cloudways takes your email and an API key. Any other host with SSH works through Connect with SSH. Go live then exports the database as a MySQL backup, swaps the local address for the live one and packs &lt;code&gt;wp-content&lt;/code&gt;. It leaves out the SQLite plugin, the local sign-in helper, ShipPress's editing helpers, its own &lt;code&gt;.aiwp&lt;/code&gt; folder and &lt;code&gt;wp-config.php&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Changing hosts later works the same way in reverse: download the site from the old host as a new local site, connect the new host and click Go live.&lt;/p&gt;

&lt;p&gt;Here's the whole flow on a restaurant site, Hinoki Udon, from the site folder to the static copy and the WordPress host tab:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/k8Ju-tnCHsM" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;The written version, step by step: &lt;a href="https://shippress.codotx.com/docs-export-move?ref=devto-en" rel="noopener noreferrer"&gt;https://shippress.codotx.com/docs-export-move?ref=devto-en&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  A short checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;List what needs PHP before you choose: forms, comments, shop, logins, search.&lt;/li&gt;
&lt;li&gt;Static copy: Post name permalinks first, then grep for &lt;code&gt;localhost&lt;/code&gt; and &lt;code&gt;admin-post.php&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Full move: &lt;code&gt;wp-content&lt;/code&gt; plus the database, &lt;code&gt;wp search-replace&lt;/code&gt; with &lt;code&gt;--precise&lt;/code&gt;, then save Permalinks once on the host.&lt;/li&gt;
&lt;li&gt;Test a real form submission on the live site.&lt;/li&gt;
&lt;li&gt;Search visibility: in Settings › Reading, untick "Discourage search engines from indexing this site" (or run &lt;code&gt;wp option update blog_public 1&lt;/code&gt;). When ticked, WordPress adds a &lt;code&gt;noindex&lt;/code&gt; robots meta tag to every page and turns off &lt;code&gt;wp-sitemap.xml&lt;/code&gt;. Before exporting, grep the export for &lt;code&gt;noindex&lt;/code&gt;. For a full move, check the setting again on the live site after the import, and confirm one page with URL Inspection in Search Console before you submit the sitemap.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Thanks to a reader for pointing out this one.&lt;/p&gt;

&lt;p&gt;Which part of the move has caught you out with an AI-built site? For me it was a booking form that worked perfectly on my laptop and posted to &lt;code&gt;admin-post.php&lt;/code&gt; on a static host.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;ShipPress (free, Mac): &lt;a href="https://shippress.codotx.com/?ref=devto-en" rel="noopener noreferrer"&gt;https://shippress.codotx.com/?ref=devto-en&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Issues and feedback: &lt;a href="https://github.com/oberonlai/shippress-releases/issues" rel="noopener noreferrer"&gt;https://github.com/oberonlai/shippress-releases/issues&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Oberon Lai&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>webdev</category>
      <category>ai</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How to brief an AI to build a WordPress site: the six questions that matter</title>
      <dc:creator>Oberon Lai</dc:creator>
      <pubDate>Wed, 28 Oct 2026 17:21:16 +0000</pubDate>
      <link>https://dev.to/shippress/how-to-brief-an-ai-to-build-a-wordpress-site-the-six-questions-that-matter-2c38</link>
      <guid>https://dev.to/shippress/how-to-brief-an-ai-to-build-a-wordpress-site-the-six-questions-that-matter-2c38</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Disclosure: I build ShipPress, the Mac app I use for the example in this article. The six questions work with any AI coding tool, with or without it.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;"Build me a website for my udon shop" gets you a generic site with a hero image, three feature boxes and a made-up menu with made-up prices. The AI isn't bad at WordPress. It just has nothing to work with, so it fills the gaps with averages.&lt;/p&gt;

&lt;p&gt;When I designed the onboarding for ShipPress, I tried to cut the brief down to the smallest set of questions that still changes what the AI builds. I ended up with six. Here they are, with what each one changes in the output and a short example answer for a small udon shop in Kyoto.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Who are you, and what do you do?
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;A family-run udon shop in Kyoto. We make the noodles by hand every morning.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This sets the voice and the page structure. A family shop gets an "Our story" page and a warmer tone. A consultancy gets service pages and case studies. Without it, the AI guesses, usually a startup landing page.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Who do you most want to visit your site?
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;Tourists planning a trip to Kyoto, plus regulars checking if we're open.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;One audience is enough. Tourists need the address, a map and an English menu near the top. Regulars need today's hours. Naming the audience decides what goes above the fold.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. What do you sell or offer?
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;Six kinds of udon, a seasonal special, and take-out on weekdays.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Real items give the AI real content to lay out. "Food" gets you placeholder cards. "Kitsune udon, curry udon and a seasonal special" gets you a menu page that's close to done.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Once the site is online, what would make you happy?
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;More table reservations on weekend evenings.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This one surprises people, but it changes the most. The goal becomes the main call to action. With "more reservations", the AI put a "Reserve a table" button at the top of the home page and added a reservation section. With no goal, you get a contact form at the bottom that nobody scrolls to.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. What must be on the site?
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;Opening hours, a map, the menu with prices, and that we're closed on Tuesdays.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;This is your checklist. It's also where I ask the AI to be honest: if it doesn't know the prices or hours, it should ask instead of inventing them. A site that shows a wrong closing day is worse than a site with a gap.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. What style do you like?
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;Warm and calm, with wood tones.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Three or four words is plenty. Adjectives plus one material or color ("wood tones", "navy and cream") steer the design better than "modern" or "clean", which every site claims to be.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tips that made the biggest difference
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Put the name in your first sentence.&lt;/strong&gt; "A small handmade udon shop in Kyoto called Hinoki Udon" tells the AI the site name. In ShipPress, the word after "called" becomes the site's name.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One concrete detail per answer.&lt;/strong&gt; A real dish, a real visitor, a real goal. Short is fine. Vague is the problem.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Leave blanks rather than guess.&lt;/strong&gt; You can skip any question and tell the AI more in the chat later.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Give real facts when the AI asks.&lt;/strong&gt; Prices, hours, address. Don't let placeholders ship.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What this looks like in ShipPress
&lt;/h2&gt;

&lt;p&gt;In ShipPress you type the one-sentence description on the Home screen, and it walks you through these six questions as a short interview. Your sentence stays at the top, so you only add what's missing. Then you click &lt;strong&gt;Build my site&lt;/strong&gt;, and your AI tool (Claude Code, Codex, Cursor CLI and others, on your own account) builds a real WordPress site on your Mac. Nothing is public until you choose to go live.&lt;/p&gt;

&lt;p&gt;Here's the full flow for the udon shop, from the first sentence to a site with its own design:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/yzBzLayJnmE" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;The written version, with screenshots of each step, is here: &lt;a href="https://shippress.codotx.com/docs-describe-your-site?ref=devto-en" rel="noopener noreferrer"&gt;https://shippress.codotx.com/docs-describe-your-site?ref=devto-en&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you already work with an AI CLI directly, you can paste the six answers into your first prompt as a brief. They work the same way there.&lt;/p&gt;

&lt;h2&gt;
  
  
  Your turn
&lt;/h2&gt;

&lt;p&gt;Which of the six do you usually skip when you brief an AI or a designer? For me it was question 4, until I saw how much it changed the home page.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;ShipPress (free, Mac): &lt;a href="https://shippress.codotx.com/?ref=devto-en" rel="noopener noreferrer"&gt;https://shippress.codotx.com/?ref=devto-en&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Issues and feedback: &lt;a href="https://github.com/oberonlai/shippress-releases/issues" rel="noopener noreferrer"&gt;https://github.com/oberonlai/shippress-releases/issues&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Oberon Lai&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>ai</category>
      <category>webdev</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Build real WordPress sites on your Mac by chatting with AI (fully local)</title>
      <dc:creator>Oberon Lai</dc:creator>
      <pubDate>Wed, 28 Oct 2026 13:30:38 +0000</pubDate>
      <link>https://dev.to/shippress/build-real-wordpress-sites-on-your-mac-by-chatting-with-ai-fully-local-4mpj</link>
      <guid>https://dev.to/shippress/build-real-wordpress-sites-on-your-mac-by-chatting-with-ai-fully-local-4mpj</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Disclosure: I build ShipPress, the Mac app this article is about.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;AI coding agents like Claude Code and Codex are pretty good at writing WordPress themes and pages now. When I actually use them, though, the code is rarely where I get stuck. The friction is everything around it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;setting up a local WordPress with PHP and a database&lt;/li&gt;
&lt;li&gt;deciding which folders the agent is allowed to touch&lt;/li&gt;
&lt;li&gt;rolling back a change that went wrong&lt;/li&gt;
&lt;li&gt;getting the finished site onto a real server&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I built ShipPress, a free Mac app, to take care of those parts. Here's what building a WordPress site through chat looks like with it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you need
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;macOS (Apple Silicon or Intel)&lt;/li&gt;
&lt;li&gt;one of these AI CLIs with your own account: Claude Code, Codex, Grok Build, Antigravity CLI or Cursor CLI&lt;/li&gt;
&lt;li&gt;ShipPress (free): &lt;a href="https://shippress.codotx.com/?ref=devto-en" rel="noopener noreferrer"&gt;https://shippress.codotx.com/?ref=devto-en&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You sign in to the CLI with your own account. ShipPress doesn't store your credentials, and AI usage runs on the plan you already pay for. On first launch ShipPress can install the AI tool for you with one click, so you don't have to open a terminal.&lt;/p&gt;

&lt;h2&gt;
  
  
  The flow
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Pick a starting point
&lt;/h3&gt;

&lt;p&gt;Either describe your project in one sentence or start from one of the bundled block themes (there are WooCommerce shop designs too). For example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Build a website for a small harbour-side cafe called "Harbor Beans", with a menu and opening hours.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Putting the name in the sentence also sets the site name.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Let the AI build
&lt;/h3&gt;

&lt;p&gt;Your chosen CLI builds the theme, pages and content straight into a local WordPress install. You can run more than one AI worker on the same site at once.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Fix things by chatting
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Make the header dark green.
Add the opening hours to the footer.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The preview updates right away. ShipPress saves a restore point after every AI change, so you can go back with one click. For me that's the biggest difference from working with the bare CLI.&lt;/p&gt;

&lt;p&gt;The canvas view shows all your pages side by side, and you can click a spot on a page to ask for a change there. You can check the phone view too.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Go live
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;direct connections: InstaWP, Hostinger, Pressable, Cloudways, Kinsta, xCloud&lt;/li&gt;
&lt;li&gt;over SSH: SiteGround, WordPress.com, DigitalOcean and other hosts with SSH access&lt;/li&gt;
&lt;li&gt;no hosting at all: export a static site and host it through ShipPress, including buying a domain in the app (not for shop sites)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Bare CLI or ShipPress?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Bare CLI&lt;/th&gt;
&lt;th&gt;ShipPress&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Local WP environment&lt;/td&gt;
&lt;td&gt;you set it up&lt;/td&gt;
&lt;td&gt;the app does it&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Undoing changes&lt;/td&gt;
&lt;td&gt;your own git workflow&lt;/td&gt;
&lt;td&gt;automatic restore point per change&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Preview&lt;/td&gt;
&lt;td&gt;open a browser yourself&lt;/td&gt;
&lt;td&gt;live in the app&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Deployment&lt;/td&gt;
&lt;td&gt;by hand&lt;/td&gt;
&lt;td&gt;host connection, SSH or static export&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;If you're comfortable in a terminal, the bare CLI works fine. ShipPress is for people who want to build WordPress sites with AI without living in the terminal.&lt;/p&gt;

&lt;h2&gt;
  
  
  Wrapping up
&lt;/h2&gt;

&lt;p&gt;AI agents are genuinely useful for WordPress sites. The hard parts are the environment, rollback and deployment, and that's what ShipPress handles.&lt;/p&gt;

&lt;p&gt;It's still early. If you try it and get stuck anywhere, tell me in the comments or open a GitHub issue.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Download: &lt;a href="https://shippress.codotx.com/?ref=devto-en" rel="noopener noreferrer"&gt;https://shippress.codotx.com/?ref=devto-en&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Issues: &lt;a href="https://github.com/oberonlai/shippress-releases/issues" rel="noopener noreferrer"&gt;https://github.com/oberonlai/shippress-releases/issues&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Video tutorials: &lt;a href="https://www.youtube.com/@codotx-app" rel="noopener noreferrer"&gt;https://www.youtube.com/@codotx-app&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A Windows version is planned.&lt;/p&gt;

&lt;p&gt;Oberon Lai&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>ai</category>
      <category>macos</category>
      <category>webdev</category>
    </item>
    <item>
      <title>5 safety steps before you let an AI coding agent touch WordPress</title>
      <dc:creator>Oberon Lai</dc:creator>
      <pubDate>Wed, 28 Oct 2026 11:19:02 +0000</pubDate>
      <link>https://dev.to/shippress/5-safety-steps-before-you-let-an-ai-coding-agent-touch-wordpress-epe</link>
      <guid>https://dev.to/shippress/5-safety-steps-before-you-let-an-ai-coding-agent-touch-wordpress-epe</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Disclosure: I make ShipPress, a Mac app, and I mention it briefly at the end. Everything before that works without my tool.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Claude Code, Codex and similar agents can now do a surprising amount of work on a WordPress theme or a set of pages. They also sometimes go a little past what you asked: they edit files they shouldn't touch, or write straight to the database. These are five things I wish I had done from day one after a few months of pairing AI agents with WordPress.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Work locally or on staging, never on production
&lt;/h2&gt;

&lt;p&gt;It sounds obvious, and it's the one that saves you the most. Don't let the agent work over SSH on the live site. Make changes locally or on a staging copy, check them, then move them over.&lt;/p&gt;

&lt;p&gt;wp-env, Local, Docker: it doesn't matter which. What matters is that it's a place where breaking things hurts nobody.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Limit the working directory
&lt;/h2&gt;

&lt;p&gt;If you hand the agent the whole repo or the WordPress root, it will read &lt;code&gt;wp-config.php&lt;/code&gt; and core files too. If you only want it working on the theme, start it inside the theme folder:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd &lt;/span&gt;wp-content/themes/my-theme
claude   &lt;span class="c"&gt;# or codex, etc.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;With Claude Code, a &lt;code&gt;CLAUDE.md&lt;/code&gt; in the project that spells out what's allowed helps a lot:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="gu"&gt;## Rules&lt;/span&gt;
&lt;span class="p"&gt;-&lt;/span&gt; Only change files under wp-content/themes/my-theme
&lt;span class="p"&gt;-&lt;/span&gt; Don't read or change wp-config.php or core files
&lt;span class="p"&gt;-&lt;/span&gt; Suggest new plugins, don't install them yourself
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  3. Back up the database, not just the files
&lt;/h2&gt;

&lt;p&gt;git can roll back files. But posts, pages, menus and block theme template edits live in the database, and git alone won't bring back a page the AI rewrote.&lt;/p&gt;

&lt;p&gt;So export with WP-CLI before every session:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# before&lt;/span&gt;
wp db &lt;span class="nb"&gt;export &lt;/span&gt;backups/before-ai-&lt;span class="si"&gt;$(&lt;/span&gt;&lt;span class="nb"&gt;date&lt;/span&gt; +%Y%m%d-%H%M&lt;span class="si"&gt;)&lt;/span&gt;.sql

&lt;span class="c"&gt;# roll back if needed&lt;/span&gt;
wp db import backups/before-ai-20261028-1300.sql
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And on the file side, commit after every step:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git add &lt;span class="nt"&gt;-A&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; git commit &lt;span class="nt"&gt;-m&lt;/span&gt; &lt;span class="s2"&gt;"before: ask agent to change header colour"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  4. Keep each request small
&lt;/h2&gt;

&lt;p&gt;"Build me the whole website" is much harder to review and undo than "build only the hero section of the home page". If you work in small rounds (request, check, snapshot), you can see right away which instruction broke something.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Read the diff before you deploy
&lt;/h2&gt;

&lt;p&gt;Before anything goes live, I check at least this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git diff &lt;span class="nt"&gt;--stat&lt;/span&gt;                  &lt;span class="c"&gt;# which files changed&lt;/span&gt;
wp plugin list &lt;span class="nt"&gt;--status&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;active   &lt;span class="c"&gt;# any plugins you don't recognise?&lt;/span&gt;
wp option get siteurl            &lt;span class="c"&gt;# did the URL get rewritten?&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If &lt;code&gt;siteurl&lt;/code&gt; or &lt;code&gt;home&lt;/code&gt; reaches production still set to your local URL, the site stops loading. That one is worth a second look.&lt;/p&gt;

&lt;h2&gt;
  
  
  Summary
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Work locally or on staging&lt;/li&gt;
&lt;li&gt;Limit where the agent can work&lt;/li&gt;
&lt;li&gt;Back up files with git and the database with &lt;code&gt;wp db export&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Small requests, check after each one&lt;/li&gt;
&lt;li&gt;Check the diff and settings before you deploy&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Aside: an app that does this for you
&lt;/h2&gt;

&lt;p&gt;Steps 1 to 3 were too much manual work for me every time, so I built a free Mac app called &lt;strong&gt;ShipPress&lt;/strong&gt;. It sets up a local WordPress site, lets the AI CLI you already have (Claude Code, Codex, Grok Build, Antigravity CLI, Cursor CLI) build the site, and creates a restore point every time the AI changes something. You can publish through host integrations like InstaWP, over SSH, or as a static export.&lt;/p&gt;

&lt;p&gt;Download: &lt;a href="https://shippress.codotx.com/?ref=devto-en" rel="noopener noreferrer"&gt;https://shippress.codotx.com/?ref=devto-en&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you have your own tricks for keeping AI agents safe around WordPress, I'd love to hear them in the comments.&lt;/p&gt;

&lt;p&gt;Oberon Lai&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>ai</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Créer de vrais sites WordPress sur Mac en discutant avec une IA (100 % en local)</title>
      <dc:creator>Oberon Lai</dc:creator>
      <pubDate>Wed, 28 Oct 2026 10:19:38 +0000</pubDate>
      <link>https://dev.to/shippress/creer-de-vrais-sites-wordpress-sur-mac-en-discutant-avec-une-ia-100-en-local-3hac</link>
      <guid>https://dev.to/shippress/creer-de-vrais-sites-wordpress-sur-mac-en-discutant-avec-une-ia-100-en-local-3hac</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Transparence : je développe l'app Mac ShipPress, dont parle cet article.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Les agents de code IA comme Claude Code ou Codex écrivent désormais des thèmes et des pages WordPress plutôt correctement. En pratique, ce n'est presque jamais le code qui me bloque, mais tout ce qu'il y a autour :&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;monter un environnement WordPress local avec PHP et une base de données&lt;/li&gt;
&lt;li&gt;décider quels dossiers l'agent a le droit de toucher&lt;/li&gt;
&lt;li&gt;revenir en arrière quand une modification tourne mal&lt;/li&gt;
&lt;li&gt;mettre le site terminé sur un vrai serveur&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;C'est pour ça que j'ai créé ShipPress, une app Mac gratuite. Voici à quoi ressemble le déroulé quand on construit un site WordPress uniquement en discutant.&lt;/p&gt;

&lt;h2&gt;
  
  
  Ce qu'il vous faut
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;macOS (Apple Silicon ou Intel)&lt;/li&gt;
&lt;li&gt;l'un de ces CLI d'IA avec votre propre compte : Claude Code, Codex, Grok Build, Antigravity CLI ou Cursor CLI&lt;/li&gt;
&lt;li&gt;ShipPress (gratuit) : &lt;a href="https://shippress.codotx.com/?ref=devto-fr" rel="noopener noreferrer"&gt;https://shippress.codotx.com/?ref=devto-fr&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Vous vous connectez au CLI avec votre propre compte. ShipPress ne stocke aucun identifiant, et l'utilisation de l'IA passe par votre abonnement existant.&lt;/p&gt;

&lt;h2&gt;
  
  
  Le déroulé
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Choisir un point de départ
&lt;/h3&gt;

&lt;p&gt;Soit vous décrivez votre projet en une phrase, soit vous partez d'un des thèmes blocs fournis (il y en a aussi pour les boutiques WooCommerce). Par exemple :&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Crée un site pour le petit café "Harbor Beans" sur le port, avec la carte et les horaires d'ouverture.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  2. Laisser l'IA construire
&lt;/h3&gt;

&lt;p&gt;Le CLI choisi construit le thème, les pages et le contenu directement dans une installation WordPress locale. Vous pouvez aussi faire travailler plusieurs workers IA en même temps sur un même site.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Ajuster en discutant
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Passe l'en-tête en vert foncé.
Ajoute les horaires d'ouverture dans le pied de page.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;L'aperçu se met à jour tout de suite. Après chaque modification de l'IA, un point de restauration est créé automatiquement, et un clic suffit pour revenir en arrière. Pour moi, c'est la plus grosse différence avec le CLI seul.&lt;/p&gt;

&lt;p&gt;La vue Canvas affiche toutes les pages côte à côte, et vous pouvez cliquer directement sur un endroit pour demander une modification. La vue mobile se vérifie aussi.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Publier
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;connexion directe : InstaWP, Hostinger, Pressable, Cloudways, Kinsta, xCloud&lt;/li&gt;
&lt;li&gt;par SSH : SiteGround, WordPress.com, DigitalOcean et d'autres hébergeurs avec SSH&lt;/li&gt;
&lt;li&gt;sans hébergement : export en site statique hébergé par ShipPress, avec achat de nom de domaine dans l'app (pas pour les boutiques)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  CLI seul ou ShipPress ?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;CLI seul&lt;/th&gt;
&lt;th&gt;ShipPress&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Environnement WP local&lt;/td&gt;
&lt;td&gt;à monter soi-même&lt;/td&gt;
&lt;td&gt;géré par l'app&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Annuler une modification&lt;/td&gt;
&lt;td&gt;à la main avec git ou autre&lt;/td&gt;
&lt;td&gt;point de restauration automatique à chaque modification&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Aperçu&lt;/td&gt;
&lt;td&gt;ouvrir le navigateur soi-même&lt;/td&gt;
&lt;td&gt;immédiat dans l'app&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mise en ligne&lt;/td&gt;
&lt;td&gt;à la main&lt;/td&gt;
&lt;td&gt;connexion hébergeur, SSH ou export statique&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Si vous êtes à l'aise dans le terminal, le CLI seul fait très bien l'affaire. ShipPress s'adresse à ceux qui veulent construire du WordPress avec l'IA sans se battre avec le terminal.&lt;/p&gt;

&lt;h2&gt;
  
  
  En résumé
&lt;/h2&gt;

&lt;p&gt;Les agents IA sont tout à fait utilisables pour des sites WordPress. Les vrais obstacles sont l'environnement, le retour en arrière et la mise en ligne, et c'est ce dont s'occupe ShipPress.&lt;/p&gt;

&lt;p&gt;Le projet est encore jeune. Si vous l'essayez et que vous bloquez quelque part, dites-le dans les commentaires ou ouvrez une issue GitHub.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Téléchargement : &lt;a href="https://shippress.codotx.com/?ref=devto-fr" rel="noopener noreferrer"&gt;https://shippress.codotx.com/?ref=devto-fr&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Issues : &lt;a href="https://github.com/oberonlai/shippress-releases/issues" rel="noopener noreferrer"&gt;https://github.com/oberonlai/shippress-releases/issues&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Une version Windows est prévue.&lt;/p&gt;

&lt;p&gt;Oberon Lai&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>ai</category>
      <category>francais</category>
      <category>macos</category>
    </item>
    <item>
      <title>Echte WordPress-Seiten auf dem Mac per KI-Chat bauen (komplett lokal)</title>
      <dc:creator>Oberon Lai</dc:creator>
      <pubDate>Wed, 28 Oct 2026 09:26:51 +0000</pubDate>
      <link>https://dev.to/shippress/echte-wordpress-seiten-auf-dem-mac-per-ki-chat-bauen-komplett-lokal-4n19</link>
      <guid>https://dev.to/shippress/echte-wordpress-seiten-auf-dem-mac-per-ki-chat-bauen-komplett-lokal-4n19</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Hinweis: Ich entwickle die Mac-App ShipPress, um die es in diesem Artikel geht.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;KI-Coding-Agenten wie Claude Code oder Codex schreiben WordPress-Themes und Seiten inzwischen ziemlich gut. In der Praxis hänge ich aber selten am Code fest, sondern an allem drumherum:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;eine lokale WordPress-Umgebung mit PHP und Datenbank aufsetzen&lt;/li&gt;
&lt;li&gt;festlegen, welche Ordner der Agent anfassen darf&lt;/li&gt;
&lt;li&gt;schiefgegangene Änderungen zurückrollen&lt;/li&gt;
&lt;li&gt;die fertige Seite auf einen echten Server bringen&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Genau dafür habe ich ShipPress gebaut, eine kostenlose Mac-App. Hier zeige ich, wie der Ablauf aussieht, wenn man eine WordPress-Seite nur per Chat baut.&lt;/p&gt;

&lt;h2&gt;
  
  
  Was du brauchst
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;macOS (Apple Silicon oder Intel)&lt;/li&gt;
&lt;li&gt;eines dieser KI-CLIs mit eigenem Konto: Claude Code, Codex, Grok Build, Antigravity CLI oder Cursor CLI&lt;/li&gt;
&lt;li&gt;ShipPress (kostenlos): &lt;a href="https://shippress.codotx.com/?ref=devto-de" rel="noopener noreferrer"&gt;https://shippress.codotx.com/?ref=devto-de&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Du meldest dich im jeweiligen CLI mit deinem eigenen Konto an. ShipPress speichert keine Zugangsdaten, und die KI-Nutzung läuft über deinen bestehenden Tarif.&lt;/p&gt;

&lt;h2&gt;
  
  
  Ablauf
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Startpunkt wählen
&lt;/h3&gt;

&lt;p&gt;Entweder beschreibst du dein Projekt in einem Satz, oder du nimmst eines der mitgelieferten Block-Themes (es gibt auch welche für WooCommerce-Shops). Zum Beispiel:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Bau eine Website für das kleine Café "Harbor Beans" am Hafen, mit Speisekarte und Öffnungszeiten.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  2. Die KI bauen lassen
&lt;/h3&gt;

&lt;p&gt;Das gewählte CLI baut Theme, Seiten und Inhalte direkt in einer lokalen WordPress-Installation. Du kannst auch mehrere KI-Worker gleichzeitig an einer Seite arbeiten lassen.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Per Chat nachbessern
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Mach den Header dunkelgrün.
Füge die Öffnungszeiten in den Footer ein.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Die Vorschau aktualisiert sich sofort. Nach jeder Änderung der KI entsteht automatisch ein Wiederherstellungspunkt, sodass du mit einem Klick zurückkannst. Das ist für mich der größte Unterschied zur Arbeit mit dem nackten CLI.&lt;/p&gt;

&lt;p&gt;In der Canvas-Ansicht siehst du alle Seiten nebeneinander und kannst direkt auf eine Stelle klicken, um eine Änderung anzufordern. Die mobile Ansicht lässt sich auch prüfen.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Veröffentlichen
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;direkte Anbindung: InstaWP, Hostinger, Pressable, Cloudways, Kinsta, xCloud&lt;/li&gt;
&lt;li&gt;per SSH: SiteGround, WordPress.com, DigitalOcean und andere Hosts mit SSH&lt;/li&gt;
&lt;li&gt;ganz ohne Hosting: als statische Seite exportieren und über ShipPress hosten, inklusive Domainkauf in der App (nicht für Shop-Seiten)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Nacktes CLI oder ShipPress?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Nacktes CLI&lt;/th&gt;
&lt;th&gt;ShipPress&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Lokale WP-Umgebung&lt;/td&gt;
&lt;td&gt;selbst einrichten&lt;/td&gt;
&lt;td&gt;macht die App&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Änderungen zurücknehmen&lt;/td&gt;
&lt;td&gt;selbst mit git o. Ä.&lt;/td&gt;
&lt;td&gt;automatischer Wiederherstellungspunkt pro Änderung&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Vorschau&lt;/td&gt;
&lt;td&gt;Browser selbst öffnen&lt;/td&gt;
&lt;td&gt;sofort in der App&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Deployment&lt;/td&gt;
&lt;td&gt;von Hand&lt;/td&gt;
&lt;td&gt;Host-Anbindung, SSH oder statischer Export&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Wer sich im Terminal wohlfühlt, kommt auch mit dem nackten CLI gut zurecht. ShipPress ist für Leute gedacht, die WordPress mit KI bauen wollen, ohne sich mit dem Terminal herumzuschlagen.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fazit
&lt;/h2&gt;

&lt;p&gt;KI-Agenten sind für WordPress-Seiten absolut brauchbar. Die Hürden sind Umgebung, Zurückrollen und Deployment, und darum kümmert sich ShipPress.&lt;/p&gt;

&lt;p&gt;Das Projekt ist noch früh. Wenn du es ausprobierst und irgendwo hängen bleibst, schreib es gern in die Kommentare oder als GitHub-Issue.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Download: &lt;a href="https://shippress.codotx.com/?ref=devto-de" rel="noopener noreferrer"&gt;https://shippress.codotx.com/?ref=devto-de&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Issues: &lt;a href="https://github.com/oberonlai/shippress-releases/issues" rel="noopener noreferrer"&gt;https://github.com/oberonlai/shippress-releases/issues&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Eine Windows-Version ist in Planung.&lt;/p&gt;

&lt;p&gt;Oberon Lai&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>ai</category>
      <category>deutsch</category>
      <category>macos</category>
    </item>
    <item>
      <title>5 précautions avant de laisser un agent de code IA toucher à WordPress</title>
      <dc:creator>Oberon Lai</dc:creator>
      <pubDate>Wed, 28 Oct 2026 08:13:29 +0000</pubDate>
      <link>https://dev.to/shippress/5-precautions-avant-de-laisser-un-agent-de-code-ia-toucher-a-wordpress-2h6g</link>
      <guid>https://dev.to/shippress/5-precautions-avant-de-laisser-un-agent-de-code-ia-toucher-a-wordpress-2h6g</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Transparence : je développe l'app Mac ShipPress, que je présente rapidement à la fin. Les conseils qui précèdent marchent très bien sans mon outil.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Claude Code ou Codex savent maintenant faire beaucoup de choses sur un thème ou des pages WordPress. Mais un agent déborde parfois de sa mission : il modifie des fichiers qu'il ne devait pas toucher, ou écrit directement dans la base de données. Voici cinq habitudes que j'aurais aimé prendre dès le début, après quelques mois à faire travailler l'IA sur WordPress.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Travailler en local ou en préproduction, jamais en production
&lt;/h2&gt;

&lt;p&gt;Ça paraît évident, et c'est pourtant ce qui protège le plus. Ne laissez pas l'agent travailler en SSH sur le site en ligne. Modifiez en local ou sur un staging, vérifiez, puis seulement ensuite publiez.&lt;/p&gt;

&lt;p&gt;wp-env, Local ou Docker, peu importe. Ce qui compte, c'est d'avoir un endroit où casser quelque chose ne gêne personne.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Limiter le répertoire de travail
&lt;/h2&gt;

&lt;p&gt;Si vous donnez à l'agent tout le dépôt ou la racine WordPress, il lira aussi &lt;code&gt;wp-config.php&lt;/code&gt; et les fichiers du cœur. S'il ne doit toucher qu'au thème, lancez-le dans le dossier du thème :&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd &lt;/span&gt;wp-content/themes/mon-theme
claude   &lt;span class="c"&gt;# ou codex, etc.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Avec Claude Code, un fichier &lt;code&gt;CLAUDE.md&lt;/code&gt; dans le projet permet en plus d'écrire noir sur blanc ce qui est autorisé :&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="gu"&gt;## Règles&lt;/span&gt;
&lt;span class="p"&gt;-&lt;/span&gt; Ne modifier que les fichiers sous wp-content/themes/mon-theme
&lt;span class="p"&gt;-&lt;/span&gt; Ne pas lire ni modifier wp-config.php ni les fichiers du cœur
&lt;span class="p"&gt;-&lt;/span&gt; Proposer de nouvelles extensions, sans les installer soi-même
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  3. Sauvegarder la base de données, pas seulement les fichiers
&lt;/h2&gt;

&lt;p&gt;Git permet de revenir en arrière sur les fichiers. Mais les articles, les pages, les menus et les modifications des modèles d'un thème de blocs vivent dans la base. Git seul ne vous rendra pas une page créée par l'IA.&lt;/p&gt;

&lt;p&gt;Avant chaque session, un export avec WP-CLI :&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# avant&lt;/span&gt;
wp db &lt;span class="nb"&gt;export &lt;/span&gt;backups/avant-ia-&lt;span class="si"&gt;$(&lt;/span&gt;&lt;span class="nb"&gt;date&lt;/span&gt; +%Y%m%d-%H%M&lt;span class="si"&gt;)&lt;/span&gt;.sql

&lt;span class="c"&gt;# retour arrière si besoin&lt;/span&gt;
wp db import backups/avant-ia-20261028-1300.sql
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Et côté fichiers, un commit après chaque étape :&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git add &lt;span class="nt"&gt;-A&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; git commit &lt;span class="nt"&gt;-m&lt;/span&gt; &lt;span class="s2"&gt;"avant : changement de couleur du header"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  4. Donner des tâches courtes
&lt;/h2&gt;

&lt;p&gt;« Construis-moi tout le site » est bien plus difficile à vérifier et à annuler que « Construis seulement la section hero de l'accueil ». En avançant par petits tours (demande, vérification, sauvegarde), on voit tout de suite quelle consigne a cassé quelque chose.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Relire le diff avant de déployer
&lt;/h2&gt;

&lt;p&gt;Avant toute mise en ligne, je vérifie au minimum ceci :&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git diff &lt;span class="nt"&gt;--stat&lt;/span&gt;                  &lt;span class="c"&gt;# quels fichiers ont changé&lt;/span&gt;
wp plugin list &lt;span class="nt"&gt;--status&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;active   &lt;span class="c"&gt;# une extension inconnue est-elle apparue ?&lt;/span&gt;
wp option get siteurl            &lt;span class="c"&gt;# l'URL a-t-elle été réécrite ?&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Si &lt;code&gt;siteurl&lt;/code&gt; ou &lt;code&gt;home&lt;/code&gt; arrivent en production avec l'URL locale, le site devient inaccessible. Ça mérite un second coup d'œil.&lt;/p&gt;

&lt;h2&gt;
  
  
  En résumé
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Travailler en local ou en préproduction&lt;/li&gt;
&lt;li&gt;Limiter le périmètre de l'agent&lt;/li&gt;
&lt;li&gt;Fichiers avec git, base de données avec &lt;code&gt;wp db export&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Petites tâches, vérification à chaque étape&lt;/li&gt;
&lt;li&gt;Contrôler le diff et les réglages avant le déploiement&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Au passage : une app qui fait ça automatiquement
&lt;/h2&gt;

&lt;p&gt;Les étapes 1 à 3 me demandaient trop de travail manuel à chaque fois, alors j'ai créé &lt;strong&gt;ShipPress&lt;/strong&gt;, une app Mac gratuite. Elle installe un WordPress local, laisse votre CLI d'IA existante (Claude Code, Codex, Grok Build, Antigravity CLI, Cursor CLI) construire le site, et crée un point de restauration à chaque modification de l'IA. Pour publier, il y a des intégrations d'hébergeurs comme InstaWP, le SSH ou un export statique.&lt;/p&gt;

&lt;p&gt;Téléchargement : &lt;a href="https://shippress.codotx.com/?ref=devto-fr" rel="noopener noreferrer"&gt;https://shippress.codotx.com/?ref=devto-fr&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Si vous avez vos propres astuces pour faire travailler un agent IA sur WordPress sans risque, je serais ravi de les lire en commentaire.&lt;/p&gt;

&lt;p&gt;Oberon Lai&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>ai</category>
      <category>francais</category>
      <category>webdev</category>
    </item>
    <item>
      <title>5 Sicherheitsmaßnahmen, bevor du einen KI-Coding-Agenten an WordPress lässt</title>
      <dc:creator>Oberon Lai</dc:creator>
      <pubDate>Wed, 28 Oct 2026 07:22:36 +0000</pubDate>
      <link>https://dev.to/shippress/5-sicherheitsmassnahmen-bevor-du-einen-ki-coding-agenten-an-wordpress-lasst-31f0</link>
      <guid>https://dev.to/shippress/5-sicherheitsmassnahmen-bevor-du-einen-ki-coding-agenten-an-wordpress-lasst-31f0</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Hinweis: Ich entwickle die Mac-App ShipPress. Am Ende des Artikels stelle ich sie kurz vor. Die Tipps davor funktionieren auch ganz ohne mein Tool.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Mit Claude Code oder Codex kann man inzwischen erstaunlich viel an einem WordPress-Theme oder an Seiten erledigen lassen. Gleichzeitig gehen Agenten manchmal etwas über den Auftrag hinaus: Sie ändern Dateien, die sie nicht anfassen sollten, oder schreiben direkt in die Datenbank. Hier sind fünf Dinge, die ich nach einigen Monaten mit KI und WordPress gerne von Anfang an gemacht hätte.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Lokal oder auf Staging arbeiten, nicht auf Produktion
&lt;/h2&gt;

&lt;p&gt;Klingt banal, bringt aber am meisten. Lass den Agenten nicht per SSH auf der Live-Seite arbeiten. Besser: lokal oder auf einer Staging-Umgebung ändern, prüfen und erst dann übernehmen.&lt;/p&gt;

&lt;p&gt;Ob wp-env, Local oder Docker ist egal. Wichtig ist nur, dass es ein Ort ist, an dem kaputte Dinge niemandem wehtun.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Das Arbeitsverzeichnis eingrenzen
&lt;/h2&gt;

&lt;p&gt;Wenn du dem Agenten das ganze Repo oder das WordPress-Root gibst, liest er auch &lt;code&gt;wp-config.php&lt;/code&gt; und Core-Dateien. Soll er nur am Theme arbeiten, starte ihn im Theme-Ordner:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cd &lt;/span&gt;wp-content/themes/my-theme
claude   &lt;span class="c"&gt;# oder codex usw.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Bei Claude Code hilft zusätzlich eine &lt;code&gt;CLAUDE.md&lt;/code&gt; im Projekt, die festhält, was erlaubt ist:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;&lt;span class="gu"&gt;## Regeln&lt;/span&gt;
&lt;span class="p"&gt;-&lt;/span&gt; Nur Dateien unter wp-content/themes/my-theme ändern
&lt;span class="p"&gt;-&lt;/span&gt; wp-config.php und Core-Dateien weder lesen noch ändern
&lt;span class="p"&gt;-&lt;/span&gt; Neue Plugins nur vorschlagen, nicht selbst installieren
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  3. Nicht nur Dateien, auch die Datenbank sichern
&lt;/h2&gt;

&lt;p&gt;Dateien lassen sich mit git zurückdrehen. Aber Beiträge, Seiten, Menüs und Änderungen an Block-Theme-Templates liegen in der Datenbank. Mit git allein bekommst du eine von der KI erstellte Seite nicht zurück.&lt;/p&gt;

&lt;p&gt;Vor jeder Session also ein Export mit WP-CLI:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# vorher&lt;/span&gt;
wp db &lt;span class="nb"&gt;export &lt;/span&gt;backups/before-ai-&lt;span class="si"&gt;$(&lt;/span&gt;&lt;span class="nb"&gt;date&lt;/span&gt; +%Y%m%d-%H%M&lt;span class="si"&gt;)&lt;/span&gt;.sql

&lt;span class="c"&gt;# zurück, wenn nötig&lt;/span&gt;
wp db import backups/before-ai-20261028-1300.sql
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Und auf der Dateiseite nach jedem Schritt committen:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git add &lt;span class="nt"&gt;-A&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; git commit &lt;span class="nt"&gt;-m&lt;/span&gt; &lt;span class="s2"&gt;"vorher: Header-Farbe ändern lassen"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  4. Aufträge klein halten
&lt;/h2&gt;

&lt;p&gt;„Bau mir die ganze Website" ist schwerer zu prüfen und zurückzunehmen als „Bau nur den Hero-Bereich der Startseite". Wenn du in kleinen Runden arbeitest (Auftrag, prüfen, Snapshot), siehst du sofort, welche Anweisung etwas kaputt gemacht hat.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Vor dem Deploy den Diff anschauen
&lt;/h2&gt;

&lt;p&gt;Bevor etwas live geht, prüfe ich mindestens das hier:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git diff &lt;span class="nt"&gt;--stat&lt;/span&gt;                  &lt;span class="c"&gt;# welche Dateien sich geändert haben&lt;/span&gt;
wp plugin list &lt;span class="nt"&gt;--status&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;active   &lt;span class="c"&gt;# sind unbekannte Plugins dazugekommen?&lt;/span&gt;
wp option get siteurl            &lt;span class="c"&gt;# wurde die URL umgeschrieben?&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Landen &lt;code&gt;siteurl&lt;/code&gt; oder &lt;code&gt;home&lt;/code&gt; mit der lokalen URL auf Produktion, ist die Seite nicht mehr erreichbar. Darauf lohnt sich ein zweiter Blick.&lt;/p&gt;

&lt;h2&gt;
  
  
  Zusammenfassung
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Lokal oder auf Staging arbeiten&lt;/li&gt;
&lt;li&gt;Den Arbeitsbereich des Agenten eingrenzen&lt;/li&gt;
&lt;li&gt;Dateien mit git, Datenbank mit &lt;code&gt;wp db export&lt;/code&gt; sichern&lt;/li&gt;
&lt;li&gt;Kleine Aufträge, nach jedem Schritt prüfen&lt;/li&gt;
&lt;li&gt;Vor dem Deploy Diff und Einstellungen kontrollieren&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Nebenbei: eine App, die das automatisch macht
&lt;/h2&gt;

&lt;p&gt;Weil mir die Schritte 1 bis 3 jedes Mal zu viel Handarbeit waren, habe ich die kostenlose Mac-App &lt;strong&gt;ShipPress&lt;/strong&gt; gebaut. Sie richtet eine lokale WordPress-Umgebung ein, lässt deine vorhandene KI-CLI (Claude Code, Codex, Grok Build, Antigravity CLI, Cursor CLI) die Seite bauen und legt bei jeder Änderung der KI einen Wiederherstellungspunkt an. Veröffentlichen kannst du über Host-Integrationen wie InstaWP, per SSH oder als statischen Export.&lt;/p&gt;

&lt;p&gt;Download: &lt;a href="https://shippress.codotx.com/?ref=devto-de" rel="noopener noreferrer"&gt;https://shippress.codotx.com/?ref=devto-de&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Wenn ihr eigene Tricks habt, um KI-Agenten bei WordPress sicher arbeiten zu lassen, freue ich mich über einen Kommentar.&lt;/p&gt;

&lt;p&gt;Oberon Lai&lt;/p&gt;

</description>
      <category>wordpress</category>
      <category>ai</category>
      <category>deutsch</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
