Skip to content
Codex DesignBETA

Landing page HTML to production code prompt for Codex

Rebuild the approved HTML landing page in your real stack, such as Next.js and Tailwind, with your own components and the copy left as it is.

Prompt
Rebuild landing.html as a [Next.js] page using [Tailwind CSS] and our existing components in [src/components]. Match the layout, spacing, and type sizes of the HTML file, make it responsive between 390px and 1440px, and keep the copy exactly as it is.
Works with
Codex
From the set
Landing pages

About this prompt

Here the HTML file stops being the design and becomes the spec. Codex rebuilds landing.html as a page in your codebase, matching its layout, spacing and type sizes, using your existing components where they fit, making it responsive between 390px and 1440px, and keeping every word of the copy.

Replace the brackets with your framework, styling approach and components folder; an Astro page with CSS modules works as well as Next.js with Tailwind. If your file has a different name or lives in a subfolder, give its real path. Mention the 390px file from the mobile check too, so Codex has a reference for the small-screen layout instead of guessing it.

With a large component library, ask Codex to build the page section by section and compare each one with the HTML at the same width before going on. This step reads and writes your repository, so run it in Codex inside your project rather than in a chat window.

More prompts from this set

An independent plugin for Codex. Not affiliated with or endorsed by OpenAI.