[ 01 // PROJECT SCOPE & RESULTS ] · CLIENT: Sestry.eu (Netguru Contract) · ROLE: Infrastructure architecture and publishing integrations · 2024 – 2025

Sestry.eu: publishing infrastructure built for growth

Connecting content distribution, translation and audio with a Cloudflare layer that reduces repeated requests to the editorial CMS.

REPORTED ORIGIN TRANSFER REDUCTION 95%

DISTRIBUTION Onet.pl article feed

LOCALISATION Ukrainian → Polish / English

AUDIO ElevenLabs narration

[ 01. BUSINESS CONTEXT ]

What needed to change

Sestry.eu needed to serve growing readership while keeping the Webflow workflow used by its editorial team. The existing project account describes additional bandwidth charges reaching $450 per month. At the same time, the publication needed to reach readers through partner media, translated articles, audio and subscriber notifications. The engineering challenge was to connect those services around the publishing process while reducing repeated transfers from the source system.

[ 02. SYSTEM ARCHITECTURE ]

How the system fits together

[ Readers ]
    │
[ Cloudflare: request filtering + content cache ]
    │ Requests that need the source
[ Webflow CMS: editorial content ]
    ├── Cloudflare Worker / XML feed → Onet.pl
    ├── DeepL → Polish and English translation drafts
    ├── ElevenLabs → in-article audio
    ├── OneSignal → browser notifications
    └── Mailchimp → newsletters

[ 03. ARCHITECTURAL DECISIONS ]

Scope and key decisions

1. Keep the editorial workflow. Our architectural scope, delivered by Mariusz Ruski under a Netguru contract, connected the existing Webflow CMS to a Cloudflare cache layer. Reusing cached content reduced the need to fetch the same pages and assets from the source. 2. Meet a distribution partner’s requirements. A Cloudflare Worker transformed CMS content into the XML feed required by Onet.pl. This made syndication part of the publishing workflow. 3. Connect content services. DeepL produced Polish and English translation drafts; ElevenLabs provided article narration. OneSignal and Mailchimp connected published content with notification and newsletter channels. The key architectural decision was to extend the existing editorial system with specialised services rather than require a CMS migration.

[ 04. RESULTS & DELIVERY STATUS ]

What the work delivered

▶ The project account reports 95% less data transfer from the source. This is a bandwidth result, not a 95% reduction in total operating cost.

▶ Automated article delivery opened a distribution channel through Onet.pl.

▶ Translation drafts, article audio and subscriber communications were connected to the publishing workflow.

When this approach applies

Relevant when a publisher or content platform needs to handle more traffic and connect new distribution channels while preserving the tools its editorial team already uses.

[ 05. TECHNOLOGIES & TOOLS ]

Cloudflare Workers Cloudflare Edge Cache ElevenLabs AI (TTS) DeepL API Webflow CMS OneSignal (WebPush) Mailchimp Automation XML / ATOM Syndication Cloudflare WAF

[ A SIMILAR CHALLENGE? ]

Discuss your system

Describe the process, current constraints and result you need.

Discuss your project