Generating static websites and React applications

Codexe generates two kinds of web project. A static site is plain HTML, CSS and JavaScript that runs by opening a file or dropping it on any host. A React application is a component-based project for interfaces with real state and routing.

Static output has no build step and no dependencies. That makes it the right choice for landing pages, portfolios, documentation pages and server websites - anything where the content is the point.

my-site/
├── index.html
├── css/styles.css
├── js/main.js
└── assets/

Because there is nothing to compile, you can host it anywhere: GitHub Pages, Netlify, Cloudflare Pages, or a plain nginx directory. Ask for responsive layout in your prompt if you want mobile breakpoints included.

React projects come as a component tree with the entry point, routing and state wiring already in place. Use this when the interface has genuine interactivity - dashboards, multi-step forms, anything driven by data that changes.

my-app/
├── package.json
├── index.html
└── src/
    ├── main.jsx
    ├── App.jsx
    └── components/

Install dependencies and run the dev server the usual way. Nothing in the output is Codexe-specific - it is a standard project you can take anywhere.

• Content that mostly sits still - static site.
• Interface state, filtering, multiple views - React.
• Not sure - start static. Moving simple markup into React later is much easier than the reverse.

Both targets produce front-end code. They do not provision a backend, a database or hosting. If your site needs to persist data you will need to supply an API for it to talk to.

Use the website generator for static sites, or the React app generator for component-based applications.