Development of an information portal on 1C-Bitrix

Development of Information Portal on 1C-Bitrix

An organization publishes content in five places: news in a WordPress blog, documents in Google Drive, FAQ in Notion, procedures in PDFs on file server, event announcements in Telegram channel. An employee or client needing to find current information has to search through sources and hope they found the latest version. An information portal on 1C-Bitrix solves this: single entry point, structured content, managed access, and search that actually finds things.

Information Portal Architecture

1C-Bitrix provides ready infrastructure: info blocks for structured content storage, components for display, search module, permission system. The task is to assemble from this a portal adapted to the specific subject area.

Typical portal structure:

• Home page with content aggregation from different sections
• Thematic sections with hierarchical nesting
• Material cards with metadata (author, date, tags, related documents)
• Full-text search with filtering by sections and content types
• Personal account with subscriptions and favorites

Info Blocks — Foundation of Content Model

Each content type is modeled as a separate info block: articles, documents, news, events, FAQ. Inside the info block are sections and elements.

Designing element properties determines how content will be filtered and displayed. For an article: title, annotation, text (visual editor), author (user binding), rubric, tags, publication date, status (draft/moderation/published).

Links between info blocks are implemented through "Binding to Elements" property. Article references documents, event references related news, FAQ references knowledge base section. This builds cross-reference navigation without content duplication.

Recommendation on sections. Hierarchy should not exceed 3–4 levels. Deeper nesting complicates navigation and slows down breadcrumb construction through CIBlockSection::GetNavChain().

Content Management and Workflow

Editors work through administrative interface of 1C-Bitrix or through site's public part (component bitrix:iblock.element.add.form). For portals with dozens of authors, the second option is preferable — no need to grant admin access.

Content Status Model:

Transitions between statuses are implemented through bizproc module business processes. On sending to moderation — moderator notification, on publication — RSS update and sitemap ping.

Roles and Access Rights

1C-Bitrix uses user groups. For information portal, typical roles:

• Reader — view published content, subscribe to sections
• Author — create and edit own materials
• Moderator — review and publish others' materials, manage comments
• Section Editor — full rights within assigned section
• Administrator — manage structure, rights, settings

Rights are assigned at info block and section level. Through advanced rights (iblock with SECTION_ID support), you can restrict access so marketing department editor sees only their section.

Search

Standard 1C-Bitrix search module indexes info blocks, files, forums. For information portal this is basic: Russian morphology, relevance by word frequency, filtering by modules.

For portals with content over 10,000 elements Elasticsearch or Sphinx is recommended. Integration is through search module with custom handler. Advantages: faceted search, result highlighting, "did you mean", auto-completion.

Component bitrix:search.page displays results. Parameters configure: items per page, sorting, annotation display with highlighting.

SEO Component

Information portal must be indexed by search engines. In 1C-Bitrix SEO is covered by tool set:

• Clean URLs — through URL template configuration in info block (#SECTION_CODE#/#ELEMENT_CODE#/)
• Meta Tags — title, description, keywords set for each element and section, or templated
• Canonical URLs — component bitrix:main.canonical prevents duplication
• Sitemap — generation through standard SEO module or custom handler for info blocks
• Structured Data — Schema.org for articles (Article), FAQ (FAQPage), events (Event)
• Open Graph — for correct display when sharing in social networks

RSS Feeds are generated by component bitrix:rss.out — by sections, tags, content type. Both distribution channel and signal to search robots about new content.

Performance

For high-traffic portal critical:

• Composite Cache — module composite returns static HTML, dynamic blocks load via AJAX
• Component Caching — configured individually, lifetime depends on section update frequency
• CDN for Static — images, CSS, JS served via CDN
• Pagination — bitrix:system.pagenavigation in AJAX mode for sections with hundreds of elements

Properly configured information portal on 1C-Bitrix handles tens of thousands of views per day on standard VPS. With growing load — horizontal scaling through web cluster and moving MySQL to separate server.