motnas.org — Audited Product Plan

Current Reality

• This folder contains only plan.md.
• The concrete implementation evidence lives in motnas.com/, which already has a Cloudflare-native Worker, D1, R2, and scheduled ingestion flow.
• motnas.org should therefore not be treated as a blank standalone stack. It should become a distinct editorial surface on top of the same underlying Cloudflare system.

Product Role

• motnas.org should be the knowledge and archive site for segala tentang motor nasional dari dulu sampai sekarang.
• The focus is not live race updates.
• The focus is:
  • sejarah motor nasional
  • merek, pabrikan, dan model dari masa ke masa
  • timeline industri roda dua Indonesia
  • regulasi, tren pasar, dan budaya motor
  • tokoh, komunitas, balap, dan momen penting
  • arsip foto, katalog, dan artikel referensi

Information Architecture

• Beranda: ringkasan sejarah dan pintu masuk ke era, merek, dan topik.
• Linimasa: perjalanan motor nasional dari era awal sampai modern.
• Merek & Pabrikan: halaman profil tiap merek dan perusahaan terkait.
• Model & Generasi: katalog model motor, generasi, spesifikasi inti, dan konteks zamannya.
• Balap & Kompetisi: catatan balap nasional, tim, pembalap, dan tonggak penting.
• Budaya & Komunitas: cerita klub, modifikasi, touring, dan pengaruh sosial.
• Arsip Media: foto, poster, brosur, iklan, dan dokumentasi lama.
• Ensiklopedia Istilah: glosarium teknis dan istilah populer dunia motor Indonesia.

Shared Cloudflare Stack

• Worker / Pages: reuse the same Cloudflare-native foundation proven in motnas.com/.
• D1: store timelines, article metadata, manufacturer/model records, glossary entries, and editorial tags.
• R2: store scanned brochures, archive images, posters, and media assets.
• Cron / import jobs: optionally reuse ingestion patterns for structured datasets and scheduled archive refresh.
• motnas.org should share the platform, but not collapse into the same editorial purpose as motnas.com.

Editorial Rules

• Every article must prioritize historical clarity and reference value, not clickbait.
• Pages should be evergreen and internally linked by:
  • era
  • brand
  • model
  • topic
• The site should read like a living archive, not a generic news portal.
• Current news can appear only when it helps explain the long story of motor nasional.

Build Sequence

• Define the canonical taxonomy for era, brand, model, race, and community topics.
• Build the first timeline-driven homepage and archive navigation.
• Create structured D1 records for manufacturers, models, and milestone events.
• Move archival images and brochure material into R2.
• Publish the first set of cornerstone pages:
  • sejarah motor nasional
  • daftar merek motor nasional
  • timeline industri motor Indonesia
  • arsip model motor lintas dekade

Definition of Done

• motnas.org has a clear identity as the long-horizon archive and knowledge site for motor nasional.
• The site covers the story from the early era to the present day.
• It runs on the same Cloudflare-native platform family as motnas.com, but with a different editorial mission.
• The plan is specific to the domain purpose and no longer reads like a generic alias note.

⚙ HARD CONSTRAINTS (enforced for all sites)

This domain MUST operate within these constraints — no exceptions:

• 100% Cloudflare serverless — Workers + D1 + R2 + KV + Workers AI + Vectorize. NEVER PM2, NEVER VPS, NEVER Docker in production path.
• 100% AI-automated — every customer interaction, every moderation decision, every transaction reconcile = AI. No manual queue, no live human chat support, no physical fulfillment.
• 1-operator solo — one person can run the entire operation from a phone. No team meetings, no shared inbox, no shift rotation.
• WhatsApp AI bot for all support (24/7, instant response, no SLA promises that need humans).
• Mayar QRIS for all Indonesian payments (subscription auto-renew, no manual invoicing).
• Indonesian UI primary — bahasa-first, English fallback only where unavoidable.
• Privacy — opt-in only, delete-on-request honored within 24h (cron-driven).
• No physical goods, no inventory — digital products + affiliate referrals only.

If the plan above describes any flow that violates these constraints, treat the plan as ASPIRATIONAL only and rework before building. The constraint trifecta wins.