does.software
English Español Català
sign in
faq
English Español Català
sign inclaim a name
questions45guides4

guides

The walkthroughs for what a short answer never quite covers. Each one is one task from start to finish, with the real limits written down instead of implied, in about a thousand words. For the quick version, the questions tab is next door.

publish a site from your github repoImport a repository, serve it at your own name and redeploy on every push. No build server, no DNS, HTTPS included.a real email address without buying a domainForward mail from your own name to the inbox you already read, or keep a full mailbox on it. What each one can and cannot do.one name, many destinationsHow the redirect works, what happens to the query string, and how path rules turn a subdomain into a set of short links you can measure.a subdomain or your own domainWhat you give up, what you save, and the cases where a name under does.software is the wrong answer.

what is inside each one

publish a site from your github repo

  • what you get
  • what your repo has to contain
  • import it
  • deploy on every push
  • single-page apps and 404s
  • the limits

a real email address without buying a domain

  • forwarding or a real mailbox
  • set up forwarding
  • what forwarding cannot do
  • a real mailbox, on pro
  • the limits

one name, many destinations

  • what the redirect actually does
  • path rules
  • a path with no rule
  • short links you can measure
  • the limits

a subdomain or your own domain

  • what each one actually is
  • where a subdomain wins
  • where it doesn't
  • what it costs over five years
  • moving later
claim your name