The Design Model (API Terminology Explained #3)

Last week, I gave an introduction to our product type model. In this blog post, I will talk about our design model.

Understanding the Design Model

In our terminology, a design represents a pixel (png, jpg, gif) or vector image (svg) that a customer or partner can use to put it on a product type. A typical design, e.g. the “I Heart” design from the Spreadshirt marketplace, is illustrated in the picture above. A design has the following characteristics:

  • Core Data: Each design has a name, a description, a size and a price. The price is in this case the commission that the owner of the design earns for each usage.
  • Color Layers: Vector designs consist of one or more color layers. We provide for each color layer, the original color of the uploaded design as well as the color set by the owner as actual default color.
  • Allowed Print Types: For each design, we provide a list of print types, e.g. flock, flex or digital direct print, that can be used to print that design. Vector and pixel images are printed using different print types!
  • Restrictions: We also provide for each design information that restrict the usage of that design. This restrictions are configured by the design owner. The attribute fixedColors tells the user of the design for example, whether colors can be changed or not. Another attribute minimumScale tells the user of the design for example how much he can scale down the design from the original size given with the dimension attribute. Continue reading “The Design Model (API Terminology Explained #3)”