Document

• Interface
  • Changelog
• Inline commands
  • data-chrome-file
  • data-chrome-options
  • data-chrome-metadata
• Attributes
• Data Sources
  • Interface
  • Inline “json”
  • Remote file “uri”
  • Local file “local”
  • External source “export”
  • View Engine
  • Event callbacks
  • Changelog
• Plugins
  • Interface
  • Built-In
  • Breakdown
  • Settings
• Appending source
  • Build Options
• Miscellaneous
  • Merge conflicts
  • Image dimensions
  • Element content
  • Manifest
  • Changelog
• Watch
  • Using JSON config
  • Using copyTo options
  • Using JWT authentication
  • data-chrome-watch
  • Build Options
• Broadcast
  • Interface
  • Example usage
• Finalize
• Settings
  • Changelog
  • References

Note

JSON (yaml) is the preferred way to configure commands due to the limitiations of storing data inline using the data-chrome- dataset namespace. Any assets inside the configuration file will override any settings either inline or from JavaScript.