A prioritized, living to-do list for webarter.net, built from this site's sources and current trends in Creative Coding. 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 webarter.net 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 webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Make the site mythos-attack-proof — harden against automated & AI-agent abuse — on the site webarter.net. 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. | ||||
| 2 | 99 | Security | 2026-06-19 | on webarter.net 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 webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Verify HTTPS, security headers & a safe Agents-First surface — on the site webarter.net. 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. | ||||
| 3 | 98 | Security | 2026-06-20 | on webarter.net 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 webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Lock down sensitive data — nothing private is publicly reachable — on the site webarter.net. 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. | ||||
| 4 | 95 | Flagship | 2026-06-22 | on webarter.net Build the definitive Creative Coding cornerstone guide |
Create the single most useful, authoritative page on Creative Coding 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 webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Build the definitive Creative Coding cornerstone guide — on the site webarter.net. WHY IT MATTERS Create the single most useful, authoritative page on Creative Coding 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 Creative Coding — 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 Creative Coding 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 | 95 | Flagship | 2026-06-22 | on webarter.net 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 webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Make the homepage genuinely distinctive — kill any generic-template feel — on the site webarter.net. 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 Creative Coding — 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 Creative Coding 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 | 94 | Flagship | 2026-06-23 | on webarter.net Add an interactive tool and an email capture for Creative Coding |
Build one genuinely useful interactive element for Creative Coding (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 webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Add an interactive tool and an email capture for Creative Coding — on the site webarter.net. WHY IT MATTERS Build one genuinely useful interactive element for Creative Coding (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 Creative Coding — 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 Creative Coding 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 | 93 | Trends | 2026-06-23 | on webarter.net Publish: A current, data-backed explainer in Creative Coding |
Trending angle in Creative Coding. 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 webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Publish: A current, data-backed explainer in Creative Coding — on the site webarter.net. WHY IT MATTERS Trending angle in Creative Coding. 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 Creative Coding 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. | ||||
| 8 | 91 | Popularity | 2026-06-25 | on webarter.net Monthly generative-art challenge with gallery |
Run a themed monthly creative-coding challenge — one constraint, one canvas — publishing every submission in a gallery with source visible. Challenges are how the p5.js and shader communities organize attention; hosting one earns recurring participation and inbound links from entrants sharing work. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Monthly generative-art challenge with gallery — on the site webarter.net. WHY IT MATTERS Run a themed monthly creative-coding challenge — one constraint, one canvas — publishing every submission in a gallery with source visible. Challenges are how the p5.js and shader communities organize attention; hosting one earns recurring participation and inbound links from entrants sharing work. (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. | ||||
| 9 | 87 | Popularity | 2026-06-28 | on webarter.net Annotated source walkthroughs of classic sketches |
Deep walkthroughs of landmark generative pieces — flow fields, reaction-diffusion, ten-print variations — with line-by-line annotation and live-editable canvases. Creative coders search for exactly these techniques; annotated, runnable explanations become the reference pages tutorials link to. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Annotated source walkthroughs of classic sketches — on the site webarter.net. WHY IT MATTERS Deep walkthroughs of landmark generative pieces — flow fields, reaction-diffusion, ten-print variations — with line-by-line annotation and live-editable canvases. Creative coders search for exactly these techniques; annotated, runnable explanations become the reference pages tutorials link to. (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. | ||||
| 10 | 85 | Trends | 2026-06-29 | on webarter.net Publish: The question your Creative Coding audience is searching most right now |
Trending angle in Creative Coding. 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 webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Publish: The question your Creative Coding audience is searching most right now — on the site webarter.net. WHY IT MATTERS Trending angle in Creative Coding. 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 Creative Coding 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 webarter.net Curated creative-coding videos on /videos/ |
Build the /videos/ page with the best generative-art talks and coding-train-style tutorials, embeddability verified via check-embed.mjs, organized by technique. Video is where this discipline is actually taught; careful curation makes the site a syllabus, not a blog. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Curated creative-coding videos on /videos/ — on the site webarter.net. WHY IT MATTERS Build the /videos/ page with the best generative-art talks and coding-train-style tutorials, embeddability verified via check-embed.mjs, organized by technique. Video is where this discipline is actually taught; careful curation makes the site a syllabus, not a blog. (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 | 83 | Trends | 2026-06-30 | on webarter.net Publish: A 'what changed in 2026' round-up for Creative Coding |
Trending angle in Creative Coding. 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 webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Publish: A 'what changed in 2026' round-up for Creative Coding — on the site webarter.net. WHY IT MATTERS Trending angle in Creative Coding. 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 Creative Coding 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. | ||||
| 13 | 80 | Revenue | 2026-07-03 | on webarter.net Creative-coder bookshelf with Amazon links |
A curated shelf — Nature of Code, Generative Design, shader references, pen-plotter supplies — tagged colinfirthfan-20 with one honest line on who each serves. This audience genuinely buys books and plotters; a specific shelf beats scattered links. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Creative-coder bookshelf with Amazon links — on the site webarter.net. WHY IT MATTERS A curated shelf — Nature of Code, Generative Design, shader references, pen-plotter supplies — tagged colinfirthfan-20 with one honest line on who each serves. This audience genuinely buys books and plotters; a specific shelf beats scattered links. (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 | 76 | Revenue | 2026-07-05 | on webarter.net AdSense on tutorial walkthrough pages only |
Enable pub-7759195213529699 on the long-form technique walkthroughs — genuine dwell-time pages — while keeping galleries and the challenge pristine. Art spaces stay gallery-clean; the teaching library carries the monetization. Junk categories already blocked account-wide. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) AdSense on tutorial walkthrough pages only — on the site webarter.net. WHY IT MATTERS Enable pub-7759195213529699 on the long-form technique walkthroughs — genuine dwell-time pages — while keeping galleries and the challenge pristine. Art spaces stay gallery-clean; the teaching library carries the monetization. Junk categories already blocked account-wide. (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. | ||||
| 15 | 71 | Content | 2026-07-09 | on webarter.net Deepen the main Creative Coding 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 webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Deepen the main Creative Coding guide with current data and examples — on the site webarter.net. 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 Creative Coding 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 Creative Coding. - 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. | ||||
| 16 | 71 | Design | 2026-07-09 | on webarter.net The site itself renders as generative art |
Art-direct by demonstration: header backgrounds are live generative canvases (seeded per visit, source linked), dividers are plotted-line SVG output, the 404 page is a one-off sketch. On a creative-coding site, the medium must be the portfolio — templates are disqualifying. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) The site itself renders as generative art — on the site webarter.net. WHY IT MATTERS Art-direct by demonstration: header backgrounds are live generative canvases (seeded per visit, source linked), dividers are plotted-line SVG output, the 404 page is a one-off sketch. On a creative-coding site, the medium must be the portfolio — templates are disqualifying. (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. | ||||
| 17 | 70 | Revenue | 2026-07-10 | on webarter.net Challenge digest email via newsletter widget |
Wire wholetech.com/newsletter/widget.js to a monthly digest — new challenge theme, standout submissions, one technique link. Challenge cadence gives email a natural rhythm this audience opts into; signups draft notifications for review, never auto-send, per network rule. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Challenge digest email via newsletter widget — on the site webarter.net. WHY IT MATTERS Wire wholetech.com/newsletter/widget.js to a monthly digest — new challenge theme, standout submissions, one technique link. Challenge cadence gives email a natural rhythm this audience opts into; signups draft notifications for review, never auto-send, per network rule. (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. | ||||
| 18 | 69 | Content | 2026-07-10 | on webarter.net Add an FAQ answering the top questions in Creative Coding |
Pull the real questions people ask in Creative Coding and answer them plainly. Mark up with FAQ schema for rich results. ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Add an FAQ answering the top questions in Creative Coding — on the site webarter.net. WHY IT MATTERS Pull the real questions people ask in Creative Coding and answer them plainly. Mark up with FAQ schema for rich results. HOW TO APPROACH IT 1. Audit the flagship Creative Coding 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 Creative Coding. - 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. | ||||
| 19 | 69 | Design | 2026-07-10 | on webarter.net Gallery cards with visible seed and parameters |
Every gallery piece shows its seed value and key parameters in monospace beneath the canvas, with a 're-roll' control where feasible. Exposing the machinery is the aesthetic of this community — reproducibility as decoration — and it invites the tinkering that drives return visits. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Gallery cards with visible seed and parameters — on the site webarter.net. WHY IT MATTERS Every gallery piece shows its seed value and key parameters in monospace beneath the canvas, with a 're-roll' control where feasible. Exposing the machinery is the aesthetic of this community — reproducibility as decoration — and it invites the tinkering that drives return visits. (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. | ||||
| 20 | 64 | Product | 2026-07-14 | on webarter.net Zero-setup sketch playground with shareable permalinks |
An in-browser editor preloaded with the site's walkthrough sketches, saving to hash-based permalinks — no accounts, no backend state. Remixing walkthrough code and sharing the result is the natural loop of this community, and every shared permalink is inbound traffic. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Zero-setup sketch playground with shareable permalinks — on the site webarter.net. WHY IT MATTERS An in-browser editor preloaded with the site's walkthrough sketches, saving to hash-based permalinks — no accounts, no backend state. Remixing walkthrough code and sharing the result is the natural loop of this community, and every shared permalink is inbound traffic. (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. | ||||
| 21 | 61 | AEO | 2026-07-16 | on webarter.net Glossary of generative techniques with definitions |
A structured glossary — Perlin noise, L-systems, Voronoi, SDF — each with DefinedTerm schema, one-paragraph plain definition, and a linked runnable demo. Technique definitions are precisely what coding assistants cite; clean structure earns those citations. Confirm 90+ via af-deploy.py. (Fable enhanced action — also on the global worksheet.) ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Glossary of generative techniques with definitions — on the site webarter.net. WHY IT MATTERS A structured glossary — Perlin noise, L-systems, Voronoi, SDF — each with DefinedTerm schema, one-paragraph plain definition, and a linked runnable demo. Technique definitions are precisely what coding assistants cite; clean structure earns those citations. Confirm 90+ via af-deploy.py. (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. | ||||
| 22 | 57 | Fresh | 2026-07-19 | on webarter.net Keep the live / news feed updated on cadence (2×/day) |
Confirm the cron is publishing fresh, attributed Creative Coding items and pinging IndexNow each run. ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Keep the live / news feed updated on cadence (2×/day) — on the site webarter.net. WHY IT MATTERS Confirm the cron is publishing fresh, attributed Creative Coding items and pinging IndexNow each run. HOW TO APPROACH IT 1. Confirm or set up the auto-publishing /live/ or /news/ feed for Creative Coding: 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 Creative Coding 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. | ||||
| 23 | 56 | Design | 2026-07-19 | on webarter.net 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 webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Apply a WT-Skins kit to lift the design and Agents-First score — on the site webarter.net. 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. | ||||
| 24 | 54 | SEO | 2026-07-21 | on webarter.net 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 webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Submit updated URLs via IndexNow and refresh the sitemap — on the site webarter.net. 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. | ||||
| 25 | 47 | SEO | 2026-07-26 | on webarter.net Add Article + FAQ structured data |
Schema.org markup earns richer results and helps answer-engines cite the page correctly. ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Add Article + FAQ structured data — on the site webarter.net. 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. | ||||
| 26 | 46 | Video | 2026-07-26 | on webarter.net Refresh the /videos/ playlist with current, embeddable uploads |
Swap any dead or stale videos; keep only authoritative, non-clickbait Creative Coding videos. Re-verify embeds. ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Refresh the /videos/ playlist with current, embeddable uploads — on the site webarter.net. WHY IT MATTERS Swap any dead or stale videos; keep only authoritative, non-clickbait Creative Coding videos. Re-verify embeds. HOW TO APPROACH IT 1. Find 6-10 authoritative, genuinely useful Creative Coding 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. | ||||
| 27 | 45 | SEO | 2026-07-27 | on webarter.net 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 webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Strengthen internal links between the core, /sources/ and this worksheet — on the site webarter.net. 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. | ||||
| 28 | 42 | Monetize | 2026-07-29 | on webarter.net Verify affiliate links and ad placement resolve correctly |
Spot-check Skimlinks / Amazon links and AdSense units; remove anything broken or low-value. ★ Copy-paste prompt for webarter.net You are working on ONE specific website: webarter.net (live at https://webarter.net/), a Creative Coding site in the WholeTech network, served from /var/www/webarter.net/ on the droplet (ssh root@143.198.182.180). Every instruction below is for webarter.net and no other site — make all changes on webarter.net. Act like a senior editor and web engineer who knows the Creative Coding niche cold. GOAL (on webarter.net) Verify affiliate links and ad placement resolve correctly — on the site webarter.net. 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. | ||||