Developing a kindergarten website using 1C-Bitrix

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Our competencies:
Development stages
Latest works
  • image_website-b2b-advance_0.png
    B2B ADVANCE company website development
    1175
  • image_bitrix-bitrix-24-1c_fixper_448_0.png
    Website development for FIXPER company
    811
  • image_bitrix-bitrix-24-1c_development_of_an_online_appointment_booking_widget_for_a_medical_center_594_0.webp
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    564
  • image_bitrix-bitrix-24-1c_mirsanbel_458_0.webp
    Development based on 1C Enterprise for MIRSANBEL
    747
  • image_crm_dolbimby_434_0.webp
    Website development on CRM Bitrix24 for DOLBIMBY
    655
  • image_crm_technotorgcomplex_453_0.webp
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    976

Kindergarten Website Development on 1C-Bitrix

A kindergarten website is not a marketing landing. It is a mandatory tool regulated by federal legislation. The Law "On Education in the Russian Federation" (273-FZ) imposes specific requirements on the content of educational organization websites. Simultaneously, the website solves two practical tasks: attracting new parents and daily communication with current ones. On 1C-Bitrix, both tasks are solved using standard information blocks and a custom personal account.

Compliance with 273-FZ: Mandatory Sections

Article 29 of the law and the order of the Federal Service for Supervision in Education define the list of information that an educational organization must display on its website. Missing any section is grounds for a compliance notice during inspection.

Mandatory sections are implemented as static pages or information blocks:

  • Basic Information — full name, founder, creation date, address, working hours, contacts
  • Structure and Governance — organizational chart, names and contacts of leaders
  • Documents — charter, license, state accreditation certificate, internal regulations (information block with file properties, sorted by document type)
  • Education — implemented programs, number of students, languages of instruction
  • Educational Standards — Federal State Educational Standards for preschool
  • Management. Pedagogical Staff — names, positions, qualifications, experience
  • Material and Technical Resources — facilities, grounds, equipment
  • Paid Educational Services — list, procedure of provision
  • Financial and Economic Activity — plan, report
  • Vacant Places for Admission — by each age group
  • Accessible Environment — information for children with special needs
  • International Cooperation — even if none exists, section must be present

A separate menu item "Information on Educational Organization" is created for navigation through these sections with a fixed structure. Each subsection is a page with bitrix:news.detail component or static content in visual editor.

Groups and Educational Programs

The "Groups" information block contains information about each kindergarten group:

  • Name (string): "Sunshine", "Stars"
  • Age (list): 1.5–2, 2–3, 3–4, 4–5, 5–6, 6–7 years
  • Direction (list): classical, Montessori, bilingual, speech therapy
  • Teachers (binding): connection to "Pedagogical Staff" information block
  • Maximum Capacity (number)
  • Current Capacity (number)
  • Daily Schedule (HTML text): detailed timetable

Educational programs are a separate information block with PDF files, descriptions, and binding to age groups.

Virtual Tour

Parents want to see where their child will be. Photo gallery is grouped by zones: entrance, cloakroom, playroom, bedroom, dining room, gym, playground.

Technical implementation is an "Facilities" information block with multiple "Photos" property and binding to building/branch. On the frontend, photos are displayed in a slider (Swiper.js) with zone navigation. For a full 3D tour, Matterport embed or similar is connected via iframe on the element detail page.

Online Application for Enrollment

The application form collects child and parent data:

  • Child's name, date of birth
  • Parent's name, phone, email
  • Desired group / direction
  • Preferential category (if applicable)
  • Comment

Application creates an element in the "Enrollment Applications" Highload block with statuses: new → under review → interview invitation → enrolled → rejected. Parent can track status by application number through public page (without authorization, by number + phone).

Status change notifications are sent via email + SMS. On transition to "Interview Invitation", a letter is automatically generated with date, time, and list of required documents.

Pedagogical Staff

Information block with teacher cards: photo, name, position, education, qualification category, experience, awards, professional development certificates (file properties). For 273-FZ this is a mandatory section, but for marketing it also works — parents choose a kindergarten partly based on people.

Parent Personal Account: Deep-Dive

Personal account is the main communication channel between kindergarten and parents. Instead of dozens of messenger messages, printed announcements on the door, and verbal notices — a unified information point.

Account Structure

Account is accessible after authorization (login + password provided at enrollment). "Parent → Child → Group" binding is implemented through user properties (UF_CHILD_ID — binding to "Children" information block element, UF_GROUP_ID — to group). One parent can have multiple children — interface allows switching between them.

Account tabs:

  • Feed — general event stream: announcements, photo reports, menu
  • Meal Menu — for current week and archive
  • Photo Reports — daily photos from group
  • Announcements — notifications from administration and teacher
  • Payment — current charges, history, online payment
  • Documents — contract, additional agreements

Daily Photo Reports: Technical Implementation

Photo reports are the function parents visit the account for daily. Teacher photographs children during classes, walks, meals. Photos are published linked to group and date.

Upload. Teacher logs into admin panel (limited rights — only "Photo Reports" section). For simplicity, custom upload interface created on frontend: drag-and-drop zone accepts up to 30 photos, automatically compresses to 1920px on long side via PHP handler (module main, class CFile::ResizeImageGet), generates 400×400 thumbnails for feed.

"Photo Reports" information block contains:

  • Group (element binding)
  • Date (date-type property)
  • Description (string): "Drawing class", "Outdoor play"
  • Photos (multiple file-type property)

Display in Account. Component filters photo reports by current parent's child's group. Feed displayed in reverse chronological order: today's first, then yesterday's. Each block — date, description, thumbnail grid. Click opens Lightbox (Fancybox) with option to download original.

Notifications. When new photo report is published, OnAfterIBlockElementAdd event triggers, handler sends push notifications (if FCM connected) or email to group parents. For email, mail template with preview of first 4 photos is used.

Privacy. Photos accessible only to authorized parents of children from corresponding group. Rights check at component level in PHP, files stored outside DOCUMENT_ROOT and served via proxy script with session check. Direct file links don't work.

Archive. Photo reports older than 6 months moved by agent (CAgent) to archive information block. Account shows "Archive" button with month-by-month navigation.

Meal Menu

The "Meal Menu" information block contains one element per day with text description of breakfast, lunch, snack, dinner. Teacher or dietitian fills it a week ahead. In account displayed as table:

Meal Monday Tuesday ...
Breakfast Oat porridge, cocoa Omelette, tea ...
Lunch Chicken soup, cutlet, compote Borscht, fish, kisel ...
Snack Cottage cheese casserole Fruits, cookies ...

Implementation Timeline

Stage Content Timeline
Analysis 273-FZ requirements audit, section structure, personal account TZ 5–7 days
Design Prototypes, information block structure, roles and permissions 5–7 days
UI Design Mockups (homepage, sections, account), responsive design 10–12 days
Mandatory Sections Development and integration of all 273-FZ sections 10–12 days
Personal Account Authorization, photo reports, menu, announcements, payment 14–18 days
Enrollment Application Form, statuses, notifications 5–7 days
Content and Launch Mandatory sections population, testing, deployment 7–10 days

Total Timeline — 8–11 weeks. Critical path is personal account with photo reports: it determines whether parents will use the site daily or close the tab after first visit.