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.detailcomponent. - 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:
| Meal | Monday | Tuesday | Wednesday | Thursday | Friday |
|---|---|---|---|---|---|
| Breakfast | Oatmeal, cocoa | Omelet, tea | Cottage cheese, yogurt | Millet porridge, compote | Pancakes, milk |
| Lunch | Chicken soup, cutlet, compote | Borscht, fish, jelly | Pickle soup, pasta, juice | Shchi, meatballs, tea | Pea soup, cutlet, compote |
| Snack | Cottage cheese casserole | Fruits, cookies | Syrniki, sour cream | Yogurt, bun | Cake, tea |
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
- Analysis—audit of requirements, document collection, section structure.
- Design—prototypes, infoblock scheme, roles and permissions.
- Layout—mockups of main page, internal pages, dashboard, responsive.
- Programming—frontend, integration, component writing, caching setup.
- Testing and launch—content filling, compliance check with Federal Law 273, deployment.
Implementation Timeline
| Stage | Content | Duration |
|---|---|---|
| Analysis | Audit of requirements under 273-FZ, section structure, TOR for dashboard | 5–7 days |
| Design | Prototypes, infoblock structure, roles and permissions | 5–7 days |
| Layout | Mockups (main page, sections, dashboard), responsive | 10–12 days |
| Mandatory sections | Frontend and integration of all sections under 273-FZ | 10–12 days |
| Parent dashboard | Authorization, photo reports, menu, announcements, payment | 14–18 days |
| Enrollment form | Form, statuses, notifications | 5–7 days |
| Content & launch | Filling mandatory sections, testing, deployment | 7–10 days |
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.