How did you handle build artifacts in this deployment approach?

When approaching deployment, when the frontend build is done separately (for example, through CI/CD), the build artifacts (compiled files — HTML, CSS, JS) are usually stored in an artifact repository or storage (for example, Artifactory, Nexus, S3).

Then these artifacts are used for deployment to servers or CDN. This approach allows:

• Isolating the build process from the deployment process.
• Reusing specific build versions.
• Ensuring rollback to previous versions if necessary.

Example: after a successful build in CI, the system uploads artifacts to S3, and then the deployment script downloads them and places them on the server or in the CDN.