MultiConnectCloud › Website Deployments
2. Supported frameworks
On the form this is the Platform field. It sets the default build output folder, and it cannot be changed after the website is created: the Update form shows it, but locked.
| Platform | Default output folder | Build command shown on the form |
|---|---|---|
| React (Create React App) | build |
npm run build |
| React (Vite) | dist |
npm run build |
| Vue.js | dist |
npm run build |
| Angular | dist |
ng build --configuration production |
| Svelte / SvelteKit | build |
npm run build |
| Next.js (Static Export) | out |
npx next build |
| Gatsby | public |
npx gatsby build |
| Blazor WebAssembly (.NET 6 – 10) | wwwroot |
dotnet publish -c Release |
| Hugo | public |
hugo |
| Plain HTML/CSS/JS | . (the top of the zip) |
No build step |
Notes for some frameworks:
- Angular. The default output folder is
dist, but Angular CLI 17 and later write the site todist/<project-name>/browser. Leave Build Output Directory blank and the folder is found for you, or set it todist/<project-name>/browserif that is where yourindex.htmlis. - Next.js. Only a static export works. Set
output: 'export'innext.config.jsbefore you build. A Next.js app that needs a server at request time is not a website deployment. - SvelteKit. Use the static adapter, so the build is a folder of files.
- Blazor WebAssembly.
dotnet publishputs the site in awwwrootfolder inside the publish folder. Zip the contents ofwwwroot, or zip the whole publish folder and leave Build Output Directory blank. Blazor's_frameworkfiles are always re-checked by browsers, so a new deploy never mixes old and new files. With Compression on, the.gzfiles thatdotnet publishwrites are sent as they are.

