Creative · Community report
Build and deploy a personal website
Five people on X say Muse built or redesigned a personal website for them, from a static catalog on free Cloudflare hosting to a one-page site made from WhatsApp voice notes in 30 minutes. These are individual reports, so below is what to give it and what to check before you deploy.
What you can get
What it is
Deployed website
A draft personal website, built, redesigned, or revamped, that reflects content you actually supplied, ready for your review before it goes live.
It came back right when
- The site reflects the content and facts you actually provided, not invented filler.
- Pages load and look correct on both desktop and mobile.
- Contact details, links, and any catalog or listing entries are accurate.
- The hosting and/or repository ownership is clear to you (who can update or take down the site).
The checks are editorial, not from the source.
- Gather your material
Text, photos, voice notes, or an existing site to redesign.
- Request a first draft
Ask for pages and design based only on what you supplied.
- Review before publishingStops for your approval
Check content, links, and design on desktop and mobile.
- Confirm hosting ownershipStops for your approval
Make sure you hold the login for the hosting account or repo.
Editorial, not from the source
Works when
- You have the raw material (writing, photos, or voice notes) but not the time or skill to assemble a site.
- A simple static site (a one-pager, a portfolio, a personal catalog) is enough; you're not building a complex web app.
- You're willing to review a draft and give feedback before anything goes live.
Does not work when
- You need e-commerce, user logins, or other dynamic features; these reports only describe static content sites.
- You have strict brand or design requirements that need a professional designer's sign-off.
- You want guaranteed uptime or support commitments; none of these reports mention a service-level agreement.
Build a personal website: review template
| Page or section | Source material it's based on | Status |
|---|---|---|
| [Homepage/about/portfolio] | [Your text, photos, or voice notes] | [Reviewed] |
| [Catalog or listed items, if any] | [What you supplied] | [Checked against source] |
| [Hosting / repository] | [Account or repo name] | [Access confirmed] |
The source case
On X, @StepintoBEra reports building a static personal catalog website entirely with Muse Digging up the cases, grading them, designing and coding the site. Static site, free Cloudflare hosting. Still adding cases as I find them. Four other X users describe building or redesigning a personal website the same way: @jeffb198712 says they used @bot together with Muse, working through GitHub and a home folder, to build and keep growing a personal site for articles and history, with no website-building skills of their own; @liveink says Muse redesigned their outdated founder homepage; @manicktweet says Muse built a one-page personal website entirely from spoken WhatsApp voice notes in 30 minutes, with no typing; @mayiapapaya4 says Muse revamped a UGC content creator's portfolio and saved them hours. These are five individual reports, checked on 2026-10-09, not evidence of what Muse will build for any particular site, audience or design. u/IamVirtualboy says Muse built a portfolio site from a resume, deployed it live and added the link to the resume; this does not show the exact prompt, the code quality or how much editing was needed. @GFX_Rayhan says their first website is now live and was designed and built with Muse AI, best viewed on desktop; the post does not show what content they supplied, what kind of site it is, how it was hosted or how much editing was needed.
A public report by someone outside this library. Not independently reproduced here.
From the source
Source excerpt
This was a fun experiment. Built the whole thing with @Muse. Digging up the cases, grading them, designing and coding the site. Static site, free Cloudflare hosting. Still adding cases as I find them.
Source excerpt
With no real website building skills, I used @bot and @Muse working through GitHub and a home folder on my laptop to build a website where I post articles and history, free for anyone to read. It has only been live for 3 days I work on it after work in my spare time, it will continue to grow daily!
Source excerpt
i had @Muse redo my homepage this morning. every founder's site is a resume frozen in 2019. mine was telling an old story.
Source excerpt
I built this website by just talking. 30 minutes. Zero typing. ... Then Meta Muse did it for me. In 30 minutes. Without me typing a single word. ... Here's all I did: I spoke into WhatsApp. Just voice notes. I told Meta Muse everything about me.
Source excerpt
Just revamped my UGC Portfolio by using @muse and it saved me HOURS of time
Source excerpt
I told my AI assistant to build a portfolio site from just my resume and put it online. It came back with a full site.
Source excerpt
Designed and built with Muse AI. Best experienced on desktop — take a look:
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring Your own content: text, photos, or voice notes about what the site should say, A hosting or repository destination (e.g., Cloudflare, GitHub). Acts Publishes a live, public website once you approve. May create or push to a GitHub repository. Source community report, checked 2026-10-21.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
Other ways to ask
Editorial rewrites of the brief above, for a different emphasis. Copy them separately.
What you need
Editorial, not from the source
You supply
- Your own content: text, photos, or voice notes about what the site should say
- A hosting or repository destination (e.g., Cloudflare, GitHub)
Connected
- A static hosting account (Cloudflare or similar)
- A GitHub repository, if you want the code kept and versioned
- A messaging channel such as WhatsApp, if you want to build through voice notes
Approved by you
- Approval before the site is published live
- Approval before any repository is created or pushed to
How to try it
Editorial, not from the source
- Decide what the site needs to do, who you are, and what you want listed (an about page, a portfolio, a catalog), and gather the writing or photos you already have.
- Give Muse the raw material, whether typed notes, voice notes, or an existing repo or folder, and ask for a first draft of pages and design.
- Review the draft in your own voice, checking content against what you actually supplied, and send feedback or corrections to Muse.
- Confirm hosting (a static host such as Cloudflare, or your own GitHub repo) before anything goes live, and check the published site yourself on desktop and mobile.
Start from the material you already have
These reports describe three different starting points: typed notes and an existing repo, spoken voice notes with no typing at all, and an already-live site in need of a redesign. In each case the author supplied the raw material themselves, whether that was years of writing and research, photos and a personal story told aloud, or an outdated homepage used as the baseline to improve on. None of the reports describe Muse inventing a persona or a biography from nothing. Before asking for a build, gather what you actually have: the text you want published, the photos or portfolio pieces, or the specific site you want reworked. The richer and more specific that material is, the closer the first draft is likely to land, and the easier it is to check the result against something real rather than judging it on tone alone.
Expect a draft, not a finished publish
None of the five reports describe a site going live without the author looking at it first. One account built an entire site through spoken WhatsApp voice notes and still describes checking the finished one-pager before treating it as done; another says they are "still adding cases as I find them," meaning the site keeps changing after the initial build. Treat the first result as a draft: read it the way a visitor would, check that your name, photos, links and any listed items are correct, and look for generic filler text that doesn't match what you actually said. A personal site carries your name and contact details, so a mistake is more visible and more awkward to fix after the fact than catching it before the link is shared.
Keep track of who holds the keys afterward
A static site built this way usually depends on a hosting account (one report names free Cloudflare hosting) and sometimes a GitHub repository holding the code, as another report describes working through "GitHub and a home folder." None of the five reports say who retains access to that hosting account or repository once the build is done, or what happens if you want to move hosts, add a custom domain, or hand the site to someone else later. Before you treat the project as finished, confirm you, or whoever should, actually has the login details and can get back into the account without Muse. A personal site is meant to last longer than the chat session that built it, so ownership of the account is worth settling early rather than discovering it's missing when you need to make a change.
Open Muse to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
Limits to confirm
- Five individual reports, no two from the same build; they do not show what Muse would produce for your own content, structure or design preferences.
- Three of the five reports give no build time or revision detail; only one states a time (30 minutes, for a one-page site built entirely from voice notes).
- None of the reports say whether Muse covers ongoing hosting or domain costs, or who is responsible for keeping the site updated after launch.
- The exact scope of "the cases" in the first report (what kind of cases, how many) is not stated.
Stop and check
Editorial, not from the source
- Before the first draft: confirm what content Muse has to work with and what's still missing.
- Before anything is pushed to a repo or host: review the draft pages yourself.
- Before you share the link: check the live site on both desktop and mobile.
If it goes wrong
Editorial, not from the source
- The site includes generic placeholder content instead of your material
- Supply the actual text, photos or voice notes directly, and check the draft against your own source material line by line before approving.
- You're not sure who owns the hosting account or repository afterward
- Confirm this before publishing; none of the reports state who keeps access to the Cloudflare account or GitHub repo after launch.
- Voice-note or chat-built instructions get misheard or missed
- Review the draft against what you actually said, and resend any correction as a short, explicit note rather than assuming it will be caught.
Common questions
Can Muse really build a personal website from scratch?
Some users report that it has. One account describes a static catalog site built and coded entirely with Muse and hosted free on Cloudflare; another says a one-page site was built in 30 minutes from spoken voice notes with no typing at all. These are individual reports, not evidence of what Muse will build for your content or design preferences.
Do I need to know how to code?
No report required it. One author explicitly says they had no real website building skills and worked through GitHub and a home folder with Muse's help; another built their site purely by speaking into WhatsApp. Neither report mentions the author writing any code themselves.
Can Muse redesign an existing site instead of building a new one?
One report describes exactly that: Muse redesigning an outdated founder homepage the same morning it was asked. The post gives no detail on what changed or how long it took.
Where does the finished site get hosted?
The reports mention free Cloudflare hosting and a GitHub repository as destinations, but neither is guaranteed for every build. Confirm the hosting plan and who controls the account before you call the project done.
How much of the content does Muse write versus the user?
The reports describe the user supplying the material: photos, a personal story, or existing writing and research. None describe Muse inventing biographical details the user did not provide; check the draft against what you actually gave it.
Next
Related to this task
More in Creative
Similar tasks
Get recurring task recommendations — ask your own agent to check for relevant updates.