Developing an Educational Institution Website on 1C-Bitrix

Rosobrnadzor Order No. 831 requires 13 mandatory sections on an educational institution's website. Missing even one item risks a fine of up to 50,000 rubles. Switching to electronic document management can save up to 200,000 rubles per year. We have developed over 50 projects for schools, colleges, and universities, each passing inspection without comments. Our experience with 1C-Bitrix exceeds 10 years, and we guarantee that your website will comply with 273-FZ.

Which mandatory sections are required by law?

The structure of the "Information about the educational organization" section according to Order 831 includes strictly defined subsections. Each must be accessible within 3 clicks from the homepage and have a direct link.

Technical implementation of the "Management. Teaching Staff" subsection

The Teachers infoblock contains properties: FIO, POSITION, DISCIPLINES, DEGREE, EXPERIENCE_TOTAL, EXPERIENCE_SPECIALTY, QUALIFICATION_DOCS, PHOTO, DEPARTMENT_ID. Output uses the iblock.list component with a custom template in a table. Rosobrnadzor requires a tabular representation with search by full name.

Document storage

The OfficialDocuments infoblock with categories (Charter, Licenses, Accreditation). Each element is a PDF with metadata. Important: PDFs must be text-based, not scans, for indexing and screen reading.

Monitoring relevance

A Bitrix agent (CAgent) is created that daily checks:

• Documents with expiring deadlines — notification 60 and 30 days in advance.
• Sections not updated for more than 6 months.
• Presence of all mandatory subsections (automatic checklist).

How to implement a schedule in 1C-Bitrix?

The schedule is the second most visited section after the homepage. Storage in a Highload-block Schedule with fields: UF_CLASS_ID, UF_SUBJECT_ID, UF_TEACHER_ID, UF_ROOM, UF_DAY_OF_WEEK, UF_LESSON_NUMBER, UF_TIME_FROM, UF_TIME_TO, UF_WEEK_TYPE, UF_DATE_FROM, UF_DATE_TO. ORM queries to the HL-block are faster than CIBlockElement::GetList(). The display component is custom with AJAX filtering. Import from Excel via PhpSpreadsheet.

What does a personal account give for each role?

Student: schedule, grades, homework, announcements. Parent: the same data linked to the child via UF_PARENT_OF. Teacher: own schedule, grade entry, homework publication. Grades stored in HL-block Grades, homework in Homework. Access control via user groups: Students, Parents, Teachers, Administration.

Admissions campaign

Online application for admission — a web form with fields: full name, date of birth, program, parent contacts, documents. The application is saved in CRM as a lead with a funnel: New -> Documents under review -> Enrolled/Rejected. Email notifications. This system handles up to 5,000 applications per day without failures.

Accessibility (WCAG 2.1)

Version for the visually impaired via CSS variables and JS with choice saved in localStorage. Alt texts, keyboard navigation, contrast ratio 4.5:1. These measures are mandatory for all educational sites and increase audience reach by 15-20%.

What's included in our work?

• Technical specification with detailed description of sections.
• Prototyping and responsive design with WCAG considerations.
• Development on 1C-Bitrix, custom components and integrations.
• Testing for compliance with 273-FZ and load testing (handles 1000 concurrent requests).
• Deployment with performance optimization (LCP < 2.5 sec).
• Training for administrators and editors.
• Technical support for the first month.

Stages of work

1. Audit and requirements gathering — we study processes and documents.
2. Design — structure and prototypes.
3. Development — infoblocks, HL-blocks, components.
4. Content filling — data upload.
5. Testing — all sections and accessibility.
6. Launch and monitoring setup.
7. Handover and training — instructions and Q&A session.

Timelines and cost

Exact cost is calculated individually after analyzing the technical specification. Simply contact us — we will evaluate your project within 2 days and offer a solution with a guarantee of passing Rosobrnadzor inspections. Get in touch for a free consultation on your project.

Order the development of an educational institution website on 1C-Bitrix — get a system that meets all legal requirements.

How to properly design infoblocks?

When developing a 1C-Bitrix website, we see dozens of projects where poor infoblock structure slows down the site. Typical scenario: the client asks for a "product catalog." The developer creates one infoblock catalog, puts 15 properties in it. Six months later – 40 properties, 8 of which are used only for one category. The filter lags, the b_iblock_element_property table grows to millions of rows, CIBlockElement::GetList runs for 3 seconds. Consequences – conversion drop, loss of customers, additional optimization costs. In one project after catalog refactoring, page generation time dropped from 4.2 to 0.8 seconds, and annual support costs were reduced by over $10,000 through eliminated redundant queries and agents.

Our approach: design infoblocks before writing a single line of code. Separate infoblocks for entities (products, categories, brands), dictionary properties via highload blocks, trade offers for SKUs. This builds performance for years. If you want a preliminary audit of your infoblock schema, contact us for a free review of common mistakes and recommendations.

Why 1C-Bitrix outperforms most CMS for business

The choice of CMS is dictated by business needs, not preferences. Native 1C exchange via catalog.import.1c provides two-way synchronization of products, prices, balances, and orders through CommerceML without third-party modules — five times faster than developing custom exchange on OpenCart or WordPress, saving hundreds of thousands of rubles. Proactive security module includes WAF, file integrity control, SQL injection protection, and two-factor authentication; it's certified for FSTEK requirements. Modular architecture lets you enable only needed modules — iblock, catalog, sale, search — reducing DB queries per hit. Regular patches close vulnerabilities faster than open-source projects (average CVE fix time two weeks). Official documentation is maintained on the vendor's site.

What highload blocks are and how they speed up the catalog

Highload blocks are an alternative to extended infoblock properties when the list of values can grow to thousands of entries. Typical example: manufacturers, countries, colors. If stored as list properties in an infoblock, each filter triggers a full scan of b_iblock_property_enum table. With HL-blocks, selection uses indexes – filter response time drops from 1–2 seconds to 50 ms. We use HLB component and custom queries via Bitrix\Highloadblock\DataManager. This is critical for catalogs with 100,000+ items.

From our practice: an online store with 500,000 items. Standard filter by brand took 4 seconds. The server couldn't handle 50 concurrent requests – pages crashed. We moved the brand directory to an HL-block, added tagged caching for 15 minutes, and set up an agent to clear cache on change. After optimization, filter time was 120 ms, average LCP was 1.8 seconds. The project runs stable without failures.

What integrations are critical for 1C-Bitrix stores

Each e‑commerce project requires reliable connections with payments, fiscalization, logistics, and CRM. We integrate YooKassa, CloudPayments, Tinkoff, Apple Pay, Google Pay for payments; ATOL and OrangeData for 54-FZ compliance via sale.cashbox; CDEK, Boxberry, PEC, Russian Post, Yandex.Delivery for logistics; Bitrix24, amoCRM, Roistat, Calltouch, Mindbox for analytics and CRM. All integrations are configured with proper error handling and fallback logic.

What's included in 1C-Bitrix website development

Each project includes a full set of documentation and artifacts to prevent knowledge loss after handover.

• Technical specification – user stories, infoblock diagrams, integration schemas.
• Source code in Git – with commit history, release tags, branching rules.
• Administrative documentation – description of custom components, deployment instructions, list of agents and events.
• Staff training – up to a 3-hour webinar: admin panel, order management, price settings. Recorded for later review.
• Access to staging during development – test before production deployment.
• Warranty support – bug fixes for 30 days after launch. Post-warranty support packages with SLA (response 2 hours, resolution 8 hours).

Our process and technologies

Tech stack: mobile-first markup, tested on physical devices (iPhone, iPad, Android). Use BrowserStack for Safari on iOS. Performance goals: LCP < 2.5 s, FID < 100 ms, CLS < 0.1. Enable composite site (composite module), CDN, tagged caching, WebP/AVIF, lazy loading. SEO: Schema.org via JSON-LD, auto-generation of sitemap.xml via seo module, canonical and hreflang for multilingual versions. robots.txt blocks /bitrix/ from indexing. CI/CD: Git, auto-deploy via GitLab CI, staging. DB migrations: sprint.migration module with versioning.

Process:

1. Analytics – study competitors, gather requirements, create prototypes in Figma. Output: technical specification with user stories.
2. Design – UI/UX with design system. Components are reusable.
3. Development – write components with custom templates in local/templates/. Business logic in local/modules/.
4. Testing – functional, cross-browser, load testing (up to 1000 requests). Critical bugs fixed before launch.
5. Launch – deploy to production, monitoring via UptimeRobot, alerts in Telegram. Fixes for first 48 hours.

Multilingual support and redesign

Full localization via language files lang/ and SITE_ID mechanism. hreflang for each version. Regional versions with different prices and content – IP detection (main.geo) or manual selection. Multidomain – unified management of multiple domains.

Redesign without losing rankings: performance audit (PageSpeed, WebPageTest), SEO (Screaming Frog). New template in local/templates/ with preserved URL structure. 301 redirects only if URL changes significantly. Kernel update, migration to D7 ORM, infoblock restructuring, migration via sprint.migration with Git.

Guarantee and support

We have been working with 1C-Bitrix for 12+ years, completed 500+ projects. Certified developers on staff. Fixed price in contract – no surprises. Warranty period covers code errors. After warranty, subscription packages with SLA (response time 2 hours, resolution 8 hours). 24/7 availability monitoring, alerts in Telegram. Get a consultation and preliminary estimate: contact us via the form on the website or chat – we'll respond within an hour. Order turnkey development – we'll design infoblocks, integrate 1C, and speed up the catalog. If you already have a site on another CMS, order a performance audit and migration to Bitrix.