What to do next on this site

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Build the definitive Wordpress cornerstone guide — on the site wordpressmeetup.com.

WHY IT MATTERS
Create the single most useful, authoritative page on Wordpress anywhere — the resource the whole site points to. Deep, current, expertly structured, and link-worthy. This anchors the site's authority and is the page most likely to earn rankings and citations.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Wordpress — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Wordpress resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Make the homepage genuinely distinctive — kill any generic-template feel — on the site wordpressmeetup.com.

WHY IT MATTERS
Give the homepage a clear point of view, a memorable hero, and real utility above the fold. A distinctive, intentional design lifts trust, time-on-page, and the Agents-First score out of generic-template territory.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Wordpress — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Wordpress resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Lock down sensitive data — nothing private is publicly reachable — on the site wordpressmeetup.com.

WHY IT MATTERS
Make sure a logged-out visitor or bot cannot reach anything sensitive on this site: /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404, never 200. Then scan the served HTML, JS, and JSON for leaked keys, tokens, internal emails, or personal data and remove them.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site wordpressmeetup.com.

WHY IT MATTERS
Assume a determined automated, AI-driven attacker. Enforce HTTPS, add a sensible Content-Security-Policy plus the standard security headers, eliminate open redirects and reflected user input, validate and rate-limit any form, and ensure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data — never internal or personal information.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Verify HTTPS, security headers & a safe Agents-First surface — on the site wordpressmeetup.com.

WHY IT MATTERS
Confirm the certificate is valid and HTTPS is forced, the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, CSP), and the Agents-First endpoints expose only public, non-sensitive information — trustworthy to humans and safe for the agents reading it.

HOW TO APPROACH IT
1. Confirm nothing sensitive is publicly reachable: as a logged-out visitor, /.git/, /.env, backups (.bak/.zip/.sql/.tgz), config files, .htpasswd, and any private or admin path must return 403 or 404 — never 200.
2. Scan the served HTML, JS, and JSON for leaked secrets, API keys, tokens, internal emails, or personal data, and remove anything that should not be public.
3. Enforce HTTPS and confirm the standard security headers are present (HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a sensible Content-Security-Policy).
4. Harden anything interactive against a determined automated or AI-driven attacker: validate and rate-limit forms, eliminate open redirects and reflected input, and make sure every agent/API endpoint and machine file (AGENTS.md, llms.txt, *.json) returns ONLY public data.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A logged-out request to every sensitive path returns 403/404 — verified, not assumed.
- No secret, key, token, internal email, or personal datum appears anywhere in the served HTML, JS, or JSON.
- HTTPS is forced and security headers are confirmed live; the Agents-First surface exposes only public information — the site is mythos-attack-proof.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Publish: A current, data-backed explainer in Wordpress — on the site wordpressmeetup.com.

WHY IT MATTERS
Trending angle in Wordpress. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Wordpress reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Add an interactive tool and an email capture for Wordpress — on the site wordpressmeetup.com.

WHY IT MATTERS
Build one genuinely useful interactive element for Wordpress (a calculator, checklist, finder, or quiz) plus a tasteful email capture. Tools earn repeat visits, backlinks, and a first-party audience the site actually owns.

HOW TO APPROACH IT
1. Study the strongest existing pages on this topic anywhere and decide what would make THIS the single most useful page in Wordpress — then build exactly that.
2. Write substantial, original content with a clear structure: a strong thesis up top, well-organized sections, concrete real examples and current numbers, and a decisive takeaway.
3. Ground every claim in current, authoritative sources and link out to them inline; never invent facts or statistics.
4. Wire it into the site: link from the homepage and nav, cross-link /sources/ and related pages, and add Article + FAQ schema.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The page is genuinely the strongest Wordpress resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
City-by-city WordPress meetup directory worksheet — on the site wordpressmeetup.com.

WHY IT MATTERS
Build a sortable directory of active US WordPress meetups from public meetup listings, city, cadence, format, official link, in the alldomains worksheet pattern with row-to-card detail. Each city gets its own indexable page catching 'wordpress meetup austin' style queries, with a dated last-verified stamp for honesty. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
WordCamp calendar with CFP deadline tracking — on the site wordpressmeetup.com.

WHY IT MATTERS
Maintain a WordCamp schedule page from official central listings: dates, locations, ticket windows, and speaker call-for-papers deadlines, the detail organizers hunt for. CFP deadlines especially get searched by would-be speakers and are poorly aggregated anywhere, making this page a natural recurring bookmark in the WP community. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Definitive start-a-meetup organizer playbook — on the site wordpressmeetup.com.

WHY IT MATTERS
Write the reference guide for launching a WordPress meetup: chapter program requirements, venue-finding tactics, first-event formats, sponsor etiquette, no-show math. Package a printable organizer checklist. Community organizers share operational playbooks in Slack and forums constantly, which is exactly the linking behavior this domain needs to attract. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Publish: The question your Wordpress audience is searching most right now — on the site wordpressmeetup.com.

WHY IT MATTERS
Trending angle in Wordpress. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Wordpress reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Publish: A 'what changed in 2026' round-up for Wordpress — on the site wordpressmeetup.com.

WHY IT MATTERS
Trending angle in Wordpress. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/.

HOW TO APPROACH IT
1. Research the angle right now using at least 3 authoritative, current sources; capture the real, specific data points.
2. Write a focused page: a clear thesis, the evidence, what it concretely means for a Wordpress reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- A reader learns something current and genuinely useful they could not get from a thin AI page.
- At least 3 real sources are cited and linked; no fabricated numbers.
- The page is internally linked and submitted for fast indexing.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Organizer AV gear guide with Amazon links — on the site wordpressmeetup.com.

WHY IT MATTERS
Publish an honest presenter-kit guide for meetup organizers, HDMI capture for recording talks, lapel mics, presentation clickers, portable projectors, tagged colinfirthfan-20 with real trade-offs per budget tier. Organizers buying gear for a recurring event are high-intent purchasers, and the guide slots naturally under the playbook. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Sponsored enhanced listings for local WP agencies — on the site wordpressmeetup.com.

WHY IT MATTERS
Offer local WordPress agencies and freelancers a clearly-labeled enhanced listing on their city's meetup page, logo, blurb, link. Agencies already sponsor meetups for local visibility; this is the same honest spend online. Inquiries go through a form that drafts a Gmail notification for review, never auto-sends. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
AdSense on directory and calendar pages — on the site wordpressmeetup.com.

WHY IT MATTERS
Enable AdSense pub-7759195213529699 on the city directory and WordCamp calendar pages once traffic establishes, keeping the organizer playbook lighter so it stays a clean, linkable resource. Directory traffic is habitual and geographically diverse, which suits network-standard ad inventory without harming the community-resource positioning. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Deepen the main Wordpress guide with current data and examples — on the site wordpressmeetup.com.

WHY IT MATTERS
Audit the flagship page; replace anything stale, add concrete numbers and a clear next step. Depth is what separates this from a thin template.

HOW TO APPROACH IT
1. Audit the flagship Wordpress page and list exactly what is stale, thin, or vague.
2. Replace stale material with current data, add concrete real examples, tighten the structure, and add a clear next step for the reader.
3. Cross-link to /sources/ and the most related pages.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Depth and accuracy match the best competitor page in Wordpress.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Event-flyer layout for city meetup pages — on the site wordpressmeetup.com.

WHY IT MATTERS
Lay each city page out like a great meetup flyer: oversized date block, venue line, bold RSVP-style outbound button to the official group, and a strip of upcoming-dates tickets along the bottom. The flyer metaphor keeps essential logistics scannable in five seconds, matching how attendees actually use these pages. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Lanyard-badge and sticker-sheet conference aesthetic — on the site wordpressmeetup.com.

WHY IT MATTERS
Art-direct from WordCamp material culture: city entries styled as conference name-tag badges on lanyards, sticker-sheet motifs for category chips, and the WordPress community blue (#21759b) as the anchor accent. Anyone who has attended a WordCamp recognizes the visual language immediately; it reads community, not corporate. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Event schema on every meetup and WordCamp — on the site wordpressmeetup.com.

WHY IT MATTERS
Mark each listed meetup occurrence and WordCamp with Event schema (name, date, venue, organizer URL) and add FAQPage answers for 'are WordPress meetups free' and 'do I need to be a developer to attend'. Keep both sitemaps generated and run af-deploy.py toward 90-plus. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Subscribable ICS feed of WordCamps and meetups — on the site wordpressmeetup.com.

WHY IT MATTERS
Generate an ICS calendar feed of upcoming WordCamps and major meetup dates that users and agents can subscribe to in Google or Apple Calendar. A live calendar subscription is sticky in a way no webpage is, and 'subscribe to the WordPress events calendar' becomes the site's signature shareable asset. (Fable enhanced action — also on the global worksheet.)

HOW TO APPROACH IT
1. Plan the cleanest way to accomplish this, then execute it well.
2. Use real, current information and match the existing quality of the site.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The task is fully done, accurate, and live.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Add an FAQ answering the top questions in Wordpress — on the site wordpressmeetup.com.

WHY IT MATTERS
Pull the real questions people ask in Wordpress and answer them plainly. Mark up with FAQ schema for rich results.

HOW TO APPROACH IT
1. Audit the flagship Wordpress page and list exactly what is stale, thin, or vague.
2. Replace stale material with current data, add concrete real examples, tighten the structure, and add a clear next step for the reader.
3. Cross-link to /sources/ and the most related pages.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Depth and accuracy match the best competitor page in Wordpress.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Apply a WT-Skins kit to lift the design and Agents-First score — on the site wordpressmeetup.com.

WHY IT MATTERS
The page looks generic without a kit. Roll the cluster's kit (snapshot the old design first) to get the AF score into the 90s.

HOW TO APPROACH IT
1. Snapshot the current design first (save a dated copy under the site) so there is a rollback point.
2. Apply the change so the site looks distinctive and intentional — never a generic template — then run the Agents-First scorer.
3. Verify on the live render, not on a file:// preview.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The Agents-First score is 90+ and the page looks designed rather than defaulted, with a rollback point saved.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Keep the live / news feed updated on cadence (2×/day) — on the site wordpressmeetup.com.

WHY IT MATTERS
Confirm the cron is publishing fresh, attributed Wordpress items and pinging IndexNow each run.

HOW TO APPROACH IT
1. Confirm or set up the auto-publishing /live/ or /news/ feed for Wordpress: attributed, links out, and running on a 2x/day cadence.
2. Make sure each run pings IndexNow and the items are genuinely fresh and relevant.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The feed publishes fresh, correctly-attributed Wordpress items on schedule and is discovered quickly.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Submit updated URLs via IndexNow and refresh the sitemap — on the site wordpressmeetup.com.

WHY IT MATTERS
Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Add Article + FAQ structured data — on the site wordpressmeetup.com.

WHY IT MATTERS
Schema.org markup earns richer results and helps answer-engines cite the page correctly.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Strengthen internal links between the core, /sources/ and this worksheet — on the site wordpressmeetup.com.

WHY IT MATTERS
A tight internal-link web spreads authority and keeps visitors moving through the site.

HOW TO APPROACH IT
1. Implement the specific change (structured data / IndexNow / internal links) precisely and completely.
2. Validate it — rich-results test for schema, confirm the IndexNow submission, or check the internal-link graph.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- The change validates cleanly and the affected pages are eligible for richer results or faster discovery.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Refresh the /videos/ playlist with current, embeddable uploads — on the site wordpressmeetup.com.

WHY IT MATTERS
Swap any dead or stale videos; keep only authoritative, non-clickbait Wordpress videos. Re-verify embeds.

HOW TO APPROACH IT
1. Find 6-10 authoritative, genuinely useful Wordpress videos that ALLOW embedding — verify each embed actually plays.
2. Curate them on /videos/ with short context, and drop anything clickbait, get-rich-quick, or low-substance.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Every embed plays, the set is authoritative and on-topic, and the page reuses the site's GA + AdSense.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.

You are working on ONE specific website: wordpressmeetup.com (live at https://wordpressmeetup.com/), a Wordpress site in the WholeTech network, served from /var/www/wordpressmeetup.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for wordpressmeetup.com and no other site — make all changes on wordpressmeetup.com. Act like a senior editor and web engineer who knows the Wordpress niche cold.

GOAL (on wordpressmeetup.com)
Verify affiliate links and ad placement resolve correctly — on the site wordpressmeetup.com.

WHY IT MATTERS
Spot-check Skimlinks / Amazon links and AdSense units; remove anything broken or low-value.

HOW TO APPROACH IT
1. Make the change — verify affiliate links resolve, or add the shared affiliate + AdSense setup.
2. Keep commerce low-key and well-integrated: subtle in-content links, not a bolted-on banner block.

CONSTRAINTS
- Match the site's existing design, fonts, layout and voice — never a generic AI-template look.
- Keep the HTML valid; do not break nav, internal links, the promo bar, analytics, or ad units.
- Use only real, current, accurately-attributed information — no fabricated facts, numbers, or sources.
- Reuse the site's existing Google Analytics and AdSense.

WHAT "DONE" LOOKS LIKE
- Links resolve and can earn, and placement is tasteful and does not hurt the reading experience.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

Think through the best approach first, then complete the whole task autonomously before stopping.