What Templates Does Makedraft Offer to Start a Project?
Updated
Makedraft lists templates in four categories: Apps and Games, Landing Pages, Components, and Dashboards. You can start from any of them, or browse the full set from the Templates link in the site navigation. Each template gives you a working starting point that you then customize through chat, where every message opens a real branch in a real GitHub repo and deploys automatically.
Template Categories
| Category | What it's for |
|---|---|
| Apps and Games | Interactive projects, including playgrounds and small game-style apps |
| Landing Pages | Marketing and product pages for launches or campaigns |
| Components | Reusable UI pieces you can build into a larger project |
| Dashboards | Data-focused internal tools and admin views |
Example Templates Shown on the Site
The homepage highlights a few templates with usage counts, which gives a rough sense of what other builders pick:
- Image Generation Playground (6.6K uses, 733 likes) — an app-style template for experimenting with image generation.
- Brillance SaaS Landing Page (14.5K uses, 2.1K likes) — the most-used example listed, aimed at SaaS product pages.
- 3D Gallery Photography Template (3.5K uses, 880 likes) — a visual portfolio-style landing page.
- Optimus – The AI platform to build and ship (9.1K uses, 1.4K likes) — another landing page starting point.
- Grok Creative Studio (1.1K uses, 113 likes) and Globe To Map Transform (2.4K uses, 682 likes) — smaller app-style examples.
Usage and like counts are as displayed on the homepage and will change over time.
How Starting From a Template Works
- Pick a template from a category or the full template list.
- Start a chat — your first message opens a real branch in a real GitHub repo, with no sandbox or throwaway preview.
- Customize in chat — describe changes and the agent commits them; each commit redeploys that branch as its own live service.
- Verify — check the live deployment for the branch to confirm the change shipped.
- Go further — point a custom domain at what you build instead of staying on a shared subdomain.
Templates work with React and Next.js projects, and the stack runs on GitHub, Render, Supabase, and Stripe.
Choosing Between Templates and a Blank Start
- Start from a template if you want a known layout or app pattern (a SaaS landing page, a dashboard, a playground) and plan to adjust it in chat.
- Start from scratch if your project doesn't resemble any listed category and you'd rather define structure through your first messages.
Either way, the output is your repo — one builder noted there was "nothing to migrate" because the project was already in their GitHub from the start.
Common Snags
- Template fit: a template is a starting point, not a fixed product; expect to rewrite sections in chat rather than configure settings.
- Model choice: if a chat gets stuck, Pro and Business plans let you switch the AI model on that chat instead of starting over.
- Deploy timing: deployments follow commits automatically, so check the branch's live service after approving changes rather than looking for a separate deploy step.
For plan details and what each tier includes, see the Pricing page.