Content Plan

Plans

Create a new back-end for collection, edits and static pages.

• Isolate the current front end

• Switch to a new content layer

Create service boundary for Collection and Product Detail Pages

• Wrap all Collection and Product code into presenters
• Ajaxify user-specific information (moodboard, shopping cart)

Finish Landing Page Engine

• Get ElasticSearch queries under test
• Remove dependency on PG for all content rendering.
• Profit.

Content Engine

• All Collection, Edit & Static pages are a Page model, mapped to a path and an (optional elasticsearch product query)
• Products stay more-or-less as they are for now

Pages

• path
• title
• meta-description
• canonical
• heading
• sub-heading
• description
• template (initially a static path, an edit, or a collection)
• parent page
• child pages

Pages should be:

• Translatable
• Indexable
• Cacheable
• Should (ideally) not hit postgres

An edit has a slideshow of images and no product filter A collection has a banner and a product filter

Static pages just map to a static template

Products should be 'featurable' or 'orderable' in some way.