Corporate Website Handover Prep

Below is the auto-generated project description, but the first step I need is to take the Visual studio package and the back up from my site and assess that the next.js code on my site can be opened and is functional. The VS package is not the current version on my site. The current developer is unreachable so I do not have a current VS package.

Auto generated project description below.

I need a meticulous developer to audit my corporate site’s codebase and package it for a smooth transition to a new team. All current assets—HTML / CSS, JavaScript, and the existing backend server files—are already on a private repo. Your first task is to verify that nothing is missing, flag any broken links between front- and back-end modules, and identify third-party libraries or frameworks that may have slipped in (I’m not a web designer, so I’m unsure what is there).

Once the audit is done, organise everything into a clean folder structure, remove obvious clutter, and create concise documentation that explains how to spin the project up locally and deploy it to production. A Git tag or release archive plus a clear README will be the final package I pass to the incoming developer.

Deliverables:
• Full file inventory and dependency list
• Tidied, well-structured project directory (ZIP or Git release)
• README with setup, build and deployment steps

A short screen-share or written summary confirming the handover package is complete will wrap things up.