What you can build
Landing pages
Product launch, waitlist, “coming soon,” app pre-launch — a hero, a pitch, a
call to action.
Microsites
A small multi-page campaign site — story, product, FAQ, CTA — under one link.
Event & announcement pages
A conference, launch party, or webinar page with schedule and RSVP; or a “we
raised / we shipped / we partnered” announcement.
Link-in-bio & hubs
A one-page link hub for a profile, a campaign, or a press kit.
Build it and ship it
Ask AI for the page
Describe it to Claude, ChatGPT, or any AI: “a landing page for my app launch — a
headline, three benefits, a waitlist signup, in self-contained HTML.” For a
microsite, ask for a few linked pages. Want images? Ask for them, or let it use
placeholders.
Drop it into Shareable
Drag the HTML file — or the whole folder /
.zip for a multi-page microsite
with images — onto your pages. The
index.html is the landing page; its assets come along. Or ask your AI to
publish it for you over MCP.Make it yours
Publish, then set the link preview
so it looks sharp when shared, and point it at your
own domain if you want
launch.yourbrand.com.Making it do something — forms, signups, payments
A marketing page usually needs to capture something — an email, an RSVP, a payment. Shareable doesn’t run a server, so it doesn’t collect form submissions itself. Instead, wire your page to a service that does — the form runs from the visitor’s browser, so embeds and POST endpoints work normally:- Email / waitlist → a form service (Formspree, Tally), or an embedded Mailchimp / ConvertKit form.
- RSVPs → an RSVP form or a Google Form.
- Bookings → an embedded Calendly.
- Payments → a Stripe Payment Link or buy button.
Don’t put secrets in the page. Anything in your HTML/JS is visible to anyone who
opens it, so use a form service’s public embed or a Stripe Payment Link, never a
secret API key.
Where the line is
Shareable hosts the page; it isn’t a website platform. Reach for a site builder (Webflow, Framer) or app host (Vercel, Netlify) when you need:- A CMS or non-technical editing UI (here, you edit by re-prompting and re-uploading).
- Server-side logic — storing submissions yourself, your own API, A/B testing.
- A large, evolving multi-page site with shared nav and a content model — Shareable decks are best for small, fixed sets of pages.