Independent media project · Website + Telegram
Klyamka: from source material to web and Telegram
BlueRock built Klyamka's news website and publishing workflows around two public destinations: the website and Telegram. The work connects source intake, editorial preparation and delivery, with checks that distinguish prepared content from confirmed publication.
The challenge
A news operation needs to do more than collect headlines. Incoming material must become a readable story, reach the right channel and appear correctly for readers. Those steps need to remain traceable when a source changes, a publication is held or delivery is interrupted.
For Klyamka, we developed the reading experience and the publishing process together. The website gives stories a structured home. Telegram gives the project a separate channel for news updates.
What we built
The website organises Ukrainian-language coverage into topic sections, a latest-news feed and individual article pages. Articles bring together a short summary, the main text, publication and update times, and source links. The implementation also includes English-language versions and URL monitoring.
Behind these public pages, we built workflows that separate collecting material, preparing content, running checks and publishing. Each stage has a defined role, so a prepared story is not treated as successfully delivered before the public result is verified.
The website workflow
Source and RSS material enters an intake process. An AI-assisted editorial step prepares the content, followed by checks and a static-page build. A separate publication step delivers the new site version.
The workflow then checks the public page and its content before confirming the item as published. Build records and logs support investigation if a stage fails or the delivery result is unclear.
This separation makes publication confirmation part of the workflow itself.
Telegram publishing
Klyamka's Telegram workflow separates material intake, editorial rewriting and delivery of prepared posts. Policy and timing checks govern publishing operations, while delivery records make the outcome traceable.
Selected items can be held. If a send result is uncertain, the workflow requires verification before another attempt. This control addresses a practical publishing risk: an interrupted response should not trigger a blind resend of a post that may already be public.
Telegram operates as its own delivery path alongside the website. Each channel's publication result is checked separately.
Confirmed output
The work has produced a public news website and a public Telegram channel. A completed website publishing cycle was verified on 9 October 2026, and Telegram publication was verified separately on 12 October.
These are confirmed outputs from the implemented system. Operating the platform also involves supervision, maintenance and recovery when delivery cannot be confirmed. Operational refinement continues.
Build your Telegram workflow
Need a channel that fits into your wider publishing process? We can scope the content inputs, preparation steps, review rules and delivery checks around your operation.