A client has a static HTML website with the following pages:

• Home
• About
• Services
• Contact (with a contact form)
• Blog (10 existing blog posts)

They want the website converted to WordPress while keeping the exact same UI/design.

There is no custom functionality other than the contact form. The blog posts should be be migrated so they can manage future posts through the WordPress admin.

Hey — web dev here. I build small business sites at a clip of about 1–3 a week. A lot of them are “service area” sites: 60–100+ nearly identical pages (one per service or city), same ACF layout every time — hero text, intro copy, a few content boxes, a couple images.

Content updates were always the same nightmare: open page 1, edit field, save, open page 2… ×80. At that volume, hand-editing isn’t viable. WordPress doesn’t really have a good “change this ACF field across 70 pages” answer unless you want WP-CLI or a one-off script every time.

So I built Quickfields Bulk Editor for ACF for myself, and figured I’d put it out there in case other people building similar sites have the same headache.

• GitHub (free plugin): https://github.com/Sameer559-code/Quick-Fields-Bulk-Editor-for-ACF

The workflow that actually saves the most time for me: export a project to CSV → drop it into Claude/ChatGPT and ask it to rewrite/rephrase/expand content for all 70–100 pages (keeping the structure intact) → re-import the edited CSV. That export → AI edit → import loop is what the Pro side was built around; the in-browser spreadsheet is more for spot-fixes and image swaps.

What it does:

• Create a “project,” pick a post type, select which pages belong to it
• Spreadsheet view in WP admin — rows = pages, columns = ACF fields, one tab per field group
• Text/textarea/WYSIWYG fields are inline-editable and autosave
• Free: bulk text editing + image preview + clear text fields
• Pro: CSV export/import (images excluded from CSV import on purpose so you can’t wipe them), in-sheet image upload/replace

Needs ACF (or Secure Custom Fields) active. Admin-only (manage_options) — no front-end changes.

What I’m actually asking (not selling):

1. Does “export CSV → bulk-rewrite with AI → re-import” match how you’d want to do this, or would you want the AI step built into the plugin instead of going through Claude/ChatGPT manually?
2. Is this a real pain point for other devs/agencies, or is everyone already solving it with WP-CLI, ACF export/import, or custom scripts?
3. Anything that sounds like a dealbreaker before you’d even try it?

This started as a tool for my own workflow, so I have no idea if it generalizes. Before I polish it further, I’d genuinely like to know if it’s worth it — or if it’s a “me” problem I happened to solve for myself. Happy to answer questions about how it works under the hood too.

I’m part of the team behind AnpsThemes, and we have just finished adding Elementor support to our Transport WordPress theme.

Transport has been around for several years and was originally built around WPBakery. We did not want existing users to lose their current workflow, so WPBakery remains supported while new projects can now be created with Elementor.

The theme is designed specifically for logistics, freight, trucking, courier, warehouse and cargo companies. The Elementor update includes the theme’s main layouts and elements, rather than simply adding basic compatibility.

Our goal is to gradually modernize our established themes without abandoning customers who already built websites with older page builders.

For anyone maintaining an older commercial WordPress theme: do you think supporting both builders is still valuable, or would you eventually focus entirely on Elementor?

Transport is currently available through our own shop for a one-time price of $39.

Details:
https://anpsthemes.com/transport-theme-now-supports-elementor/

I've been rebuilding some of my layouts using Elementor's Nested Widgets, and the editing experience feels much better than the old Container workflow—especially when you have multiple levels of nested content.

A few things I've noticed:

• Drag & drop inside nested areas is much more intuitive.
• Complex sections are easier to organize.
• Reusable layouts require less restructuring.

I wrote up my findings and some tips here if anyone is interested:

https://anpsthemes.com/elementor-nested-widget-drag-drop-content-areas/

I'm interested in hearing from others who are already using Nested Widgets:

• Have you switched your production sites to them?
• Have you found any limitations or bugs?
• Do you think they'll eventually replace most traditional Container workflows?

So, we're doing a complete rebuild (moving from Drupal), and I'm looking for a good core theme to build on. This is for an enterprise site that has several custom databases of tech data (probably something we'd build out with ACF), but is otherwise a standard corporate "brochure" website.

I'm currently looking at Frost, but it's basically abandonware by Gardner/WPE, and also looked at Indio, which Gardner also abandoned, but Frost is a better fit with the default patterns we could build on.

So.. is there anything else out there that is a good core theme with a decent amount of patterns we could use as a starting point?

I've had Ollie and other recommended previously, but Ollie seems way over the top in features that would lock you in. I don't need a theme that has all those extra things baked in. (Similar, no page-builders, as we don't need all that extra stuff).

We also aren't an ecommerce place, so I don't need WooCommerce or payment hooks or any of that.

Any recommendations? Or thoughts on using Frost even though it's effectively abandoned?

I’m part of AnpsThemes, a Power Elite ThemeForest author that has been selling WordPress themes there since 2011.

For more than 14 years, ThemeForest was our only sales channel.

From 1 July, the amount we receive from the same $59 theme sale dropped from $41.13 to $23.49.

The calculation is:
- Customer pays: $59
- Envato keeps: $35.51
- AnpsThemes receives: $23.49

Envato first removes a fixed $12 buyer fee and then takes 50% of the remaining amount.

We still design and develop the theme, create the demos, test compatibility, release updates, maintain the documentation and support the customer.

What disappointed us most was not only the new fee, but also the way it was communicated. We received no email or dashboard notification and discovered the announcement through Reddit. We then had around 50 days to rebuild a business that had depended entirely on ThemeForest.

That forced us to create our own checkout, customer accounts, licensing, downloads, support system and ThemeForest purchase migration almost from scratch.

We are still selling on ThemeForest, but depending on it as our only sales channel is no longer sustainable.

We published the complete story, including real transaction screenshots and the full price breakdown:

https://anpsthemes.com/themeforest-fees-anpsthemes-going-direct/

I would be interested to hear from other WordPress product authors: are marketplaces still an important part of your business, or are you moving toward direct sales?

Quick Question. Brand new to WordPress. Am looking to to choose between Blocksy templates 'Garderobe' or 'Modern Shop' for ecommerce store. Being that I plan to pretty much redsign all pages as a whole with Elementor, is it fair to say that it wouldn't really matter which I choose because I would largely be ingoring the layout provided by the templates, or do they have different 'features' that I'm not aware of and so should be more considered as to which one I choose? My current understanding is that the features are the same in each template it's just how they have designed the layout of each template that's different.

So, first time Wordpress user here. Simple question I think. I have downloaded a Blocksy Child Theme for an ecommerce store that I'm building for myself. Do I need to also create a Child Theme for the Blocksy 'Template' that I plan on using (for the same reason that I created one for Blocksy) or does the fact that I created a Child Theme for Blocksy mean that I don't need to also create one for the Template I plan on using with the Blocksy Child Theme. I'm guessing that I should have a Child Theme for both 'Blocksy' and the 'Template' each, but not sure if that would be redundant. Hope that makes sense. Thanks.

Freelancer/agency angle: describe the business in a sentence, ~90 seconds later you get a full site with pages, on-brand copy, WooCommerce/blog/events structure, exported as a clean block theme that installs on any WordPress instance.

No page-builder lock-in, no hosting tie: the theme is yours. It's free during early access.

What I want from this sub specifically is working professionals telling me what's missing or wrong — the feedback so far has already surfaced RTL support questions and a two-week-old storage bug, so brutal is useful.

getpresto.dev
(Launched on PH today too, but honestly the feedback matters more than the votes.)