meshgen,
a content network with revenue gravity.
A six-node SEO content network anchored by searchengineu.com. Blog, newsletter, reviews, products, tool, social --- routed so traffic and intent move between them on purpose.
meshgen is a deliberate cross-linking topology, not a single property. Six nodes (niche authority blog, newsletter, comparison/review hub, digital products, free AI ROI calculator, social bridge) hand off audience and intent in defined directions. The doctrine, the architecture, and the editorial Definition of Done are scoped to docs/*.md --- one file per concern, no duplication.
Tech scope
- Monorepo by node:
nodes/<slug>/for per-node assets,shared/for cross-node libraries,docs/for network-level doctrine. - Live execution state is queried (
configure_site.py status, WP REST,git log) rather than tracked in markdown — the source of truth is what is actually deployed. - Article drafts:
nodes/<slug>/articles/NN-slug.md; per-node secrets in.envat the node root, gitignored. - Generated images are gitignored; regenerated from the wrapper scripts (
shared/scripts/gen_featured_image.py,gen_pin.py) rather than committed as pixels.
Network topology
Cross-node hand-offs are deliberate, not opportunistic:
- N1 → N2 — content upgrades and email capture.
- N1 → N3 — product mentions feeding the comparison/review hub.
- N1 → N4 — resource recommendations.
- N3 → N1 — educational deep-links from review pages.
- N5 → N3 — AI ROI calculator results recommend specific tools.
- N6 → N1/N2/N3 — social bridges feed traffic upward.
When writing an article or building a page, the appropriate cross-node link is placed by hand — not by a plugin — so revenue isn''t stranded at one node.
Voice
Articles publish under the Marcus Hale byline. The voice guide is authoritative, data-driven, direct: specific numbers over adjectives, first-person on testing experience only, banned vocabulary list (no "mind-blowing", "game-changer", "revolutionary"). The full guide lives in docs/voice.md.
Surface
The mesh is not a CMS. Each node is an independently-publishable property — blog, newsletter, reviews catalog, products, tool, and social presence — that links back to and from the anchor (searchengineu.com). Authoring is markdown plus the local image worker (flux) for featured images and pin assets. Cross-linking between nodes is generated rather than hand-maintained, which keeps the mesh shape honest as nodes evolve. As of this writing, only the anchor is built; the other five are planned and named, not running.
Constraints
The hard constraint is that no node may be a single point of failure for any other — if the social property goes dark, the rest of the mesh keeps publishing without it. Anchor-as-hub is a working model, not a final one: the next ratchet is anchor-of-anchors, where two or three meshes share a topology to spread risk further. Every node is dual-format (web + RSS) and the publishing pipeline does not assume web is canonical.