Skip to content

Start building your next app or website — with AI, right in your browser.

Visit devdojo.com
Docs
Publishing & Community

Designs 03 / 03

Publishing & Community

Every design gets a public URL automatically, stays current as you build, and can be reused, remixed, and inserted into Sites through the Library.

Designs are public by default. The moment there's something on the canvas, your design has a live URL — and it keeps up with your edits on its own. The Library is where published designs live, get discovered, get remixed, and get inserted into Sites.

Your design's public link

Every design is served at:

https://devdojo.com/design/{slug}

You don't have to publish it. The first thing you build goes live on its own, and every edit after that — an AI turn, a hand edit, a restored version — reaches the link a few seconds later. Nothing to remember, nothing to press.

The Share button in the Designer gives you that URL with a Copy button, View live ↗, and Update now if you'd rather not wait the few seconds.

The live page is a snapshot, not a live render of your canvas — it's cut fresh after each edit rather than assembled per visitor. That's what makes it fast, and it's the copy Remix clones, so a half-finished experiment can never be what someone else forks mid-keystroke.

Want a design kept private? Not yet — that's coming as a Pro option. For now every design you make is reachable at its link by anyone who has it. It isn't listed anywhere public until you submit it to Community, but treat the URL as shareable.

Built, not compiled in the browser

A published design ships a real, minified stylesheet built ahead of time — not the Tailwind browser compiler. That's a few KB of CSS instead of ~70KB of blocking JavaScript, and the page arrives styled rather than painting bare markup first and catching up a moment later.

The workspace canvas is the deliberate exception: it keeps the browser compiler so a class you (or the assistant) typed a second ago styles itself instantly, with no build step in between.

Four URLs, four audiences. The workspace preview iframe is yours alone. /design/preview/{slug} is the viewer — your always-current draft framed with a device toggle, openable by you and by DevDojo admins (which is how a design gets picked for the showcase). /design/raw/{slug} is the bare document that viewer frames, and the rehearsal of the published page in a full tab. /design/{slug} is the public page. The draft surfaces build their CSS exactly the way publishing does, so they're a rehearsal of the real thing rather than an approximation.

Where published designs are listed

Three public surfaces, and they list different things:

  • /designs is the showcase — designs a DevDojo admin has hand-picked, led by the newest additions and followed by the featured model comparisons. Getting listed here is an editorial decision, not something publishing does on its own.
  • /sections is the section library — the official DevDojo Blocks collection of reusable heroes, pricing tables, footers and the rest, published by the DevDojo account and marked with a black DevDojo badge. Searchable and filterable by category, 24 per page.
  • /dashboard/designs is your work plus the Community catalog you can remix from.

Cards on all of them draw a captured screenshot rather than a live copy of the page, so a grid of two dozen designs costs one image each instead of two dozen full renders.

How a design gets featured

Featuring is admin-initiated and always makes a copy. When an admin features a design, DevDojo clones the currently published version into its own account as an immutable record, attributes you as the creator, and lists that copy on /designs. Later edits to your original never change it. An admin can retract a design from the showcase later; the copy and its URL survive, so a link someone already has keeps working.

Reusing and remixing

From a Site's Add section popup, a published design is vendored into the Site as owned code — copied in exactly as designed, no separate contract to satisfy. If you built it with the platform's semantic utility classes (bg-background, text-primary, …), it automatically renders in whatever values the host Site's own design tokens define, through ordinary CSS — the palette used while designing it isn't copied along. A design authored with raw hex values keeps its exact colors and typography wherever it lands.

Remix is how designs travel. Click Remix on any community card to clone that design's published snapshot into a brand-new design in your account and land straight in the workspace — the original stays untouched, and the owner's private draft is never exposed. The copy remembers where it came from, and from there it's fully yours: iterate with the AI, restyle it, publish your own version.

Exporting a design

Published or not, a design can leave DevDojo whenever you want:

  • Download ZIP (workspace menu → Export, or the card menu in My Designs) produces a small static project — index.html, js/script.js, a README.md, and either a css/style.css (Tailwind off) or the Tailwind setup inlined (Tailwind on). Unzip and open it anywhere; no build step required.
  • Copy the code straight from the HTML/CSS/JS editors.
  • Duplicate Design makes a full private copy ("Copy of …") inside your account — handy for trying a risky direction without touching the original.

Where to go next

  • The Designer — everything about the workspace you'll be remixing in.
  • Designs Overview — what designs are and how the library is organized.
© 2026 DevDojo Edit this page