comment: |
  Wiki markup is fine for basic formatting, but games often need more
  complex logic.  That's where macros come in.  The most basic type of
  macro is a reference.  Say you want to refer to a character by name
  in another sheet.  You can just write {{{<<ExamplePC.name/>>}}},
  and the reference will expand to “<<ExamplePC.name/>>”.  You can use
  this for any prop, so you can even render someone's badge in the
  middle of a sheet if you want to.

  <<ExamplePC.badge/>>

  This form of macro has no content, as indicated by the slash before
  the {{{>>}}}.  Macros can also have content; for example, if you
  want to refer to multiple props of an element, you can do something
  like <<sourceof leaf.example/>> to get “<<leaf.example/>>”
  
  You can also leave the prop implicit, like {{{<<ExamplePC/>>}}}.  By
  default, this shows the element's name prop, e.g. “<<ExamplePC/>>”.  
  (Behavor without an explicit prop specified is controlled by the 
  ‘substitution’ prop; the behavior specified here is defined in
  [[Owner]], which all in-game elements inherit from.)

  Aside from element references, there are built-in macros.  You can
  read more about these at [[MacroDoc]], but we'll talk about one
  common usage here: pronouns and name parsing.  If you've used
  GameTeX for a game where character names and genders aren't set
  until casting, you know the wonders and sanchecking annoyance of
  generic pronouns and name parsing.  Gameki has similar pronoun and
  name parsing functionality, so you can say something like 
  <<sourceof leaf.example2/>> and get “<<leaf.example2/>>”.

  Them's the basics.  To learn about using Subversion to check out
  your Gameki so you can edit it localy as text files, see
  [[SubversionIntro]].  Otherwise, look at the [[BazkiMap]] to see
  what's already here, or hit the [[Sandbox]] to mess around.
example: |
  <<ExamplePC>><<name/>>'s username is ##<<username/>>##<</ExamplePC>>.
example2: |
  <<ExamplePC>><<first/>> loves <<their/>> puppy.<</ExamplePC>>