Product -> Layer settings (FE, like PLP or PDP, HP, etc.)
Product -> Configuration
Basket ->
Basket -> Promo Rules (Marketing)
Basket -> Layer settings (FE, like PLP or PDP, HP, etc.)
Basket -> Configuration
Basket -> Synchronization ->!!! No clue, but I assume might become handy to have smth out of the box to support other platforms if they are represented as SPA (Single Page Application) and don't want to waste time and money on complex development.
Basket - Api (for future)
Order ->
Order -> Layer settings (FE, like fast checkout (PLP, HP) and checkout etc.)
Order -> Configuration
Order -> Checkout
Order -> Shipping
Order -> Payment
Order -> Return & Refund
Order -> Invoice
Order -> Api (for future)
Order -> Production
Customer ->
Regular Customer settings, they all the same + (GDPR)
Customer -> Login
Customer -> Portfolio/Album
Customer -> Business settings
Content ->
Content -> Pages
Content -> Blocks
Content -> Configuration
Content-> Layer settings (FE, like PLP, HP, etc.)
Topic like SEO, Meta, Analytics will be reviewed when main flow for BE (code) will be ready (Elastic, Varnish, Redis, NestJS)
DanielsHaitovs
commented
1 year ago
The idea of EAV is to be a tree (reminds me something of category tree) where will be stored setting according to tree level.
Realize simple table relationship for now. With option to store ->
Attribute id, Attribute code, Attribute (group-level) settings, Attribute value
For now, the idea is to hold and render them in elastic.
means admin should have in menu buttons such as ->
Category ->
Product ->
Basket ->
Order ->
Customer ->
Content ->
Topic like SEO, Meta, Analytics will be reviewed when main flow for BE (code) will be ready (Elastic, Varnish, Redis, NestJS)