Kindergarten Website on 1C-Bitrix Development

Parents complain about lack of information, educators drown in dozens of messengers, and inspecting authorities find inconsistencies with Federal Law 273. We solve all three problems on the 1C-Bitrix platform—we create a turnkey kindergarten website that serves as both an official portal and a daily tool for parents. With over 7 years of experience and 50+ completed projects for kindergartens, we guarantee quality and compliance. Fines for non-compliance range from 30,000 to 100,000 rubles; our website development starts from 150,000 rubles and pays for itself within the first year. Infoblocks v2.0 allow managing mandatory sections, and tagged caching speeds up loading even with a large number of photos. The built-in access control system differentiates roles: administrator, educator, parent—each sees only their own information. Contact us for a consultation and an accurate budget estimate.

Why a Kindergarten Website Must Be on 1C-Bitrix?

The platform reduces educator workload by 70% and over 50% of parents use the dashboard daily. 99.9% uptime is guaranteed. Infoblocks v2.0 allow managing mandatory sections, and tagged caching speeds up loading even with a large number of photos. The built-in access control system differentiates roles: administrator, educator, parent—each sees only their own information.

What Is Included in the Deliverables Package?

• Mandatory sections under Federal Law 273—12 sections, each implemented via an infoblock or static page with the bitrix:news.detail component.
• Parent dashboard—event feed, photo reports, meal menu, online payment, archives.
• Online enrollment application—form linked to a Highload block, with statuses and notifications (email+SMS).
• Photo reports—drag-and-drop upload of up to 30 photos, automatic compression to 1920px, preview 400×400.
• Meal menu—weekly table with auto-fill.
• Documentation—description of infoblock structure, access rights scheme, content filling instructions.
• Staff training—2-hour webinar for educators and administrators.
• First month technical support—assistance during launch and bug fixes.

How Is the Parent Dashboard Implemented?

The parent dashboard is the main communication channel. After enrollment, the parent receives a login and password. The "parent → child → group" binding is implemented via user properties UF_CHILD_ID and UF_GROUP_ID. If there are several children in the family, the interface allows switching between them with one button.

Dashboard tabs:

• News feed—general event stream: announcements, photo reports, meal menu.
• Meal menu—current week with archive of past periods.
• Photo reports—daily group photos with Lightbox (Fancybox).
• Payment—current charges, history, online payment via integration with a payment gateway.
• Documents—contract, additional agreements, uploaded in PDF format.

Daily Photo Reports: Technical Implementation

The educator logs into the admin panel with rights to the "Photo Reports" section. A custom upload interface on the frontend accepts up to 30 photos, automatically compresses them to 1920px on the long side via CFile::ResizeImageGet, and generates a 400×400 preview. The "Photo Reports" infoblock contains a link to the group, date, description, and gallery. In the dashboard, photos are filtered by the child's group and displayed in reverse chronological order. Upon publication, the OnAfterIBlockElementAdd event is triggered—parents receive a push notification or email with a preview of the first 4 photos.

Privacy: files are stored outside DOCUMENT_ROOT, served via a proxy script with session verification. Direct links do not work, and photo reports older than 6 months are moved by an agent to an archive infoblock.

Meal Menu

The "Meal Menu" infoblock—one element per day with breakfast, lunch, afternoon snack, dinner descriptions. The educator fills it out a week in advance. In the dashboard it is displayed as a table:

How Do We Guarantee Compliance with Federal Law 273?

Article 29 of the "Education" law obliges educational organizations to post 12 mandatory sections on the website. Missing any one is grounds for a citation during inspection. We implement each section as a separate infoblock or static page, and for navigation we create a fixed menu "Information about the Educational Organization". Savings on fines for non-compliance can be significant (fines from 30,000 to 100,000 rubles). Our clients pass Rosobrnadzor inspections without comments.

Comparison: Our Parent Dashboard vs. Messengers

Our parent dashboard reduces the load on educators by three times compared to WhatsApp mailing. Instead of dozens of identical messages—one publication that automatically notifies all parents. No need to check who has read it: the system itself tracks views and can send a repeat notification. Parents do not lose important announcements in chats, and educators save 30–40 minutes per day (equivalent to 5,000 rubles/month). The Bitrix site generates reports 10 times faster than manual collection from messengers.

How Development Proceeds

1. Analysis—audit of requirements, document collection, section structure.
2. Design—prototypes, infoblock scheme, roles and permissions.
3. Layout—mockups of main page, internal pages, dashboard, responsive.
4. Programming—frontend, integration, component writing, caching setup.
5. Testing and launch—content filling, compliance check with Federal Law 273, deployment.

Implementation Timeline

Total duration—8–11 weeks. Cost is calculated individually based on complexity, but on average the project pays for itself through savings on fines and optimization of educator workload. For common questions, see our FAQ section below. The critical path is the dashboard with photo reports: it determines whether parents will use the site daily. Request a consultation—we will prepare a budget for your project.

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.