Open
Conversation
added 12 commits
September 2, 2016 16:47
Contributor
Author
|
Moving the template functionality to a separate module. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Feature Overview
A new entity, called wishlist_template, can be used to filter and display a wishlist view. To the customer, we will present a list of one or more "recommended" categories when viewing their wishlist through a template block. Each block will have a configurable taxonomy term view mode dropdown, allowing you to link them using the theming system to any given page you want. If a product is in the wishlist that matches a category, it will appear underneath the category. Each category will have a recommended quantity but will not enforce or require the quantity.
The idea is that you could create a "wishlist kit" or a "shopping list" and provide links and visual feedback on their progress towards filling their list. The block would be able to tell you the total amount in the wishlist. And, of course, it is possible, just like a cart, to checkout with a wishlist. Meaning you can easily help customers build a significant cart up and then checkout with the contents or feel no pressure and save it for later.
Alpha 1 will assume we have only one cart per customer. Obviously this assumption reduces our complexity, but it is not the final goal. The final goal would be to allow the customer to choose a template and a wishlist to compare it against. These could be used as promotions, for example: Consider a blog post that says, "Get ready for winter! 10 kinds of products that will keep your feet toasty and your winter fashion ahead of the curve." And at the end of the blog post there's a link that, when your customer clicks it, creates a "Get ready for winter wishlist" ready with a few selected products and lots of recommended categories based on a template and displays it in the block.
User Stories for Alpha 1
Deadline
This will be a part of the Drupal 8 port as a sub-module and will be released in a week or two as a part of the Alpha 1 for Drupal 8's Commerce Wishlist.