A prioritized, living to-do list for paulsfriends.com, built from this site's sources and current trends in Social Media. Click any row for the why & a ready-to-paste prompt — hit Copy prompt and paste it straight into your AI agent. Click a column header to sort.
| No | Rank | Cat | Date | Action |
|---|---|---|---|---|
| 1 | 99 | Security | 2026-06-19 | on paulsfriends.com Lock down sensitive data — nothing private is publicly reachable |
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. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Lock down sensitive data — nothing private is publicly reachable — on the site paulsfriends.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. | ||||
| 2 | 99 | Security | 2026-06-19 | on paulsfriends.com Make the site mythos-attack-proof — harden against automated & AI-agent abuse |
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. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site paulsfriends.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. | ||||
| 3 | 96 | Security | 2026-06-21 | on paulsfriends.com Verify HTTPS, security headers & a safe Agents-First surface |
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. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Verify HTTPS, security headers & a safe Agents-First surface — on the site paulsfriends.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. | ||||
| 4 | 95 | Flagship | 2026-06-22 | on paulsfriends.com Build the definitive Social Media cornerstone guide |
Create the single most useful, authoritative page on Social Media 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. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Build the definitive Social Media cornerstone guide — on the site paulsfriends.com. WHY IT MATTERS Create the single most useful, authoritative page on Social Media 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 Social Media — 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 Social Media 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. | ||||
| 5 | 94 | Flagship | 2026-06-23 | on paulsfriends.com Make the homepage genuinely distinctive — kill any generic-template feel |
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. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Make the homepage genuinely distinctive — kill any generic-template feel — on the site paulsfriends.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 Social Media — 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 Social Media 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. | ||||
| 6 | 93 | Flagship | 2026-06-23 | on paulsfriends.com Add an interactive tool and an email capture for Social Media |
Build one genuinely useful interactive element for Social Media (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. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Add an interactive tool and an email capture for Social Media — on the site paulsfriends.com. WHY IT MATTERS Build one genuinely useful interactive element for Social Media (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 Social Media — 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 Social Media 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. | ||||
| 7 | 91 | Popularity | 2026-06-25 | on paulsfriends.com Consent-based friend profile cards with story snippets |
Build the site as a curated circle: a card per friend (with their okay) carrying a photo, a one-paragraph story of how you met, and links to their public work. People reliably share pages about themselves; every profiled friend becomes a distributor to their own network. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Consent-based friend profile cards with story snippets — on the site paulsfriends.com. WHY IT MATTERS Build the site as a curated circle: a card per friend (with their okay) carrying a photo, a one-paragraph story of how you met, and links to their public work. People reliably share pages about themselves; every profiled friend becomes a distributor to their own network. (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. | ||||
| 8 | 87 | Trends | 2026-06-28 | on paulsfriends.com Publish: The platform algorithm shifts creators must adapt to |
Trending angle in Social Media. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Publish: The platform algorithm shifts creators must adapt to — on the site paulsfriends.com. WHY IT MATTERS Trending angle in Social Media. 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 Social Media 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. | ||||
| 9 | 87 | Trends | 2026-06-28 | on paulsfriends.com Publish: Short-video formats winning attention now |
Trending angle in Social Media. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Publish: Short-video formats winning attention now — on the site paulsfriends.com. WHY IT MATTERS Trending angle in Social Media. 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 Social Media 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. | ||||
| 10 | 84 | Trends | 2026-06-30 | on paulsfriends.com Publish: Creator-monetization changes this year |
Trending angle in Social Media. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Publish: Creator-monetization changes this year — on the site paulsfriends.com. WHY IT MATTERS Trending angle in Social Media. 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 Social Media 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. | ||||
| 11 | 83 | Popularity | 2026-06-30 | on paulsfriends.com Austin-scene memory pages tied to real eras |
Publish era pages — early Austin internet days, springnet years, coworking scene — naming the real venues and public events friends shared. This overlaps the texascoworking.com/JoshuaBaer memorial audience; nostalgia pages about a documented scene attract organic links from people who lived it. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Austin-scene memory pages tied to real eras — on the site paulsfriends.com. WHY IT MATTERS Publish era pages — early Austin internet days, springnet years, coworking scene — naming the real venues and public events friends shared. This overlaps the texascoworking.com/JoshuaBaer memorial audience; nostalgia pages about a documented scene attract organic links from people who lived it. (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. | ||||
| 12 | 82 | Popularity | 2026-07-01 | on paulsfriends.com Guestbook wall seeded from real greetings |
A visible guestbook where friends leave a line (moderated before publish), styled prominently on the homepage. Fresh human entries signal a living site, give returning visitors something new, and every signer typically shares the page onward — compounding reach with zero outreach cost. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Guestbook wall seeded from real greetings — on the site paulsfriends.com. WHY IT MATTERS A visible guestbook where friends leave a line (moderated before publish), styled prominently on the homepage. Fresh human entries signal a living site, give returning visitors something new, and every signer typically shares the page onward — compounding reach with zero outreach cost. (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. | ||||
| 13 | 82 | Revenue | 2026-07-01 | on paulsfriends.com Reunion and meetup travel via Travala affiliate |
When the site announces friend gatherings, include a clearly disclosed Travala booking link for out-of-towners' Austin stays. Travala is already live network-wide via /root/gen-travala.py; a gathering page is the one honest context where travel booking genuinely serves this site's visitors. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Reunion and meetup travel via Travala affiliate — on the site paulsfriends.com. WHY IT MATTERS When the site announces friend gatherings, include a clearly disclosed Travala booking link for out-of-towners' Austin stays. Travala is already live network-wide via /root/gen-travala.py; a gathering page is the one honest context where travel booking genuinely serves this site's visitors. (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. | ||||
| 14 | 81 | Trends | 2026-07-02 | on paulsfriends.com Publish: Posting cadence and timing backed by current data |
Trending angle in Social Media. A fresh, data-backed page on this draws search and gives the site a current spine. Link it from the homepage and /sources/. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Publish: Posting cadence and timing backed by current data — on the site paulsfriends.com. WHY IT MATTERS Trending angle in Social Media. 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 Social Media 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. | ||||
| 15 | 78 | Revenue | 2026-07-04 | on paulsfriends.com Gift-guide page with disclosed Amazon links |
A light 'gifts my friends actually loved' page — real items with a sentence on who liked what and why — tagged colinfirthfan-20 and disclosed. Personal recommendation pages convert far better than catalogs precisely because they're specific; keep it off the profile pages entirely. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Gift-guide page with disclosed Amazon links — on the site paulsfriends.com. WHY IT MATTERS A light 'gifts my friends actually loved' page — real items with a sentence on who liked what and why — tagged colinfirthfan-20 and disclosed. Personal recommendation pages convert far better than catalogs precisely because they're specific; keep it off the profile pages entirely. (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. | ||||
| 16 | 73 | Content | 2026-07-07 | on paulsfriends.com Deepen the main Social Media guide with current data and examples |
Audit the flagship page; replace anything stale, add concrete numbers and a clear next step. Depth is what separates this from a thin template. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Deepen the main Social Media guide with current data and examples — on the site paulsfriends.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 Social Media 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 Social Media. - 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. | ||||
| 17 | 72 | Sources | 2026-07-08 | on paulsfriends.com Add source: Buffer |
Scheduling and analytics. Authoritative Social Media reference not yet linked on /sources/ — add it with a one-line note. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Add source: Buffer — on the site paulsfriends.com. WHY IT MATTERS Scheduling and analytics. Authoritative Social Media reference not yet linked on /sources/ — add it with a one-line note. HOW TO APPROACH IT 1. Open the source and confirm it is authoritative and genuinely relevant to Social Media. 2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates. 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 link works, is annotated and well-placed, and is a reference a real Social Media expert would trust. - 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. | ||||
| 18 | 72 | Sources | 2026-07-08 | on paulsfriends.com Add source: Later |
Visual content planning. Authoritative Social Media reference not yet linked on /sources/ — add it with a one-line note. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Add source: Later — on the site paulsfriends.com. WHY IT MATTERS Visual content planning. Authoritative Social Media reference not yet linked on /sources/ — add it with a one-line note. HOW TO APPROACH IT 1. Open the source and confirm it is authoritative and genuinely relevant to Social Media. 2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates. 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 link works, is annotated and well-placed, and is a reference a real Social Media expert would trust. - 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. | ||||
| 19 | 70 | Revenue | 2026-07-10 | on paulsfriends.com Newsletter list for circle announcements |
Embed wholetech.com/newsletter/widget.js as 'hear about the next get-together'. The list is the quiet asset: it powers reunion attendance (which powers the Travala page), keeps the circle warm between updates, and costs nothing since the widget infrastructure already runs network-wide. One short note per month is plenty. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Newsletter list for circle announcements — on the site paulsfriends.com. WHY IT MATTERS Embed wholetech.com/newsletter/widget.js as 'hear about the next get-together'. The list is the quiet asset: it powers reunion attendance (which powers the Travala page), keeps the circle warm between updates, and costs nothing since the widget infrastructure already runs network-wide. One short note per month is plenty. (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. | ||||
| 20 | 69 | Design | 2026-07-10 | on paulsfriends.com Scrapbook aesthetic: polaroid frames and tape corners |
Art-direct as a physical photo album: polaroid-white borders with handwritten-style captions, washi-tape corner accents, slightly rotated card stacks, ballpoint-doodle dividers. A friends site should feel handmade and warm; scrapbook vernacular says 'personal archive' where a grid of cards says 'directory'. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Scrapbook aesthetic: polaroid frames and tape corners — on the site paulsfriends.com. WHY IT MATTERS Art-direct as a physical photo album: polaroid-white borders with handwritten-style captions, washi-tape corner accents, slightly rotated card stacks, ballpoint-doodle dividers. A friends site should feel handmade and warm; scrapbook vernacular says 'personal archive' where a grid of cards says 'directory'. (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. | ||||
| 21 | 67 | Sources | 2026-07-12 | on paulsfriends.com Build /sources/ out to at least 10 authoritative links |
Only 5 sources detected. A deep, current /sources/ page is a ranking and trust signal; pad it from the curated and popular catalogs. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Build /sources/ out to at least 10 authoritative links — on the site paulsfriends.com. WHY IT MATTERS Only 5 sources detected. A deep, current /sources/ page is a ranking and trust signal; pad it from the curated and popular catalogs. HOW TO APPROACH IT 1. Open the source and confirm it is authoritative and genuinely relevant to Social Media. 2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates. 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 link works, is annotated and well-placed, and is a reference a real Social Media expert would trust. - 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. | ||||
| 22 | 66 | AEO | 2026-07-12 | on paulsfriends.com Person schema with sameAs to public profiles |
Add Person JSON-LD to each consenting friend's card with sameAs pointing to their public sites and profiles, plus an about-page FAQ explaining what the site is. This helps assistants correctly associate the circle's public figures and cite the site, and run af-deploy.py toward 90+. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Person schema with sameAs to public profiles — on the site paulsfriends.com. WHY IT MATTERS Add Person JSON-LD to each consenting friend's card with sameAs pointing to their public sites and profiles, plus an about-page FAQ explaining what the site is. This helps assistants correctly associate the circle's public figures and cite the site, and run af-deploy.py toward 90+. (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. | ||||
| 23 | 66 | Design | 2026-07-12 | on paulsfriends.com Friendship-map spread showing where everyone landed |
A designed map spread — pushpin markers, string-line connections back to Austin, postcard-styled tooltips per friend — showing where the circle lives now. It's the album's centerfold: instantly understandable, endlessly updatable, and the page friends screenshot and send each other. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Friendship-map spread showing where everyone landed — on the site paulsfriends.com. WHY IT MATTERS A designed map spread — pushpin markers, string-line connections back to Austin, postcard-styled tooltips per friend — showing where the circle lives now. It's the album's centerfold: instantly understandable, endlessly updatable, and the page friends screenshot and send each other. (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. | ||||
| 24 | 66 | Sources | 2026-07-12 | on paulsfriends.com Add source: Hootsuite Blog |
Strategy and trends. Authoritative Social Media reference not yet linked on /sources/ — add it with a one-line note. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Add source: Hootsuite Blog — on the site paulsfriends.com. WHY IT MATTERS Strategy and trends. Authoritative Social Media reference not yet linked on /sources/ — add it with a one-line note. HOW TO APPROACH IT 1. Open the source and confirm it is authoritative and genuinely relevant to Social Media. 2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates. 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 link works, is annotated and well-placed, and is a reference a real Social Media expert would trust. - 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. | ||||
| 25 | 64 | Content | 2026-07-14 | on paulsfriends.com Add an FAQ answering the top questions in Social Media |
Pull the real questions people ask in Social Media and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Add an FAQ answering the top questions in Social Media — on the site paulsfriends.com. WHY IT MATTERS Pull the real questions people ask in Social Media and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Social Media 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 Social Media. - 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. | ||||
| 26 | 64 | Product | 2026-07-14 | on paulsfriends.com RSVP form for gatherings, notifications drafted only |
A gathering RSVP form (name, headcount, note) whose submissions are written as Gmail DRAFTS for Paul's review — never auto-sent. It turns the site from a static album into the circle's working coordination tool, which is the strongest reason friends will keep coming back. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) RSVP form for gatherings, notifications drafted only — on the site paulsfriends.com. WHY IT MATTERS A gathering RSVP form (name, headcount, note) whose submissions are written as Gmail DRAFTS for Paul's review — never auto-sent. It turns the site from a static album into the circle's working coordination tool, which is the strongest reason friends will keep coming back. (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. | ||||
| 27 | 64 | Sources | 2026-07-14 | on paulsfriends.com Add source: Social Media Examiner |
Tactics and research. Authoritative Social Media reference not yet linked on /sources/ — add it with a one-line note. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Add source: Social Media Examiner — on the site paulsfriends.com. WHY IT MATTERS Tactics and research. Authoritative Social Media reference not yet linked on /sources/ — add it with a one-line note. HOW TO APPROACH IT 1. Open the source and confirm it is authoritative and genuinely relevant to Social Media. 2. Add it to /sources/ with a one-line annotation explaining why it matters, placed in the right group, with no duplicates. 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 link works, is annotated and well-placed, and is a reference a real Social Media expert would trust. - 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. | ||||
| 28 | 63 | Fresh | 2026-07-14 | on paulsfriends.com Add a /live/ news feed for Social Media |
An auto-publishing, attributed Google-News feed keeps the site fresh daily and reuses the existing GA + AdSense. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Add a /live/ news feed for Social Media — on the site paulsfriends.com. WHY IT MATTERS An auto-publishing, attributed Google-News feed keeps the site fresh daily and reuses the existing GA + AdSense. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Social Media: 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 Social Media 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. | ||||
| 29 | 57 | SEO | 2026-07-19 | on paulsfriends.com Submit updated URLs via IndexNow and refresh the sitemap |
Ping IndexNow for new and changed pages so they're discovered fast; confirm the sitemap lists /act/, /sources/, /videos/. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Submit updated URLs via IndexNow and refresh the sitemap — on the site paulsfriends.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. | ||||
| 30 | 56 | Design | 2026-07-19 | on paulsfriends.com Apply a WT-Skins kit to lift the design and Agents-First score |
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. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Apply a WT-Skins kit to lift the design and Agents-First score — on the site paulsfriends.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. | ||||
| 31 | 46 | SEO | 2026-07-26 | on paulsfriends.com Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Add Article + FAQ structured data — on the site paulsfriends.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. | ||||
| 32 | 46 | SEO | 2026-07-26 | on paulsfriends.com Strengthen internal links between the core, /sources/ and this worksheet |
A tight internal-link web spreads authority and keeps visitors moving through the site. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Strengthen internal links between the core, /sources/ and this worksheet — on the site paulsfriends.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. | ||||
| 33 | 42 | Video | 2026-07-29 | on paulsfriends.com Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Social Media videos. Re-verify embeds. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Refresh the /videos/ playlist with current, embeddable uploads — on the site paulsfriends.com. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Social Media videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Social Media 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. | ||||
| 34 | 39 | Monetize | 2026-07-31 | on paulsfriends.com Add the network affiliate + AdSense setup |
Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup. ★ Copy-paste prompt for paulsfriends.com You are working on ONE specific website: paulsfriends.com (live at https://paulsfriends.com/), a Social Media site in the WholeTech network, served from /var/www/paulsfriends.com/ on the droplet (ssh root@143.198.182.180). Every instruction below is for paulsfriends.com and no other site — make all changes on paulsfriends.com. Act like a senior editor and web engineer who knows the Social Media niche cold. GOAL (on paulsfriends.com) Add the network affiliate + AdSense setup — on the site paulsfriends.com. WHY IT MATTERS Inject the shared Skimlinks script and the AdSense unit so existing traffic earns; one-time setup. 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. | ||||