title: How to best manage versions with API Blueprint format
body: <p>How are people managing multiple API versions with API Blueprint?</p>
  
  <p>It doesn't seem that the format supports version sections within a single file, so I'm left thinking that multiple files with indicators in the filename are the best option.</p>
  
  <p>We want to leverage the tools to create a central mock-server and doc commons, and will need to handle evolving multiple versions of each API.</p>