Styleguide’s data files have two purposes:

  • Hydrate the template files’ placeholders with mock data. This feature removes the need to connect to a backend to inject data into the template.
  • Provide names used by the parent project’s View generator for creating Java interfaces. For example, if you integrate Styleguide into a Brightspot project, at build time Brightspot creates Java interfaces with method names based on the data file’s keys. For details about this process, see How the View Generator Creates View Classes.