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
- Create a business process in the admin section (Business Processes -> Add).
- Define stages: Draft, Editing, Approval, Publication.
- For each stage, assign an executor (role or specific user) and a deadline.
- Set up automatic notifications by email and in Bitrix24.
- For urgent news, create an express route that skips approval.
- 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.
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
| Type |
Purpose |
Key Feature |
| Intranet |
Internal communications and services |
News, phone directory (sync with AD), meeting room booking, IT requests via BP |
| HR portal |
HR management and development |
Profiles, KPI/OKR on custom HL blocks, training, electronic document flow |
| Knowledge portal |
Documentation and regulations |
Categorization, tags, ratings, subscriptions to updates |
| Extranet |
Work with partners and contractors |
Granular permissions via CGroup and extranet module, access without VPN |
| Holding portal |
Management of multi‑company structure |
Separate workspaces, consolidated reporting, cross‑cutting BPs |
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
| Stage |
Duration |
What we do |
| 1. Audit |
2–3 weeks |
Interviews, process analysis, architecture, integration plan |
| 2. Setup and customization |
3–6 weeks |
Structure, roles, BPs, branding (CSS template) |
| 3. Integrations |
2–4 weeks |
1C, AD, email, telephony, EDI |
| 4. Data migration |
1–2 weeks |
Documents, directories, employees from current systems |
| 5. Training and pilot |
1–2 weeks |
Administrators, key users, pilot of 20–30 people |
| 6. Scaling |
2–4 weeks |
Connecting departments, fine‑tuning based on feedback |
- Audit — we record current processes, measure time losses.
- Design — choose portal type, plan integrations.
- Implementation — configure business processes, permissions, interface.
- Test — pilot group tests scenarios, we fix issues.
- 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.
