We built a Grav CMS website for Sobol school with a shop, timetable and three types of enquiries. This case covers the development work and the checks recorded in the report dated 2 October 2026.
Project website: Sobol School
What needed to change
The school needs to update its timetable, events, news and class prices. Its website also needs a working shop and training registration.
We split the work into the theme and CMS settings, public sections and enquiry storage. Each part was checked separately.
Work and results
| Work | Result | Period or source |
|---|---|---|
| A website managed through a CMS | 12 public sections checked: HTTP 200 | Based on the report dated 2 October 2026 |
| Enquiries and a secure connection | 3 enquiry types stored in the admin area | Based on the report dated 2 October 2026 |
A website managed through a CMS
12 public sections checked: HTTP 200 · Based on the report dated 2 October 2026
We built the theme and set up content editing in Grav. We added a shop, gallery, news, events, timetable and a class price calculator.
According to the report dated 2 October, all 12 public sections checked returned HTTP 200: the pages opened on the date of the check.
Staff can change information pages through the CMS without editing the template. New shop features still require development and testing.
Enquiries and a secure connection
3 enquiry types stored in the admin area · Based on the report dated 2 October 2026
We set up training registration, event registration and shop orders. All three enquiry types are stored in the admin panel, where a saved record can confirm receipt.
We restored HTTPS and set up redirects from HTTP and the www domain. We checked the address each redirect leads to.
The screenshots show public pages on desktop and mobile. Visitors’ private enquiries are not published.
How we checked the results
The report dated 2 October records 12 accessible sections and three enquiry types stored in the admin panel. These are results from that date; they do not guarantee continuous availability.
For this case, we reopened the public website and captured desktop and mobile screenshots. We did not send new test enquiries to the school.
What to keep in mind
SMTP and Telegram setup remained on the original report’s task list. This case confirms enquiry storage in the CMS; it does not claim that every notification channel was launched.
The number of sections shows the scope of the check. Traffic, student numbers and shop sales were not assessed in this case.
Before similar work
If a website has several forms, test each one: whether the page opens, the data is saved and the notification arrives. Record the outcome of each step separately.