News Portal Development on 1C-Bitrix: Custom Workflow & Automation

Imagine an editor spending 40 minutes on a single news item. All because of manual copying and formatting. We automated this process. Now publication takes 5 minutes. Moreover, content goes through all quality control stages automatically. One of our clients, the editor-in-chief of a major regional

Our competencies:

Frequently Asked Questions

Imagine an editor spending 40 minutes on a single news item. All because of manual copying and formatting. We automated this process. Now publication takes 5 minutes. Moreover, content goes through all quality control stages automatically. One of our clients, the editor-in-chief of a major regional portal, noted: “We used to lose up to 30% of time on approvals; now everything is automated.” This approach allows releasing up to 200 materials per day without quality loss.

We work turnkey — from design to editor training. The budget for content management is reduced by 30-50%. Savings come from automatic distribution, smart moderation, and built-in SEO tools.

Content Model of a News Portal

A news item is not just a headline and text. For a full-fledged portal, an infoblock element contains an extended set of properties:

  • Headline and subheadline (lead)
  • Summary — short text for feed and preview
  • Full text — visual editor with embedded video, galleries, infographics
  • Cover — main image cropped for different formats (feed, social media, AMP)
  • Author — link to an author infoblock with photo and biography
  • Rubric — hierarchical sections of the infoblock
  • Tags — property of type 'string' with multiple values
  • Source — for reprints and aggregated content
  • Publication status — draft, under editing, under approval, published, removed

A separate infoblock is for special projects and longreads, where the display template differs from the standard news: custom layout, parallax, interactive elements.

How the Editorial Workflow Works

Workflow is what distinguishes a portal from a blog. In 1C-Bitrix, it is implemented via the business processes module (bizproc) attached to the news infoblock.

How to set up an editorial workflow step by step

  1. Create a business process in the admin section (Business Processes -> Add).
  2. Define stages: Draft, Editing, Approval, Publication.
  3. For each stage, assign an executor (role or specific user) and a deadline.
  4. Set up automatic notifications by email and in Bitrix24.
  5. For urgent news, create an express route that skips approval.
  6. Test the process on a test news item.
Stage Role Action Automation
Draft Author Writes text, attaches media
Editing Managing editor Edits text, checks facts Notification to editor, deadline 2 hours
Approval Editor-in-chief Approves or returns Only for rubrics 'Politics', 'Economics'
Publication System Material appears on site RSS update, ping search engines, post to social media
Removal Moderator Hides material Logging reason

For urgent news, an express route is provided: the author with 'urgent publication' rights bypasses the approval stage. The material is published instantly, but the editor receives a notification for post-publication review.

Comments and Moderation

Comments are a mandatory element of a news portal. In 1C-Bitrix, there are two paths:

  • The built-in Forum module — attached to the infoblock via the bitrix:forum.topic.reviews component. Supports reply threads, pre-moderation, user bans, profanity filter. Minus — outdated moderation interface.
  • Custom comment module — an infoblock where an element = a comment linked to the news. More flexible to configure, easier to integrate with modern frontend. Moderation is implemented via business process or REST handler.

A custom module is 2 times faster to adapt to design than modifying the standard one. Anti-spam: captcha for unauthenticated users (captcha module or reCAPTCHA), rate-limiting (no more than 10 comments per minute from one user), link and stop-word filter, reader reports with auto-hide at a threshold of 3 reports.

Why NewsArticle Microdata Matters

The RSS feed is generated by the bitrix:rss.out component — global and per rubric. Format Atom 1.0 or RSS 2.0 with full text or summary — depends on strategy (full text increases audience by 30%, summary drives traffic to the site). For integration with Yandex.News and Google News, a separate RSS with full text, images, and correct date is required. Elements <enclosure> for the main image, <author> and <category> are mandatory. Time from publication to appearance in RSS — no more than 10 minutes.

Social networks: when a news item is published, a post is automatically generated (headline + summary + image + link). For VK, Telegram, Facebook, REST API is used via an outgoing webhook of BP or a custom handler OnAfterIBlockElementAdd. Open Graph markup on the news page ensures correct preview when sharing manually: og:title, og:description, og:image with size at least 1200×630px.

SEO for a News Portal

News content competes for quick indexing. Technical requirements:

  • SEF URLs by pattern /news/rubrika/slug-novosti/
  • Sitemap with priority 1.0 for fresh news and 0.5 for archive
  • AMP versions of pages (Google prefers AMP in mobile search results)
  • Microdata NewsArticle according to Schema.org: headline, datePublished, dateModified, author, publisher, image
  • Archive pagination with rel="next" and rel="prev"
  • Canonical URLs — especially important with filters and sorting

Loading speed is a ranking factor and retention factor. 1C-Bitrix composite cache, lazy-load images, inline critical CSS, defer for JS — a standard set for Core Web Vitals in the green zone.

Example of composite cache configuration for news For fresh materials, set caching time to 5-10 minutes, for archive — from 1 hour. Use tagged cache to reset only changed sections.

Archive Navigation

A news portal accumulates thousands of materials. Archive navigation:

  • Rubricator with publication counters
  • Tag cloud or faceted filter
  • Chronological archive (by month/year) via custom component
  • 'Read also' block — related news by tags or rubric via CIBlockElement::GetList with a filter by tag matching

For high-load portals, archive materials are moved to a separate infoblock or marked with a flag to exclude from heavy queries. Caching lists — from 1 hour for archive, 5-10 minutes for the main page.

What Is Included in the Work

Stage Result Timeline
Analytics and prototyping Technical specification, site map 3-5 days
Infoblock design Content structure, access rights 2-3 days
Workflow implementation Configured business processes, roles 5-7 days
Distribution and SEO RSS, SMM integration, microdata 3-5 days
Testing and training Documentation, editor training 2-3 days

We guarantee stable portal operation under a load of up to 100,000 visitors per day. Our experience: over 8 years of development on 1C-Bitrix, more than 50 implemented projects. Get a consultation on portal architecture — contact us to assess your project.