Overview
This project concerns a new frontend for the existing Jiajiankang administrative system. The work connects a Vue and TypeScript interface using Vben Admin with an established backend and permission model. The broader technology context includes Java / Spring, MySQL, and Redis.
Modernization here involves more than the appearance of individual screens. The interface needs to connect to the system’s existing login flow, menu permissions, and APIs, while the older backend still has to build and start for integration work to proceed.
My contribution
My contribution covers frontend migration and interface adaptation, together with work on the older backend’s build and startup. The integration scope includes login, menu permissions, and read-only validation. These pieces connect the new frontend to the behavior already defined by the existing system.
- Sign in
- Resolve menu permissions
- Open read-only views
- Connect existing APIs
Integration flow
The diagram follows a user-facing path from login through menu permissions to a read-only interface connected with existing APIs. These steps bring together identity, access, and data presentation: the interface needs both the right information and the appropriate permission to show it.
Engineering focus
Important questions include whether the new interface reflects the permission model consistently and whether its requests match the existing API contracts. Backend startup is another practical dependency: an interface cannot be evaluated in context if its supporting service is unavailable. These relationships make the migration an integration problem as well as an interface problem.
Status & scope
This internship project covers migration and read-only integration. It does not claim that the entire production system has been replaced. Login and automated checks provide bounded functional evidence; long-term stability in a real environment requires a separate assessment.