Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -22,11 +22,11 @@
22	22
23	23	== (% style="font-size: 20.0px;letter-spacing: -0.008em;" %) 1. Manage your assets in the Partner Area(%%) ==
24	24
25		-There are no endpoints available that allow uploading or changing the content of your shop. Use the partner area to upload designs and manage your assortment. Note that not only the content you upload in the Partner Area, but also the shop settings affect the output of the [[sellable resources>>doc:API.Sellables||style="letter-spacing: 0.025em;" shape="rect"]]. For example, enabling model images affects the image URLs returned by the API.
	25	+There are no endpoints available that allow uploading or changing the content of your shop. Use the partner area to upload designs and manage your assortment. Note that not only the content you upload in the Partner Area, but also the shop settings affect the output of the [[sellable resources>>doc:API.Spreadshirt Public Shop API Documentation.API REST Resources.Sellables.WebHome||style="letter-spacing: 0.025em;" shape="rect"]]. For example, enabling model images affects the image URLs returned by the API.
26	26
27	27	== (% style="font-size: 20.0px;letter-spacing: -0.008em;" %) 2. Build a scheduled sellable data import(%%) ==
28	28
29		-To use the full potential of a custom shop implementation it is recommended to import the entries of the [[sellable list>>doc:Sellables]] resource into your own database every 24 hours. The example integration uses the Public Shop API as a direct data source for simplicity, but that is not the recommended approach. The import based solution yields better performance and allows you to introduce all kinds of filtering and sorting options (which are NOT built into the Public Shop API). Once you have imported this data you can build a frontend that meets your requirements.
	29	+To use the full potential of a custom shop implementation it is recommended to import the entries of the [[sellable list>>doc:API.Spreadshirt Public Shop API Documentation.API REST Resources.Sellables.WebHome]] resource into your own database every 24 hours. The example integration uses the Public Shop API as a direct data source for simplicity, but that is not the recommended approach. The import based solution yields better performance and allows you to introduce all kinds of filtering and sorting options (which are NOT built into the Public Shop API). Once you have imported this data you can build a frontend that meets your requirements.
30	30
31	31	== 3. Build the list page ==
32	32
...	...	@@ -34,7 +34,7 @@
34	34
35	35	== 4. Build the detail page ==
36	36
37		-When assembling a detail page on your server, request the [[sellable detail resource>>doc:Sellables]] allowing you to render all available images as well as sizes. If you want to display things like name and description of the product type, appearance names and colors, etc., the [[doc:API.Spreadshirt Public Shop API Documentation.API REST Resources.ProductType.WebHome]] resource is useful. The response of that resource is slow and rarely changes, so it is a good candidate for caching. In a somewhat generic implementation, the [[doc:Price Formatting Guide]] might be helpful.
	37	+When assembling a detail page on your server, request the [[sellable detail resource>>doc:API.Spreadshirt Public Shop API Documentation.API REST Resources.Sellables.WebHome]] allowing you to render all available images as well as sizes. If you want to display things like name and description of the product type, appearance names and colors, etc., the [[doc:API.Spreadshirt Public Shop API Documentation.API REST Resources.ProductType.WebHome]] resource is useful. The response of that resource is slow and rarely changes, so it is a good candidate for caching. In a somewhat generic implementation, the [[doc:Price Formatting Guide]] might be helpful.
38	38
39	39	== 5. Build a basket ==
40	40