E7A / 04.04
Back to archive

04 / Record

Primary focus

2023—present

AIS “Unified Admissions Campaign”

Practice

Frontend / CRM / integrations / technical leadership

Frontend development of a city information system supporting admissions and vocational education workflows in Moscow — from a Laravel 9 / Blade frontend shell working over a separate backend API to an independent Vue 3 platform with registries, applications, analytics, call-center, helpdesk, queueing and specialized operational workspaces.

Scope of work

  1. 01

    Primary responsibility: frontend architecture, user flows, client state, components and API integration

  2. 02

    Migration from Laravel 9 + Blade/server-rendered HTML, where the UI layer manually bridged a separate API, to an independent Vue SPA with a stable frontend/backend boundary

  3. 03

    Registries for applicants, applications, organizations, employees, programs, specialties and slots

  4. 04

    Admissions campaigns, entrance examinations, commissions, application monitoring and operational dashboards

  5. 05

    Call-center, helpdesk, events, forms, QR workflows, queues, public-facing and terminal interfaces

  6. 06

    Analytics, reporting, data import/export, realtime/WebSocket flows and role-based access

  7. 07

    Backend involvement when needed: code review, acceptance of changes and integrations, API contract validation and closing critical product gaps

  8. 08

    Since March 2026 — senior frontend responsibilities: technical review, acceptance, task decomposition and coordination of other frontend developers

Technology chronology

Generation 0 / Laravel frontend shell

Laravel 9 / Blade / Bootstrap 5.1 / Laravel Mix 6 / 2023

The 2023 archived state is now confirmed by source code. Laravel acted as a frontend shell: Blade rendered pages while data came from a separate backend API through APP_API_SB. Browser code used jQuery AJAX, async/await and Promise.all, some requests went through a Laravel Http helper, and Axios 0.25 was also present in the frontend dependencies. Growing async complexity and manual request coordination became one of the reasons to move to a standalone Vue frontend.

Generation 1 / Vue SPA

0.0.47 → 0.0.48 / 03.2024

The first preserved Git snapshot of the standalone frontend. Vue 3.4.7, Vite 4.5.1, TypeScript 5.3.3, Vuetify 3.3.21, Pinia 2.1.7 and Vue Router 4.2.5, with independent routing, state, access control and realtime flows.

Generation 2 / Operational CRM

0.3.0 → 0.3.7 / 01.2025

The next frontend generation: Vue 3.4.35, Vite 5.3.5, TypeScript 5.5.4, Vuetify 3.6.13, Pinia 2.2.0 and Vue Router 4.4.0. The product evolved from an administrative panel into a specialized operational CRM.

Generation 3 / Platform

0.3.753 snapshot → prod v0.3.1255-69b89a34

The current generation. The core stack is stable while development focuses on domain modules and engineering maturity: admission 2026, helpdesk, queues, commissions, feature modules, Vitest/Vue Test Utils, API + WebSocket and a multi-environment release flow. The provided source snapshot is version 0.3.753; current production is v0.3.1255-69b89a34.

Versions and dates reflect states confirmed by archives, Git history or releases and do not imply that every component was used in every deployment.

Contact
Copied