Affiliate Site Network (Build for Replication)

What we're building We run online-betting affiliate / top-list sites (Vietnamese market). Reference for the style and structure we want: https://www.amazingmike.nl/ — a "Top 10 betting platforms" ranking site: a numbered list of operator cards (logo, bonus highlights, CTA buttons) on top, followed by long-form SEO articles. We're starting with one site built on the Mercury theme (ThemeForest), but the real goal is bigger: We want to build a NETWORK of these sites — same structure, different domains, brands, content, and skins. We need a developer who builds the FIRST site in a way that makes spinning up the NEXT ones fast (re-skin + re-content, not rebuild-from-scratch). So this is not "click-configure one theme and leave." We want someone who thinks in systems and replication, and stays with us long-term to build and maintain the network. The core skill we're hiring for (read this carefully) Two layers, and we need both: 1. Build the site well (table stakes) Set up the Mercury theme (or similar casino/affiliate themes) to match the amazingmike-style layout: ranked operator list, review pages, bonus blocks, SEO article structure. Configure custom post types / ranking lists / affiliate CTA links (with rel="nofollow"). Vietnamese front-end, English admin (see "Language" below). Clean responsive build, fast load, SEO-sound markup. 2. Build it for replication (this is what makes you a fit vs. not) Keep a clean separation between the generic/reusable layer (layout system, components, design tokens, the site "engine") and the per-site layer (brand, colors, domain, content, operator list). So a second site = new child theme / new token set / new content — hours, not days. Not copy-paste-and-hand-edit every time. Document the setup so spinning up site #2, #3, #10 is a repeatable process. If you've built site networks / PBNs / multi-site affiliate setups before, that's exactly what we want — tell us about it. A developer who can only hand-build one site at a time is NOT a fit. We're hiring the person who can turn "build a site" into "stamp out sites." Language setup (important — don't overcomplicate) Front-end content = Vietnamese (we provide all content in Vietnamese). WordPress admin / back-end = English (our team reads English). Theme's fixed UI strings (buttons like "Play Now", "Read More") → translate to Vietnamese via Loco Translate (free) or the theme's own options. Do NOT use WPML. We don't need multilingual switching — just Vietnamese front + English admin. No paid multilingual plugin. What we provide / what you do We provide: theme licenses, hosting, all content (articles, operator logos, affiliate links), brand/color direction, operator lists. Content for the first site is ready within ~3 days. You do: the build, the replication system, ongoing maintenance, and spinning up new sites in the network as we grow. You don't write content or pick operators — that's us. To apply — answer these (evidence first; applications without links will be skipped) We weigh real, viewable work far above how well you describe your approach. A polished write-up with no links won't move forward. (Required — no links = skipped) Send links to a site network / multi-site setup you've actually built. Ideally 2–3 live sites that are clearly built from the same system (so we can see the replication is real, not a claim). For each: tell us which parts you personally built (vs. a team), and what was reused between sites vs. rebuilt. (Brief, supporting only) In a few sentences, how do you make site #2 fast — tokens, parent/child theme, config-driven, etc.? Keep it short; we judge mainly by the actual sites in Q1, not this paragraph. Have you used Mercury or other casino/affiliate themes (Coinflip, Spina…)? Optional — niche/theme don't matter, the replication track record does. Confirm: comfortable with Vietnamese front / English admin via Loco Translate, no WPML? Your long-term hourly availability (hours/week) and your rate. We read Q1 (your actual built sites) first. Everything else is secondary. If you can't show built work, this likely isn't the right role.