Home PageLive interface · archived snapshot 07–09.06.2026
01 / Context
A news product must support high-frequency publishing and surface the most important stories quickly
The agency covers politics, economics, culture, sport, world events, incidents, society and crime. The homepage acts as a continuously updated editorial layout, placing a lead story alongside topic columns, while section archives provide extensive feeds.
Challenge
Create a continuous flow of news from Kazakhstan and worldwide
Solution
Sections, feeds, content, search and bilingual publishing
02 / Pain Point → Solution
More than pages: clear journeys for different user intentions
01
Editorial Speed
Publish and rearrange news without developer involvement.
02
Priorities
Separate the lead story from the brief news feed and topic blocks.
03
Navigation
Keep all eight sections accessible from every article.
04
Two languages
Support separate Russian and Kazakh editorial workflows.
03 / Information Architecture
The user journey is built around a meaningful task
The architecture was reconstructed from public navigation, internal links and accessible routes.
04 / Core UX
A newspaper-style layout makes it easy to scan dozens of headlines in minutes
The homepage uses a hierarchy of headings and columns so readers can distinguish the lead story, latest updates and individual sections. Category pages narrow the feed to one topic, while articles preserve context through dates, authors and related publications.
Politics SectionThematic Publication FeedAbout the Editorial TeamMedia Status, Authors, and Contacts
05 / Content Model
The CMS separates daily publishing, categorization and language versions
Posts
News Content
Title, Date, Author, Image, and Text
Categories
8 areas
Politics, economy, culture, sport and more
Homepage
Editorial Layout
Lead story, feeds and curated topic collections
Languages
RU / QAZ
Separate Editorial Branches
Search
Archive Search
Access to Older Publications
Analytics
Demand for Content
GA and Yandex Metrica in Public Code
06 / Technology Stack
The public implementation was analysed using the source HTML and network resources
WordPressNews CMS and ArchivesElementorHome-Page Templates and LayoutPolylangRussian and Kazakh VersionsSwiperCarousels and Media BlocksGoogle / Yandex analyticsAudience MeasurementWordPress JSON-LDWebSite/Organization markup
07 / Interactive Flows
The interface helps users complete tasks without unnecessary navigation
Search
Full-Text Archive Search
Category feeds
Continuous Thematic Feeds
Share
Content Distribution on Social Media
Responsive news
Column Reflow on Mobile
08 / SEO Audit
Search Baseline and Specific Growth Opportunities
The archived version includes a description, canonical URL, Open Graph and one JSON-LD block. Categories create independent search archives. A news resource needs NewsArticle schema, accurate modified/published dates, author pages, an XML News Sitemap and duplicate control across its two language branches.
8editorial sections
2language branches
1JSON-LD on the archive home page
503current domain response
On 09.09.2026, the live domain returned a 503 ‘Hosting disabled’ response. The real interfaces shown in this case study were captured from Wayback Machine snapshots dated 07–09.06.2026. This is explicitly disclosed to reflect the project's current status accurately.
09 / Responsive
The Primary Flow Is Preserved on Mobile
Navigation, headings, cards and calls to action are reorganised into a single vertical flow. The mobile screen below is an authentic capture of the original interface at a width of 390 px.
Clear hierarchy without horizontal scrolling
Large Touch Targets for Primary Actions
Progressive Content Loading
Keeping the primary CTA accessible in the mobile journey
Mobile VersionViewport 390 × 844
10 / Technical Review
The Case Study Is Based on the Observable Implementation
01
HTTP and routes
The home page and key internal pages, response statuses and redirects were verified.
02
HTML and metadata
Title, H1, description, canonical, Open Graph and JSON-LD were captured.
03
Frontend stack
The technologies were verified through the names of public scripts, styles and API endpoints.
04
Responsive
Homepage reviewed at 1440 × 1000 and 390 × 844.
05
Content
The information model was validated against navigation, archives and the sitemap.
06
Evidence
Every interface in this case study is an authentic project screenshot with no generated UI.
11 / Result
BAI Media's editorial architecture supports continuous publishing: categories establish a stable taxonomy, the homepage directs attention, and WordPress enables publication without rebuilding the product. A separate operational lesson is that infrastructure availability needs the same rigorous monitoring as publishing speed.
8 main categories and 24/7 publishing. The solution can evolve as the content and new user journeys grow.
Need a media center or news portal with an editorial workflow?
We will analyse the audiences, content, integrations and search demand, then design the structure and technical architecture before visual design begins.
