wp

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-08-28

Final complete day: 2026-08-28. Attention was 0.4% — this entity appeared in 10 of 2,594 analyzed posts/comments in the seven days ending that day (14 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-08-28 16:17 UTCPost

   Kualo to Greengeeks - nameservers or redirects first? - Need serious help - migrating peer-reviewed journal - I'm at the end of my tether here. I'm singlehandedly trying to revamp an old custom html/php site (a peer-reviewed journal that's been running for a decade) hosted on Kualo and move it to GreenGeeks with a WP installation. The site is on a temporary domain (no SSL) and is basically finished. I got the domain transfer today. But I have no clue what I'm supposed to do next. I have 20 pages of notes. I know my way around plugins, CSS, etc. But I simply cannot figure out what order to do the major steps in... I'm genuinely exhausted. All I can do is give you these notes: * Let the domain transfer finish in the background (takes a few days). * Update Nameservers & SSL: * Update domain nameservers to point to GreenGeeks. * Turn on SSL certificate * Run Better Search Replace for all database urls * Set Up Redirects * SEO * Turn off maintenance plugin " 1. Point the nameservers to GreenGeeks. 1. Wait for ecologicalcitizen.net to reach your GreenGeeks site. 2. Get SSL working. 1. Make sure works properly. 3. Change WordPress to the real domain. 1. In Settings → General, change both WordPress Address and Site Address from the temporary URL to 2. You may be logged out; log back in using the new address. 4. Run Better Search Replace. 1. Use it for the remaining temporary-domain references and other internal URL/path changes in your database (PDFs, artwork, images, etc.). 2. You don't need it just to change the WordPress Address/Site Address. 5. Set up your 301 redirects. 1. Do this while Maintenance Mode is still ON. 2. This handles old URLs that have changed/disappeared, including the relevant old article, author and PDF URLs. 6. Check the site. 1. Make sure the new pages, images, PDFs, links, etc. work. 7. Go live. 1. Turn off Maintenance Mode. 2. Allow search engines to index the site. 8. Test old URLs. 1. Check that important old URLs redirect to their new destinations rather than producing 404s." I need to redirect thousands of URLs so I already have loads of rules written out in a document, with some idea what do for regex syntax... e.g., Regex: /what-is.php?... → /definitions/ This is blindingly complicated. I simply am beyond my capabilities here. I thought the above plan was fine, but it's not because apparently you can do the redirects first by using relative paths. Also, if you do nameserver changes first then surely everyone will get 404s. I seriously need help. This is a collossal task. In fact, if I can't do this, an entire journal dies, along with my livlihood.

2. 2026-08-27 21:53 UTCComment

   In every instance I ever used Wordpress it was client requested. I would never pick WP as a tool in any circumstance especially not in the modern era. I am not convinced that most sites require any CMS at all; markdown injection has gotten robust enough that I will generally lean in that direction unless I must do otherwise. A lot of the approach I am describing here is trying to sidestep Wordpress, so you are right to ask the question. I just always liked working inside of this paradigm in WP because it removes all the annoying platform specific nonsense that tends to create security and pagespeed issues.

3. 2026-08-27 20:00 UTCComment

   For sure I generally pitch headless Shopify to get out of plugin land for the ecommerce folks but I agree it is not something you want to be messing with. Woo is also kind of unwieldy at this point if it ever wasn't. To be honest - this is nostalgia talk for me I haven't found a WP client in years. The only work of any kind I've had this year is smart home stuff. I actually wrote a block building CMS this year with an agent just to see if I could. It was a fun project but not anything worth like actually trying to bring to market. But I did get it to build styles and js into a single bundle each and wrote like a theming / typography controls in a way I felt reflected how style guides work instead of pure WYSIWYG. Made it so that my plugin set each submitted scss and js parts to a little task runner that used a separate Node server to build bundles for each and send them back on an API call during publish, so it got pretty performant and acted like an SPA. I didn't get into tree shaking on it that was the next step but there was really no impetus to continue I am just working on projects to keep fresh and have a narrative if anyone every decides to grant me a job interview.

4. 2026-08-27 18:12 UTCComment

   Been working with WP since its inception. After approaching this problem many times as you describe, I now just immediately move to scorched earth and hand-rolled custom theme. LLM's make it too easy to transform data to not just immediately move it into a clean install and rebuild theme from scratch. I also don't use plugins, functions.php (unless I have to do like MIME-type acceptance or other core unavoidable tasks), or any of the other onboard features. Just ACF and custom theme and I generally build the theme out in a little CI/CD build script I wrote in Node a while back to replace an earlier Gulp process. The really perverse thing I do is that I use Pug with PHP, which is a super weird barely supported flavor of Pug that produces a set of templates that build themselves on the fly and therefore make no calls back to the server for header or footer; each page is complete the partials are in the codebase as pug files. I don't have a lot of live clients anymore this work has dried up for me but if you are curious here is a repo and example site from an old now defunct client. I think this approach annoys a lot of WP devs. It's basically removing Wordpress from Wordpress is order to make it performant and secure. It also puts the client experience on rails hard; there is no builder support here I think they lead to bad websites. Also the lighthouse scores kind of speak for themselves. In any case I am not expecting people to love it but it is an approach that worked for me for a long time. I designed it to handle change requests and function within a reasonable source-control paradigm. Primarily used it to manage very large corporate marketing sites that got a lot of attention from stakeholders.

5. 2026-08-27 11:43 UTCComment

   My sanity. Why would I ever touch a WP project?