What to do next on this site

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

GOAL (on jane.buildercamp.com)
Build the definitive Home Building cornerstone guide — on the site jane.buildercamp.com.

WHY IT MATTERS
Create the single most useful, authoritative page on Home Building 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 Home Building — 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 Home Building resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

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

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

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

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

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

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

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

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

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

GOAL (on jane.buildercamp.com)
Make the homepage genuinely distinctive — kill any generic-template feel — on the site jane.buildercamp.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 Home Building — 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 Home Building resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

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

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

GOAL (on jane.buildercamp.com)
Add an interactive tool and an email capture for Home Building — on the site jane.buildercamp.com.

WHY IT MATTERS
Build one genuinely useful interactive element for Home Building (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 Home Building — 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 Home Building resource on the site — deep, accurate, and a pleasure to read, not a thin template.
- Every factual claim is current and traceable to a real, linked source.
- It's discoverable: linked from the homepage, in the sitemap, and submitted via IndexNow.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

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

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

GOAL (on jane.buildercamp.com)
Publish: The energy-code changes builders must meet in 2026 — on the site jane.buildercamp.com.

WHY IT MATTERS
Trending angle in Home Building. 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 Home Building reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

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

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

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

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

GOAL (on jane.buildercamp.com)
Publish: Material costs and lead times right now — on the site jane.buildercamp.com.

WHY IT MATTERS
Trending angle in Home Building. 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 Home Building reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

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

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

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

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

GOAL (on jane.buildercamp.com)
Publish weekend skill-builder project series — on the site jane.buildercamp.com.

WHY IT MATTERS
Run a numbered series of beginner-safe weekend projects — fixing a running toilet, hanging shelves in studs, caulking like a pro — written in the encouraging, women-forward voice of the Be Jane lineage this site inherits. Sequenced skill-building content earns subscribers, not just one-visit searchers. (Fable enhanced action — also on the global worksheet.)

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

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

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

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

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

GOAL (on jane.buildercamp.com)
Link the Be Jane heritage hub — on the site jane.buildercamp.com.

WHY IT MATTERS
Cross-link with the wholetech.com/bejane rebuild and frame this subdomain as the living continuation of the Be Jane women's home-improvement mission — relevant to the Melissa Morman and BDX conversations already underway. Heritage plus active content gives the pitch a working demonstration site. (Fable enhanced action — also on the global worksheet.)

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

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

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

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

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

GOAL (on jane.buildercamp.com)
Build /videos/ of beginner tool tutorials — on the site jane.buildercamp.com.

WHY IT MATTERS
Curate embeddable tutorials on first tools — drill basics, stud finders, level use — verified with check-embed.mjs, dropping embed=false entries and renumbering. Beginners overwhelmingly learn tools by watching; pairing each written project with vetted video keeps them on-site through the whole first project. (Fable enhanced action — also on the global worksheet.)

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

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

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

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

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

GOAL (on jane.buildercamp.com)
Publish: Prefab and panelized methods gaining ground — on the site jane.buildercamp.com.

WHY IT MATTERS
Trending angle in Home Building. 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 Home Building reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

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

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

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

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

GOAL (on jane.buildercamp.com)
Recommend starter tool kits with Amazon — on the site jane.buildercamp.com.

WHY IT MATTERS
Publish an honest first-toolbox guide — cordless drill, stud finder, level, tape, safety glasses — with Amazon tag colinfirthfan-20 and a plain-spoken reason per pick. New homeowners buy a first kit within weeks of closing; a trusted starter list converts better than any category page. (Fable enhanced action — also on the global worksheet.)

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

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

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

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

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

GOAL (on jane.buildercamp.com)
Run AdSense on project guide pages — on the site jane.buildercamp.com.

WHY IT MATTERS
Enable shared AdSense pub-7759195213529699 on project and how-to pages where home-improvement advertisers bid consistently well. Place units at natural rest points between project steps, never inside a numbered sequence, so a first-timer mid-repair never loses her place — completed projects create returning readers. (Fable enhanced action — also on the global worksheet.)

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

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

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

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

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

GOAL (on jane.buildercamp.com)
Deepen the main Home Building guide with current data and examples — on the site jane.buildercamp.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 Home Building 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 Home Building.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

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

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

GOAL (on jane.buildercamp.com)
Publish: Labor-shortage workarounds that work — on the site jane.buildercamp.com.

WHY IT MATTERS
Trending angle in Home Building. 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 Home Building reader, and a clear next step.
3. Cite and link each source inline and date the piece so its freshness is obvious.
4. Link it from the homepage and /sources/, and submit it via IndexNow.

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

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

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

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

GOAL (on jane.buildercamp.com)
Adopt painter's-tape and blueprint art direction — on the site jane.buildercamp.com.

WHY IT MATTERS
Design from the first-project visual world: painter's-tape blue as the accent color with actual tape-strip UI elements, blueprint-grid paper backgrounds, and hand-tool linework icons. Approachable craft-plan aesthetics say 'you can do this' — the opposite of intimidating contractor-orange big-box branding. (Fable enhanced action — also on the global worksheet.)

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

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

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

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

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

GOAL (on jane.buildercamp.com)
Offer one-project-a-week email via widget — on the site jane.buildercamp.com.

WHY IT MATTERS
Embed https://wholetech.com/newsletter/widget.js offering a weekly single-project email matched to the skill-builder series. A gentle recurring nudge fits this audience's build-confidence-gradually journey and steadily compounds repeat traffic. All sends remain Gmail drafts for Paul's review — never auto-sent, 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.

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

GOAL (on jane.buildercamp.com)
Add an FAQ answering the top questions in Home Building — on the site jane.buildercamp.com.

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

HOW TO APPROACH IT
1. Audit the flagship Home Building 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 Home Building.
- No filler and no fabricated specifics — every number is current and sourced.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

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

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

GOAL (on jane.buildercamp.com)
Build /sources/ out to at least 10 authoritative links — on the site jane.buildercamp.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 Home Building.
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 Home Building 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.

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

GOAL (on jane.buildercamp.com)
Add HowTo schema to every project — on the site jane.buildercamp.com.

WHY IT MATTERS
Mark up complete HowTo structured data — steps, tools, materials, time estimates — on each project guide. Home-repair questions are among the heaviest answer-engine categories, and step-structured markup gets this site cited for the exact 'how do I fix' queries its audience asks first. (Fable enhanced action — also on the global worksheet.)

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

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

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

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

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

GOAL (on jane.buildercamp.com)
Style projects as paint-chip difficulty cards — on the site jane.buildercamp.com.

WHY IT MATTERS
Present each project as a paint-swatch-style card — a color chip encoding difficulty, time and tool-count printed like a chip's specs, fan-deck stacking on index pages. The paint-chip metaphor is instantly familiar from hardware stores and makes browsing projects feel like picking colors. (Fable enhanced action — also on the global worksheet.)

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

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

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

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

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

GOAL (on jane.buildercamp.com)
Add a /live/ news feed for Home Building — on the site jane.buildercamp.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 Home Building: 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 Home Building items on schedule and is discovered quickly.
- Deployed to the droplet and verified on the live URL (screenshot from a Windows machine — never run a browser on the droplet), with a short summary of exactly what changed.

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

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

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

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

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

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

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

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

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

GOAL (on jane.buildercamp.com)
Build project planner worksheet table — on the site jane.buildercamp.com.

WHY IT MATTERS
Ship a sortable planner table of all projects — difficulty, time, tool list, estimated material cost range — with rows opening into the full guides, per the network worksheet pattern. Letting a new homeowner sort by 'one hour, three tools' turns the archive into a decision tool. (Fable enhanced action — also on the global worksheet.)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

GOAL (on jane.buildercamp.com)
Add the network affiliate + AdSense setup — on the site jane.buildercamp.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.