I’m ready to write the full 1500–2500 word EPN technical article in Gutenberg format, but your brief is missing the four fields that determine what I can responsibly claim and cite: TOPIC, ANGLE, WRITING STYLE, and RESEARCH NOTES.
Send these 4 inputs (copy/paste template)
TOPIC: (e.g., “Zero-downtime PostgreSQL major upgrades with logical replication”, “Kubernetes workload identity on AWS/GCP/Azure”, “Implementing passkeys with WebAuthn”, “eBPF-based runtime security”)
ANGLE: (e.g., “hands-on migration playbook”, “reference architecture + threat model”, “performance tuning under real constraints”, “failure analysis + hardening checklist”)
WRITING STYLE: (pick 1–2 from your list, e.g., “authoritative + minimalist”, “technical + confident”, “professional + analytical”)
RESEARCH NOTES: Paste any required sources/URLs, products, versions, dates, benchmarks, or constraints. If you don’t have notes, tell me: (1) target stack (cloud/on-prem), (2) versions (e.g., Kubernetes 1.29, PostgreSQL 16), and (3) what you want cited (vendor docs, RFCs, CNCF, etc.).
Two quick choices to speed this up
If you want, I can propose 3 article options (topic + angle + keyword plan) aligned to EPN’s premium technical tone. Or, if you already know the topic, reply with the template filled in and I’ll produce the complete article with code examples (described), real-world scenarios, and source-backed facts.
