search

SAP / spartacus

Spartacus is a lean, Angular-based JavaScript storefront for SAP Commerce Cloud that communicates exclusively through the Commerce REST API.
Apache License 2.0
738 stars 383 forks source link

Spike: define the CMS strategy for Account Profile #1144

Closed plabadie closed 5 years ago

plabadie commented 5 years ago

Setup the CMS page and component structure required for the account profile feature.

Page and component design:

-Which page and component structure do we use -How much do we reuse as-is from the electronics store and what do we need to modify/add

Use the new page layout logic:

We should probably use the new generic page layout mechanism, see address book example GH-1081 GH-1080

JSP Compoenent refactoring:

-Do we use the new JSP component equivalent? -Potentially depends on GH-986.

Restricted access:

Only a signed in user can access account profile pages. -Do we use cms restrictions? See GH-1173 -Or do we use application specific mechanism?

plabadie commented 5 years ago

Page design: We will reuse current electronics store pages if possible. We create new ones otherwise

Layout: We reuse the account page template. There are examples in the code bas on how to add a new page in spa

JSP Components: We will use the new CMSFlexComponent

We will use the current mechanism to restrict the page access and team framed will provide a generic way to enforce this,

Ticket produced: https://github.com/SAP/cloud-commerce-spartacus-storefront/labels/z%2Faccountprefs