Skip to content

Content

Download .md

These rules cover every piece of interface copy in every product and role: labels, titles, hints, tooltips, toasts, error messages, empty states, dialogs, notifications and email. Legal documents, such as agreement templates, are not interface copy.

  • Talk to people as “kamu” / “-mu”, never “Anda”. For example: “Akunmu sedang kami periksa.”
  • The company is “kami” only on screens clients read. On admin screens the readers are our own staff, so name the product (“Cover Clearance”), or leave the owner out.
  • Friendly, not over the top. A light nudge is fine (“Simpan dulu, lanjutkan kapan saja.”). Avoid heavy slang such as “gak”, “banget”, or “yuk” in every sentence.
  • Short and active, one idea per sentence.
  • Say what the control does, not how the feature works.
  • No article numbers, legal terms or “perjanjian” in everyday copy. Write what it is for.
Don’t Do
Ke mana surat dan pemberitahuan terkait perjanjian dikirim. Ke sini kami kirim surat dan kabar penting untukmu.
Mohon maaf, data yang Anda masukkan tidak valid. Format email-nya belum pas.
  • A field hint is one practical sentence: what to fill in, an example, or a limit.
  • A tooltip is one sentence. It names a control; it doesn’t explain the policy behind it.
  • The backend writes them. It validates every field and returns the message, so web and mobile show the same words.
  • The client only gates the button, for example by disabling “Kirim” until the required fields have a value. It never shows its own error text.
  • Say what to fix, in the “kamu” voice: “Email-nya belum diisi.”, “Judul lagunya belum diisi.”
  • Rupiah has two decimals: Rp4.812.500,00.
  • Dates read 14 Nov 2026; add the day for schedules: Sab, 22 Nov 2026.
  • Use tabular-nums for numbers in tables and stats.
Indonesian English
Simpan Save
Batal Cancel
Kirim Send
Hapus Delete
Coba lagi Try again
Keluar Sign out

The English copy uses the same casual voice: “you” and “your”, short sentences, and no legal terms in everyday copy.