Final Notes

Summary and Recommendations

Optimizely Frontend Hosting is a streamlined solution for deploying headless Next.js applications in enterprise environments, especially for teams already using Optimizely DXP. It provides integrated hosting with global CDN, WAF, and ready-to-use environments—without the need to manage infrastructure manually.

Recommended Practices

• Start with the Deployment API
  Use the Deployment API first to understand the full deployment lifecycle. This helps you customize the flow to your needs and makes troubleshooting much easier when something goes wrong.
• Set Environment Variables Before Deploying
  Always configure all necessary environment variables in the PaaS Portal before triggering the deployment.

  🛑 Launching a deployment without them will cause the production build to fail, as the build runs immediately and depends on these variables. A failed build can lock your environment temporarily.
  👉 Set variables first, then deploy.

• Follow ZIP Naming Convention
  Use the format:
  <project-name>.head.app.<version>.zip
  Example: commercestore.head.app.1.0.0.zip
• Exclude node_modules and .next Folders
  These directories are not needed in the deployment ZIP and will only bloat your package, slowing down uploads unnecessarily.
• Try the @kunalshetye/opticloud Package
  This CLI tool simplifies the entire deployment process—from zipping to uploading and releasing. It's especially useful for developers new to Optimizely or not familiar with PowerShell or DXP internals.
  👉 npmjs.com/package/@kunalshetye/opticloud

By following these tips, you’ll ensure smoother, faster, and more reliable deployments with Optimizely Frontend Hosting.