The network hub for ~150 properties since 1996. Below: where the network goes next, the meta-tooling that should exist, and the unsexy infrastructure plays that compound.
High-leverage scope expansions ordered by impact-to-effort ratio.
Codify the visual language (gold/dark editorial, the Marquee bulb-marquee strip, the database schema-table aesthetic) into a shared CSS file every site imports. One change updates all 150 sites.
One Grafana or Plausible dashboard showing traffic, conversion, and Mythos-readiness across all properties. Currently each site reports separately.
sitemap.wholetech.com exists. Extend it: a daily-regenerated JSON feed of every property, status, last-update, traffic tier — other tools consume the feed.
llms.txt + JSON-LD coverage now near 100%. Next: a network-wide robots.txt strategy, AI-bot allowlist policy, citation tracker so we see when LLMs cite the network.
7-link subnav rolled out to most sites. Audit the remaining 5%; finish the rollout.
A consistent footer block listing 6-8 sister properties on every page. Currently uneven.
A reusable mobile-only sticky CTA pattern (RSS, newsletter, contact) other sites can adopt.
A single landing page per property summarizing audience, scope, monetization, status. Internal dashboard, public-friendly.
Why so many sites? How are they related? What's the editorial standard? Single page, builds trust.
A monthly email/RSS roundup of what's new across every property.
Copy any prompt into Claude. Replace bracketed placeholders before running. Framework follows the Opus 4.7 guide at claude.wholetech.com/prompting/.
<context> [Describe the site's current scope and the specific gap this prompt targets — replace with site-specific context before running.] </context> <instructions> Write a 1200-word /about/ essay for wholetech.com explaining the network: scope, history (since 1996), editorial standards, monetization philosophy, and the role each major property plays. </instructions> <constraints> - No preamble. Lead with the strongest claim. - Cite at least one external source per major claim. - Match the site's editorial voice. - Year-anchor any title that could date. </constraints> <output_format> H1, lede paragraph, 4-6 H2 sections, short conclusion. </output_format>
<context> [Describe the site's current scope and the specific gap this prompt targets — replace with site-specific context before running.] </context> <instructions> Audit one property's JSON-LD coverage against the network standard (WebSite + Organization + main entity type). Output the patched HTML for the head. </instructions> <constraints> - No preamble. Lead with the strongest claim. - Cite at least one external source per major claim. - Match the site's editorial voice. - Year-anchor any title that could date. </constraints> <output_format> H1, lede paragraph, 4-6 H2 sections, short conclusion. </output_format>
<context> [Replace with the specific topic, source material, and current angle before running.] </context> <instructions> Write the monthly network roundup: 3-5 paragraphs covering what shipped across all properties this month, what's in progress, and what's queued. </instructions> <constraints> - Voice: site's house style (read 2-3 existing pieces if needed). - 600-900 words unless the format specifies otherwise. - No filler, no preamble. </constraints>
<context> [Replace with the specific topic, source material, and current angle before running.] </context> <instructions> A new property launched. Write the 500-word announcement explaining what it is, who it serves, and why it slots into the network. </instructions> <constraints> - Voice: site's house style (read 2-3 existing pieces if needed). - 600-900 words unless the format specifies otherwise. - No filler, no preamble. </constraints>
Once a year, publish actual traffic, monetization, and lessons-learned across the network. Transparency as a brand asset.
A common affiliate-disclosure footer on every commerce-adjacent property. One legal review, network-wide.
A downloadable press kit for the network as a whole — useful when properties are mentioned in trade press.