Design assets:
https://www.dropbox.com/sh/a7a0z3z1ib2l2mv/AADwXj76EH54ETfAhhlm3yqqa/v2/01_web?dl=0

Design assets:
https://www.dropbox.com/sh/a7a0z3z1ib2l2mv/AADwXj76EH54ETfAhhlm3yqqa/v2/01_web?dl=0

We need to have a package which can be downloaded and installed on any 6.2 instance (with all deps embeded).

Design assets:
https://www.dropbox.com/sh/a7a0z3z1ib2l2mv/AADwXj76EH54ETfAhhlm3yqqa/v2/01_web?dl=0

We need to have users with avatars and profile info which we could use as articles authors.

All templates should be compatible with Template Editor and moved to the new structure.
Currently needed templates:

• Hero page - dark header, hero image, footer
• Content page - light header, footer

Existing content needs to be updated to use new templates.

commit 315fdac breaks app package install because file at [1] got deleted, but is still referenced in the client lib and the main.js.dir folder is still there. not sure if this is missing cleanup or if the file should not have been deleted.

[1] https://github.com/Adobe-Marketing-Cloud/aem-sample-we-retail/blob/264f9b933680d7a31b65e700e096899bcd7c1858/ui.apps/src/main/content/jcr_root/apps/we-retail/components/content/section-products/clientlibs/js/main.js

/cc @gabrielwalt, @gknob

Let's move all extra clientlibs from clientlib-all to "per template page" clientlibs.

Design assets: https://www.dropbox.com/sh/a7a0z3z1ib2l2mv/AADwXj76EH54ETfAhhlm3yqqa/v2/01_web?dl=0

Top section of the home page (hero image, first title and category teasers) should be targeted for the following segments:

• summer, female, over 30
• summer, female, under 30
• summer, male, over 30
• summer, male, under 30
• winter, female, over 30
• winter, female, under 30
• winter, male, over 30
• winter, male, under 30
• female
• male

Adobe Target should be used as the targeting engine.

Implement basic tracking through DTM.

All occurrences of "geometrixx" and "geometrixx-outdoors" should be replaced with "we-retail". Also package needs to be tested on a clean AEM 6.2 instance without sample content.

Design assets:
https://www.dropbox.com/sh/a7a0z3z1ib2l2mv/AADwXj76EH54ETfAhhlm3yqqa/v2/01_web?dl=0

How should we obtain recommended products

There's no top-level Discover section in We.Retail.

As discussed with @gabrielwalt:

Related to feature parity of ContextHub, we should make sure there's no ClientContext segment in We.Retail, but we use ContextHub based ones.

there is a typo -> "sampe"

Design assets:
https://www.dropbox.com/sh/a7a0z3z1ib2l2mv/AADwXj76EH54ETfAhhlm3yqqa/v2/01_web?dl=0

It seems that it is caused by missing dtm clientlibs

README.md refers to the folders ui.tests and ui.launcher. These should be changed to it.tests and it.launcher, respectively.

AEM ships with the ExampleContentHealthCheck which needs a discriminator to spot we-retail packages as content package. - Those are not suitable for production.

Assets
https://www.dropbox.com/s/dr4fkegjq0dky29/we.retail.assets-1.0.0.zip?dl=0

Catalog
https://www.dropbox.com/s/kx8y7groysscxmy/we.retail.products-catalog-1.7.0.zip?dl=0

We will commit this in a separate GIT that can build this package in the next few days.

Note: Right now - these packages are overwritten paths the we-retail projects currently uses - and they are different from the Geometrixx Outdoors catalog currently used in we-retail.

Design assets:
https://www.dropbox.com/sh/a7a0z3z1ib2l2mv/AADwXj76EH54ETfAhhlm3yqqa/v2/01_web?dl=0

Hi,

I recently committed on the quickstart a modification that requires all the policies to be located under the following pattern:

* <libs/apps/folderUnderConf>
** <settings>
*** <wcm>
**** <policies>
***** <sling:resourceType>
****** <policyName>

Furthermore, policies location is now resolved thanks to relative paths by the Conf Manager. Paths should then be stored on the policy mapping as for example for the wcm responsivegrid:

* <templates>
** <my-template>
*** <initial>
**** <jcr:content>
*** <policies>
**** <jcr:content>
***** <root>
***** cq:policy="wcm/foundation/components/responsivegrid/my-policy"
*** <structure>
* <policies>
** <wcm>
*** <foundation>
**** <components>
***** <responsivegrid>
****** <my-policy>

That said we also have introduced a mechanism to copy the policies referenced by the template type under the policies node of the current template folder. You might want to copy it manually if you have an existing template in order not to loose the cq:authoring capabilities.

Please refer to the following links:

https://wiki.corp.adobe.com/display/cq5/Template+Editor
https://sj1glm754.corp.adobe.com:12001/browse/CQ-71363

And don't hesitate to rich me out if needed,

Regards

AEM or Social login for publish-side users.

As discussed with @gabrielwalt, we need a permission model for We.Retail users & groups.

• Which groups do we need?
• What permissions should they have?
• Which users do we need?

Articles in the Experience section should use Content Fragments.

The featured article should be the text and images of Norway by Jacob and Sofia.

There is a policy referenced in the following file that is not included in the source:

https://github.com/Adobe-Marketing-Cloud/aem-sample-we-retail/blob/master/ui.apps/src/main/content/jcr_root/apps/we-retail/components/structure/page/.content.xml#L3

Can you please add it so that I can have a look at it :D

Product component should support multiple variant axes with multiple images for each variant.

Publish-side search of:

• Products
• Content (e.g. experiences)
• Social Content (from Communities)
• People (from Communities)
• Popular searches

Need to find out whether we are able to use omnisearch (in-product solution) on publish instance.
We need to find out what is the API and how to do it properly.

tbd

Would look better :)

No mobile layout at this moment. Desktop - #10

Other design assets:
https://www.dropbox.com/sh/a7a0z3z1ib2l2mv/AADwXj76EH54ETfAhhlm3yqqa/v2/01_web?dl=0

This won't be in the foundation components (see CQ-61930) so it'll have to be done in custom code throughout, both at the page level and at the image level.

Design assets:
https://www.dropbox.com/sh/a7a0z3z1ib2l2mv/AADwXj76EH54ETfAhhlm3yqqa/v2/01_web?dl=0

Initial compilation of LESS files takes a lot of time so we have to optimize them. Removing unused variables/styles is the first step.

Disclaimer: I am not an Adobe employee. I am member of the reference implementation group working for Netcentric.

I can't build the project anymore. It seems that the required dependency com.adobe.cq.commerce:cq-commerce-core:jar:5.14.84 is not publicly available yet.

The commit where the dependency was introduced: ee4a9d6

Since this is an internal repository I wouldn't classify this as bug. But we would be really glad if we could find a solution for this problem. We are currently working with the latest loads of AEM. The source of the We Retail project already helped us out a few times with features that aren't documented yet. So we would like to continue to build and deploy We Retail.

Any suggestions?

In the template type definition for the html5page the referenced resource type is missing in my local AEM instance:

wcm/foundation/components/pagetypes/html5page

I use AEM 6.2 load18 and the whole wcm/foundation/components/pagetypes node is missing.

As I am not a Adobe developer I don't know if wcm/foundation/components/pagetypes/html5page was removed and the we.retail demo wasn't updated or if the pagetype is just not bundled in the latest loads (yet).