Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Needs an explanation of default business rules/data structures #5

Closed
Redmega opened this issue Dec 2, 2016 · 1 comment
Closed

Comments

@Redmega
Copy link

Redmega commented Dec 2, 2016

For example, the difference between a Collection and a Category. Would it be like, Category is "Apparel" and collection is "Spring"? Is collection a member of category, or are they independent? etc.

@andrecrt
Copy link
Member

andrecrt commented Dec 5, 2016

The storefront is powered by the Atlas API and its only business rule/data structure for grouping products is "Collections".

It's up to the storefront consuming the API to create any additional logic. In this case, the logic of "Categories" and "Collections" (this time around in the sense of "Spring", "Summer", etc).

The way this logic is embedded in the API/Database is through the property tags of the Collections resource. If you browse the Live API you can see that there are API Collections with the tag category and the tag collection. This is where the storefront looks for to see if the API Collection is a Category or a Collection.

Hope this makes sense :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants