Media Portal on 1C-Bitrix: Workflow, Paywall & Highload

Imagine: a material with a typo goes into the night edition. An hour later — a wave of negative feedback. The reason? The lack of an editorial workflow. We build media portals on 1C-Bitrix from scratch or improve existing ones. Our 1C-Bitrix media portal solutions integrate editorial workflow, paywall, and highload features seamlessly. 10+ years of practice, 50+ projects. Get a consultation.

Key problems solved by media portal development on 1C-Bitrix

A media portal is not just a news site. It is a platform that withstands peak loads up to 1000 RPS. It manages content from dozens of authors, monetizes through subscriptions, and distributes materials to social networks. 1C-Bitrix provides ready-made tools: infoblocks, business processes, composite cache, sale module. Without proper architecture, even a powerful CMS won't save you.

Composite cache speeds up static page loading by 10 times compared to regular caching. This is 10x faster than standard caching and 50x faster than dynamic page generation. For one of our clients — a regional media with 500,000 unique monthly visitors — we implemented a metered paywall. Within 3 months, revenue grew by 40% (saving 100,000 rubles monthly on infrastructure).

How is the editorial workflow arranged?

Workflow is what distinguishes a publication from a blog. Each material goes through a processing chain. At each stage — its own responsible person and its own rules.

Roles in the editorial office:

• Correspondent/author — creates a draft, edits before sending for review.
• Production editor — proofreads, corrects style, checks facts.
• Section editor — approves material for his/her section.
• Editor-in-chief — final approval for materials marked 'important' and 'breaking'.
• Proofreader — proofreading before publication (optional stage).
• Photo editor — selection and processing of illustrations.
• SMM editor — preparation of announcements for social networks.

Business process of publication via bizproc:

1. Author creates material, fills required fields, attaches media → status 'Draft'.
2. Sends for editing → production editor receives notification, deadline depends on priority (urgent — 30 minutes, normal — 4 hours).
3. Editor edits text in track changes mode (via visual editor or third-party tool), approves or returns to author with comments.
4. Approved material goes to section editor (if required) or directly to publication.
5. Materials marked 'important' — additional stage of approval with editor-in-chief.
6. On publication: SEO-friendly URL is formed, sitemap is updated, announcement for social networks is generated, aggregators are pinged.

Express publication for breaking news: author with 'urgent publication' right bypasses approval stages. Material is published instantly but automatically enters the post-factum verification queue.

Publication scheduling. The editorial board plans an issue for the day/week. Planning board — Kanban or calendar where all materials are visible by statuses and release dates. Implemented via a custom component with drag-and-drop.

Multi-author system

A publication with 20+ authors requires:

• Author profiles — infoblock: photo, biography, position, social networks, list of publications. Author page — /authors/ivanov-petr/ — with all materials.
• Access rights — author edits only his/her own materials, editor — materials of his/her section, editor-in-chief — everything.
• Guest authors — external experts who write columns. Separate user group with limited rights: create draft → send to moderation, without publication capability.
• Author statistics — number of publications, views, average reading completion rate. Available to editor and the author himself.

Effectiveness of paywall on 1C-Bitrix

Monetization through subscription is a trend among quality publications. In 1C-Bitrix it is implemented in several ways.

Paywall models:

Implementation of metered paywall:

• On each view — counter in cookie and/or database (for authorized users).
• Limit reached → content blocked with a modal window offering subscription.
• Subscriber — user group 'Subscribers', access to full text via infoblock permissions.
• Bypass via incognito — protection: account binding, fingerprinting (subject to legislation).

Subscription payment:

• 1C-Bitrix sale module: product = subscription for month/quarter/year.
• Recurring payments via YooKassa, CloudPayments, Stripe.
• On subscription expiration — automatic removal from 'Subscribers' group, progress (reading history) is preserved.
• Corporate subscriptions — invoice to legal entity, IP authorization (access from all devices in office network).

Savings on infrastructure due to composite cache reach up to 60%. This gives savings up to 100,000 rubles per month at 1 million pageviews. Compared to standard caching, composite cache is 10x faster.

Optimization for highload

A media portal is one of the most loaded types of web projects. A trending news story gathers hundreds of thousands of views per hour.

Optimization stack:

• 1C-Bitrix composite cache — the basis. Static HTML version of the page is served by nginx, dynamic blocks (view counter, comments, paywall widget) are loaded via AJAX.
• Nginx as reverse proxy — with microcaching (1-5 seconds) for hot pages.
• CDN — Cloudflare, AWS CloudFront or Selectel CDN. Static content is served from the nearest edge server.
• Automatic image resizing — via imgproxy or built-in 1C-Bitrix handlers. Cover 3000x2000 is not served to mobile client — version 800x450 is generated, reducing load by 40%.
• Deferred operations — view counter is accumulated in Redis/Memcached and flushed to DB by agent once per minute.
• MySQL read replicas — separate server for SELECT queries. 1C-Bitrix supports DB cluster out of the box (cluster module).
• Horizontal scaling — several web nodes behind a load balancer. Sessions stored in Redis, files in S3-compatible storage (via clouds module).

Load budget:

Media portal content model

A media portal works with several content types, each with its own specifics.

Infoblocks:

• News — quick materials, short format, fast publication.
• Articles — analytics, investigations, longreads with extended layout.
• Interviews — structured format (question-answer), linked to a person.
• Opinions/columns — author materials, linked to a regular author.
• Special projects — custom landing pages with unique design.
• Photo reports — galleries with captions and event links.
• Video — embedded videos or links to video hosting.

Material element — extended properties:

Content distribution

Material is published — it needs to be delivered to the audience.

Channels:

• RSS/Atom — global feed and by sections. For Yandex.News and Google News — separate feeds with full text and extended metadata.
• Telegram channel — automatic posting via Telegram Bot API on publication. Format: title + lead + image + link.
• Social networks — VK, Facebook, Twitter via REST API. Open Graph markup for correct previews.
• Push notifications — Web Push via Service Worker. Segmentation: subscribers of 'Politics' section receive push only for that section.
• Email digest — daily/weekly selection via 1C-Bitrix mailing module.
• AMP pages — for priority in Google mobile search.
• Yandex Turbo pages — RSS feed in Turbo format for fast loading from Yandex.

SEO for media portal

• Microdata NewsArticle / Article: headline, datePublished, dateModified, author (with link to profile), publisher, image, wordCount.
• SEO-friendly URLs — /section/material-slug/ or /section/yyyy/mm/dd/slug/ (with date for news portals).
• Canonical URL — required for pagination, AMP versions, sorting parameters.
• Sitemap — split by content type and time periods: sitemap-news-current-month.xml, sitemap-articles.xml.
• Core Web Vitals — LCP < 2.5s, FID < 100ms, CLS < 0.1. Achieved via composite cache, lazy-load images, critical CSS.
• Internal linking — 'Read also', 'Related', 'Popular' blocks — automatic generation by tags and sections.

Comments and UGC

• Comment system — custom module or 'Forum' module linked to material.
• Pre-moderation for new users, post-moderation for trusted.
• Comment rating — likes/dislikes, best comments are pushed up.
• Verification — mark for experts and public figures (like 'blue checkmark').
• Ban system — temporary/permanent ban, shadow ban (user writes but only he sees his comments).
• Anti-spam — captcha, rate-limiting, stop words, ML filter for toxic content.

What is included in the work

When ordering development of a media portal on 1C-Bitrix, we provide:

• Technical specification with architecture, screen map and prototypes.
• Repository with Git history, code review, CI/CD pipeline.
• Full deployment and operation documentation.
• Access to admin panel and monitoring system.
• Training for editorial staff and administrators (2-3 sessions).
• 12-month warranty on code and post-project support.

Budget for development varies from 1 to 3 million rubles depending on complexity. Timeline — from 3 weeks to 3 months. Contact us to evaluate your project. Get a consultation today.

How a corporate portal on Bitrix24 solves the problem of information chaos?

Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.

We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).

What does the portal offer in daily work and why is it better than messengers?

In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.

Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.

Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.

Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.

HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.

Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.

Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.

How does integration with 1C and Active Directory accelerate HR management?

Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.

Types of corporate portals and key integrations

Additional integrations that deliver real value:

• Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
• IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
• Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
• EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.

Security and compliance with Federal Law 152‑FZ

The portal contains personal data, financial reports, strategic plans. We guarantee protection:

• role model via CGroup and section‑level permissions;
• two‑factor authentication (OTP, Yandex.Key, SMS);
• audit of all actions (b_event_log);
• TLS encryption for transmission and disk encryption;
• full compliance with Federal Law No. 152‑FZ "On Personal Data".

How is implementation carried out? Step‑by‑step plan

1. Audit — we record current processes, measure time losses.
2. Design — choose portal type, plan integrations.
3. Implementation — configure business processes, permissions, interface.
4. Test — pilot group tests scenarios, we fix issues.
5. Launch — connect all employees, train, hand over documentation.

What you receive after implementation

• Project documentation: architecture, integration scheme, business process diagrams.
• Configured portal with all integrations (1C, AD, telephony, EDI).
• Business process descriptions and instructions for administrators and users.
• 30 days of technical support after launch.
• Access to our knowledge base and migration scripts.

Post‑launch support: how to prevent the portal from becoming obsolete

After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.

Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.

Order a turnkey corporate portal implementation

Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.