Editorial Guidelines
Content Standards
All content published on FlyFish NWA must meet the following criteria:
- Technical accuracy — Claims must be verifiable. Configuration examples must be tested. Performance numbers must cite methodology.
- Vendor neutrality — Provider comparisons present objective analysis. We do not accept sponsored content or paid reviews.
- Practitioner perspective — Authors must have hands-on experience with the technologies they write about.
- Structured learning — Content follows a clear progression from concept explanation to practical implementation.
Article Structure
Each article should include:
| Metric | Edge Processing | Origin Processing | Improvement |
|---|---|---|---|
| Latency (p50) | 8–15 ms | 120–300 ms | 15–20x faster |
| Cache Hit Ratio | 85–95% | N/A | Reduces origin load |
| TLS Handshake | 1–5 ms (nearby PoP) | 50–150 ms | 10–30x faster |
| Bandwidth Cost | $0.01–0.04/GB | $0.05–0.12/GB | 3–5x cheaper |
| Availability | 99.99% (multi-PoP) | 99.9% (single DC) | 10x fewer outages |
- A clear problem statement or concept introduction
- Technical explanation with diagrams or code where appropriate
- Practical examples drawn from real-world CDN operations
- Common pitfalls and how to avoid them
- References to related articles for deeper exploration
Review Process
Every article undergoes technical review by at least one other team member before publication. We prioritize depth over speed — a well-researched article that takes a week beats a surface-level post published today.
Corrections
If you find an error in any article, please contact us. We issue corrections promptly and transparently, noting what changed and when.