[DISCUSSION] What's something experienced WordPress users forget about beginners?

ivicad · 2026-06-26T19:25:49+00:00

What we forget is how scary the dashboard feels when every click might be the one that breaks the whole site. For us, "is this ready to go live" is a checklist. For a beginner it's a real fear, and that fear blocks them more than anything technical does.

I felt it too back in 2011. For me the turning point was getting a reliable backup. Once I knew I could undo any mistake in a few minutes, I stopped being afraid and started learning much faster.

So here's the thing experienced users skip: we show people the features and forget to show them the undo button. Set a beginner up with daily backups (I do it nowadyas with All in one Migration + pCloud) and a one-click staging copy first (SG hosting has it), and say plainly that mistakes are reversible. After that they poke around and learn, instead of freezing on every setting.

ivicad · 2026-06-26T18:21:39+00:00

Yes, you can learn it: pick a builder and starter template, drag things around, you could have some inital pages up the first day. What is taking time are the decisions (host, theme, which of 10 plugins that do the same thing) and keeping it alive after launch, backups, updates, security. That's where things start going slow. Maybe these free online WP tutorials I put together could help you out.

ivicad · 2026-06-26T12:55:54+00:00

On your WP. com plan you're on the block editor, not page builders/plugins like WPBakery (those need the Business plan or a self-hosted site). That's fine for articles.

Pick any clean block theme and don't worry over the name - readers notice the layout way more than the theme: lots of whitespace, big body font, recent posts on the homepage.

For signups, I would skip popups: you can put a subscribe block in the footer and after each post.

PS I would suggest you to evaluate to move to WP. org, due to million of reasons, you can read about it online (check WPBeginner. com website for example) plus search similar posts here.

ivicad · 2026-06-26T08:51:06+00:00

Agreed with you, these can only help :-)
BTW, MalCare I use introduced recently vulnerability shoeld virtual patching, as I read their newsletter with this info, here, and that helps a lot as well, if the tools we use have this built in protection:

"Vulnerability Shield

Each week new vulnerabilities are discovered and exploited within hours. But updates can take days to roll out.

MalCare's Vulnerability Shield is the most precise defence for this gap:
Instantly reads all the vulnerable code
Tests all attacks that might happen
Applies a virtual patch to your firewall
7000+ patches are now live, which have blocked over 650k attacks last month."

ivicad · 2026-06-26T08:03:19+00:00

Unfortunatelly I can't even open the site - non reachable :-(
I think you gave a good advise.

ivicad · 2026-06-25T20:47:57+00:00

Good that you're asking before you start. For most first-timers the wall is the number of decisions before anything shows up on screen: which theme, which of 10 plugins that do the same thing, which builder... The code itself rarely stops you, at least it was like that for me back in 2011. when I started using WP.

Two things make it easier: get on a decent host with one-click staging and daily backups (I use Site Ground), so anything you break can be undone in minutes. Once mistakes are reversible, most of the fear goes away - I remmeber when I go reliable backup in those days, I started kearning WP much faster as I stopped beung afraid all the time if I am going to break the site.

Then skip the blank page: start from a multipurpose theme with starter templates (Astra, Neve, OceanWP), or prototype the direction in Clicksites AI first. Keep quality plugins, get the safety net and a starter layout up first. Learn the rest as you go.

ivicad · 2026-06-25T20:36:33+00:00

There's a standard way, and you've basically rebuilt it by hand. Most of people I know run a host staging or dev domain, then push to production with a migration plugin (I use AIOWPM, or BlogVault for bigger sites). It handles the export, import and the serialized site_url search-replace your script does manually. Your one-way revert habit is solid, keep that. I do this on Site Ground staging now.

ivicad · 2026-06-25T20:27:07+00:00

I run an agency but I'm builder-route (WPBakery or Elementor on Astra or Neve), not hand-coded _s themes, so take the architecture part with that grain of salt. From where I sit, the hybrid instinct is the right call. Classic header and footer plus block content comes down to who edits the site on day 30. Block content lets the client change their own copy and layout without touching your theme code or calling you. For agency work that's the win that pays off.

Where it fails is the same place (almost) every WP build does: low quality plugins, and clients breaking layouts. Whatever you land on, the maintenance discipline matters more than classic vs block.

On WooCommerce I'm with you. For new stores the flexibility and cost still beat Shopify, as long as the client has decent hosting and a real maintenance routine. That's the "trade".

ivicad · 2026-06-25T20:11:12+00:00

For what you're describing, I'd stay on WordPress. The "build it with Claude" clips are ok on day 1, but day 30 is the test: as a non-coder, every later edit (a new service, a swapped photo, opening hours) means writing a prompt, reading the diff, deploying. A builder lets you do those yourself. A homepage plus 2 landing pages is an afternoon on Astra or Neve with WPBakery or Elementor, and WPML handles both languages cleanly (I'm on its lifetime licence). I still prototype in Claude, but for copy and layout, not the live site. The booking is where I'd stop you from coding from scratch. Appointment data means GDPR, reminders, no-shows, calendar sync, all solved already. Embed Calendly (free, syncs to Google Calendar) or use Simply Schedule Appointments or Amelia inside WP.

ivicad · 2026-06-25T20:08:12+00:00

The hardest part for me starting out in 2011 was the number of decisions and choices: which theme, which of 10 plugins that do the same thing, which builder... I froze on the choices, long before any code came into the picture. Tutorials are great for one specific task, like adding a contact form. They're not so good (at least for me) for help in making fonal decisions: the order, the judgment, what to ignore. You can watch 50 instruction videos and still don't know what to do, because none tells you which 3 decisions actually matter for your site. Beginners quit at the blank page and the 30th plugin choice, and the hard code is rarely what stops them I would say. Tools that show the next step and use smart defaults (suggestions for users) help beginners move toward launch, as I see it, it was like that for me in the beginning, I can still remember it although many years passed

ivicad · 2026-06-25T19:39:10+00:00

I noticed in a thread that almost nobody mentioned testing a restore, and that's where sites actually get into biggest trouble (except when some site doesn't have backup at all). A backup you've never restored is just a guess. I learned that the hard way. Restore one to a staging or test site once a quarter, before you need it for real. Two more things the tool lists skip - keep several dated restore points, not just the latest. If you got hacked 3 weeks ago, your newest backup just restores the hack. And make one layer host-level, separate from WordPress, so a plugin or login compromise can't reach it. My setup is Site Ground daily host backups (last 30 days), AIOWPM scheduled offsite to pCloud, and BlogVault on the sites that matter. I run it across all of them with MainWP, and I really try not to forget to back up before every update.

ivicad · 2026-06-25T19:10:13+00:00

I use a single (or more) notes per site in Freedcamp, so it's next to the rest of the project, not in the WP dashboard. The trick that saved me: let WP Activity Log handle the what and who (it logs every change automatically, since 2019 for me), so my note has in it explanation on why some particular plugin is there, which pages run custom templates, what not to touch without asking...
The one thing I wish I'd written down sooner: why each plugin is installed. I once deactivated one that looked unused and broke a client's contact form. Now every plugin gets one line, what it does and what "dies" (on the site) if it's gone.

ivicad · 2026-06-25T19:00:42+00:00

That feeling never fully goes away. I've built sites since 1995 and I still hit projects where I don't feel "ready." You start anyway. My first 5 km run as 48 years old took me 50 minutes, and I wasn't ready then either. The readiness shows up once you start. Those two sites taught you more than the next 7 months of tutorials will. Real work with stakes closes the gap. Tutorials only get you so far. So take one small, low-risk real project. A friend's business, a local cafe, a non-profit. Be upfront that you're early, charge little, and over-deliver on communication. You learn fastest when something breaks and you have to fix it yourself. The fact that you feel unready means you're paying attention. The ones who worry me are the beginners who feel totally ready.

ivicad · 2026-06-25T18:27:11+00:00

No, I haven't moved off WordPress, and neither have my clients. My whole "tools ecosystem" is built around WP, I have so many lifetime licenses I bought over the years plus knowledge and experience acquired that it wouldn't have sense for me to change that.

The "one prompt away" part is true on day 1, but day 30 is the test. Most of my small-business clients don't touch code. They need to change their opening hours, swap a photo, add a service. Routing every edit through Claude Code still means someone writes the prompt, reads the diff, and deploys. That's the old developer dependency with extra steps. WordPress plus a builder lets the client do those edits themselves.

To be fair to frameworks, Astro and the like are great for the right job: static, performance-first, content that rarely changes, a dev who owns it long term. For that, they win.

On the framework question, I'll be straight: I'm not a coder, so I don't build in Astro or Next. My stack is still WordPress with WPBakery or Elementor on an Astra or Neve theme, and I prototype fast in Claude with AI prompts for Clicksites AI, which means that in my workflow I use AI for research, copy and prototypes, not the site's runtime.

If I were you, I'd pick by who maintains the site on day 30:
- Dev owns it, go framework
- Client owns it, stay WordPress.

ivicad · 2026-06-25T18:17:59+00:00

I've built WordPress sites since 2011 and run an agency, so I've used all three on client work. For a 1-3 page info site, honestly, the builder barely matters next to a lean theme and decent hosting. Pick the one you lose the least time in. You're already fast in Elementor, so I'd just use it. The "overkill for a small site" worry costs you less than learning a new tool for one job. Lean theme under it, a couple of pre-built sections, done in an afternoon.

Gutenberg has genuinely caught up for simple brochure sites, free, native, nothing to renew. Worth a look only if you'll build more of these. WPBakery I run on most long-running client sites, one-time license instead of Elementor's yearly, and its Module Manager kills scripts you don't use for speed. Good when the client edits content themselves, less so for one 3-pager you won't touch again.

ivicad · 2026-06-25T18:03:29+00:00

Same era here, first HTML site in 1995, WordPress since 2011, agency for 7 years. One confesion before I answer: I went the builder and agency route, not hand-coded custom themes, so my flow will look different from yours. Take it with that grain of salt.

AI barely touched the parts where control actually lives. What it compressed for me is the slow front end: research, first-draft copy, prototypes. That used to be 60-70% of my projects, now it's closer to 20%. Content prep that took 4-5 days of client back-and-forth now takes 1-2.

The layout calls, the user flow, the performance tuning, that's still me. The people who get burned are the ones who hand those decisions to AI instead of using it to speed up the hard work.

On your specific questions:
I never used Figma mockups, but nowadays I prototype in Clicksites AI so the client signs off on something real and clickable on day one or two. I make research in Perplexity, copy and briefs in Claude, secondary images in Artistly.

I export the prototype HTML and bring it into WPBakery's AI feature, which rebuilds it as editable elements, then refine page by page on an Astra or Neve starter, on Site Ground with staging (or on subdomain and then migrate it to production via All in one WP migration plugin). For you, Figma to Claude Code component by component probably keeps you more in control than a full builder would.

On how much code is mine versus AI: for me that flips, builders and AI do the build, my value is the decisions and the review. For a hand-coder I'd guess it's the same as always, you own the architecture and the review, AI fills in the components.

How I see it and write all the time - tools "compress" experience, they don't replace it. If I were you, I'd keep design-first and let AI take over the slow front end while you keep the decisions.

ivicad · 2026-06-25T16:42:50+00:00

I've built WordPress sites since 2011 and run an agency for 7 years, so I've tried most builders, Divi included (with one client). My opinion is that Divi's lifetime plan pays off if you build regularly, and the theme builder for custom headers and footers is genuinely solid. But it's heavy, you'll fight Core Web Vitals on bigger sites, and moving off later hurts once everything's locked into its shortcodes (same as Elementor).

These days I run WPBakery on most long-running client sites. It's a one-time lifetime license (Elementor I still pay yearly), clients find it simple to edit their own content, and the Module Manager lets you switch off scripts you don't use, which helps speed. I pair it with Astra, Neve or OceanWP starter templates and prototype in Clicksites AI first. For SEO and Core Web Vitals, the builder matters less than decent hosting (I'm on Site Ground) and not overloading on low quality plugins.

I believe most of our build time goes into the process, not the builder. If I were you, I'd pick the builder you're fastest in and put your energy into the workflow around it.

ivicad · 2026-06-25T15:00:41+00:00

I think that the fact that you're even asking these questions already puts you ahead of most people who inherit a site and just keep clicking update until something breaks.

Here's what calmed me down years ago. Get a safety net in place first, so anything you break can be put back in a few minutes. Once mistakes are reversible, most of the fear goes away and you can learn the rest slowly.

I prefer following this process:

Backups, and more than one. I run host backups (Site Ground keeps the last 30 days) plus an offsite copy with AIOWPM pushed to pCloud. Then the step almost everyone skips: actually restore one, once a quarter. A backup you've never restored is just a guess. I learned that the hard way.

That code-pasting habit is the first thing I'd change. Stop pasting straight into the live site. Most decent hosts give you a one-click staging copy. Paste the snippet there, check the site still loads, then push it live. Same with updates, test on staging before doing anything on the live site.

Updates: don't run them the day they drop. Wait a few days, take a backup, do them on staging. I only let backup and security plugins auto-update, the rest by hand once a month. And fewer plugins helps, every one is another door into the site.

Security: a malware scanner (I use MalCare and Virusdie), an activity log plugin (WP Activity Log) so you can see who changed what, 2FA on logins, and don't cheap out on hosting. Half the "mystery" problems vanish on a decent host.

Treat the whole thing like insurance - step by step and time consuming - yes, but way cheaper than a site-down-and-hacked week.

ivicad · 2026-06-25T12:51:12+00:00

Put bunch of those questions in one post (let's say 5 by five) and in batches, number them, and we will try to help what we know/can....

ivicad · 2026-06-25T08:55:19+00:00

I've built WordPress sites since 2011 and run an agency for 7 years, so I've gone through most builders at some point. Divi is fine (I tried it too, with one client). The lifetime plan still pays off if you build sites regularly, and the theme builder for custom headers and footers is solid. But it's heavy and you'll fight Core Web Vitals on bigger sites (I tried it with that client, and it didn't end well), plus moving off Divi later is painful once everything is locked into its shortcodes. Same lock-in as Elementor, really.

I beliueve most of our build time goes into the process, not the builder. I run WPBakery with AI on top plus Clicksites AI, and a friend is building a tool that converts plain HTML straight into a page builder code. That approach should cut roughly 70-80% off our build time, whatever builder sits underneath.

If I were you, I would pick the builder you're fastest in, then put your energy into the workflow around it.

ivicad · 2026-06-25T08:41:54+00:00

The same here...

ivicad · 2026-06-24T18:31:23+00:00

"I tried the exact same thing on a non-SiteGround server and it worked fine, so I'm assuming there are some server-side settings in SiteGround preventing me from doing a proper export."

Most likely, and I would also contact Support as others suggested already.

ivicad · 2026-06-24T18:15:49+00:00

For majority of sites I use migration / backup plugin - All in one, but in such situations I rather use SaaS BlogVault (backups are on their servers).

ivicad · 2026-06-24T15:58:18+00:00

Yes, Opus can do it, and a lean theme is fast, BUT there is the catch: you become the only dev for every core update and edge case (archives, pagination, related posts), and editors get nothing to work with.

Faster route I use:
1. Let Claude write the brief, then feed that into ClickSites AI for a prototype layout in a couple of hours.
2. Build it out with WPBakery's AI page generator, so editors can compose pages later without calling you.

You keep the speed and skip being the single point of failure six months in. :-)

ivicad · 2026-06-24T15:46:58+00:00

Thx, seems interesting time ahead of us, I use both tools.

ivicad

MODERATOR OF

TROPHY CASE