Extend Build Pipeline to Support Multiple Deployment Targets (Git, S3, Custom Destinations)

[christophmatt]

Is your feature request related to a problem? Please describe.
No.

Describe the solution you'd like
Enhance the build process to support multiple deployment targets beyond the default main page output.

After a successful build, it should be possible to:

• Push artifacts to a Git repository
• Upload artifacts to an S3-compatible object storage
• Deploy to alternative/custom destinations
• Define configurable output targets

The goal is to make the build system more flexible and usable in modern CI/CD pipelines.

Describe alternatives you've considered

• Keeping the current static output behavior (too limited for advanced deployment workflows).
• Using external deployment scripts only (less integrated and harder to standardize).
• Manual artifact handling outside the build system (not scalable).

Additional context
The enhancement should:

• Allow pluggable deployment targets
• Support S3-compatible storage (not limited to AWS)
• Allow Git push (e.g., to a deployment branch or dedicated repository)
• Support environment-based configuration (dev/stage/prod)
• Be usable in CI environments

Optional implementation ideas:

• Introduce a deploy stage after build
• Use a configurable target interface
• Allow multiple deployment targets per build
• Provide CLI flags or config file-based target definitions