Supported frameworks for AI website hosting.

A build can succeed while its files sit in a folder the publishing path does not expect. Do not assume `dist`, `build`, `out`, `public`, `_site` and `site` mean the same thing.

Next.js, Nuxt and SvelteKit can look static while still requiring server-side rendering. Configure and test a real static export before choosing static hosting.

Recognised frontend projects need a usable npm build script. Fix missing dependencies and failed build steps in GitHub before publishing again.

Static output can safely contain only values intended to be public in the browser. A secret needed at request time means the project needs a server-side component.

Test the production build locally. A failed dependency install or unsupported native dependency is a project issue, not a reason to edit server files manually.

Test relative/base paths in the built site. If images, fonts or scripts are missing, inspect the project build and deployment result first.

Run the project’s normal production build and inspect the generated dist directory. Check that your main pages, images and browser-side navigation work from the built result. Vite is a recognised current static pattern, but your own base-path and asset settings are still part of the project.

Astro is a good fit when it generates static output. Build the project, inspect dist, and check that any integrations do not change the site into a request-time server application. A fast static site can still include external forms or analytics; those services remain separate from the static host.

Use a real static-export configuration, not a development server as a stand-in for production. Next.js documents static export with output: 'export'; a successful build creates an out directory containing static assets. Server actions, dynamic request behaviour and other server-only features do not fit this route.

For Vite-based projects, use the normal build command and inspect dist. For an older Create React App project, inspect build. If a React or Vue project uses a custom server, protected API or process at request time, assess whether it meets the separate managed Node contract.

Docusaurus, Eleventy, Hugo, Jekyll and MkDocs are all capable of producing static pages, but their normal tools and output folders differ. A framework that produces files is not automatically a supported build contract. Review whether your project needs npm, Ruby, Python, Go or a non-standard output location before treating it as ready.

Claude Code, Cursor, Lovable, Bolt, v0, ChatGPT and Gemini can help create a website. They are not by themselves a hosting compatibility signal or a Host Luma integration. Open the repository, identify the framework, run the production build and check whether the published result can be static or meet the supported managed Node contract.

A landing page built with React can be static when the build creates browser files and all visitor interaction happens in the browser or through an external service. Host Luma can assess that static output.

The same React interface becomes a different hosting requirement if it depends on a custom API, session server, database query or request-time authentication controlled by the application.

Next.js, Nuxt and SvelteKit can all generate static pages in one configuration and require an application runtime in another. Check the real production output, not the development command.

The current workflow gives a successful supported project a permanent HTTPS preview URL. It is useful for review and sharing; it does not turn a server-dependent application into a static site.