User Story: SO_15 Extend Boutique Ado models & framework

EPIC: #35

SO_15 As System Owner I want to build on the Boutique Ado framework so as to improve the system and increase user functionality

Assumptions or Pre-Requisites:

Site is constructed by following Boutique Ado frameworks and structures
This user story captures enhancements and deviations from that model
Capture Demonstration of programmer's craft
Note - its a CI PP5 project requirement to have at least 3 new/enhanced models within the delivered app

Acceptance Criteria: (Must be completed before task is moved to 'Done')

[x] Must include at least 3 custom models
[x] Must contribute towards overall usability of the solution

Enhancements

[ ] Model Enhancement1: User Profile Image & Addresses:
Extend BA's custom user profile to include Avatar image, and to display avatar on-screen for logged-in user.
Extend user profile address: rather than just storing a single default address, store multiple addresses for the user (as Inline records within a user profile). Each address has an address type (BILL or SHIP), a single BILL address is permitted per user profile, but multiple shipping addresses (with a user-defined label e.g. HOME, WORK, MUM) allowed.
Extend the user profile template to allow the user to maintain/update the above
Extend the checkout function (for an authenticated user) to retrieve the user's BILL address if it exists & apply it to the order; permit the user to choose between SHIP addresses if exist on profile. Note that the user won't be permitted to update BILL address from the checkout screen but can modify or add SHIP addresses.
Add a permitted discount code to the customer??
[x] Model Enhancement2: Product Catalog and product Maintenance:
Extend the catalog maintenance by adding more categories. In the case of a jeweller the main category is Product Type, then source type (STOCK, MTO make to order, COMMission), promotion type
Add a template under SysAdmin dropdown to maintain categories
Extend the product add/edit functionality by offering a grid format to speed up the add/edit process DONE 14/02/24
Extend the Product model by including Product lead time, with backup default value from Source type catgory #29 DONE 14/02/24
[ ] Model Enhancement4: Non-stock items which can be added at checkout - e.g. giftwrap, engraving, gift card (with message)
[ ] Model Enhancement5: Affinity products???? Identify 'bought-together' product and add to affinity table. Allow this table to be auto built based on historical orders, then edited by administrator
[ ] Model Enhancement6: Promotions - promotion codes - discount code that can be entered on order. If it matches a discount code on the item then apply it to the item, otherwise if it matches a discount code on the customer then apply it to the entire order (excluding any items already discounted)
[x] Model Enhancement7: Feedback/ Contact Us form - and provision of a sysadmin grid to review the feedbacks provided and determine any furter action needed
[x] Model Enhancement8: Reviews/Ratings - provide a mechanism for registered users to give star ratings and commentary on a particular product. Reviews are moderated by sysadmin before being applied. (Does the user need to have purchased the product first?) - ONGOING 13/02.24 #57
[ ] Model Enhancement9: Newsletter - allow user to signup for newsletter and provide for sending out.
[x] Model Enhancement10: Order - added status, promised ship date, and added order maintenance to update the status

DESIGN ENHANCEMENTS:

[x] Modularise elements of the main and sub-heading navbars and search menus. To avoid duplication of code for responsive variations.
[x] Meaningful order number (and order line numbers). A 'starting' order number is assigned in the settings e.g. 24001. When an order is generated, the stored Orders are checked, and incremented to determine next order#. if no Orders on file then value from settings is used. Save incremented value in settings. Order line#s are stored in increments of 10, e.g. 10, 20 etc.
[x] Approach to sizing - In the Jewellery trade, sizing typically applies to rigns which can have a finger size of N? to S. For any item with has_sizing type a separate line is created in the basket per item, and the sizing field is enabled. A size category is offered if item category = ring, this is offered at the basket stage, and is stored as per Boutique Ado as an item tuple
[x] Approach to personalisation - products are defined as can_engrave (boolean); this will never apply with rings (as the jeweller doesnt have the setup to do ring engraving), the user can add personalisation/ engraving text when adding to the asket.
[x] Product, Catalog Maintenance - apply grid front-end for Product
[x] Order maintenance - a functional console to take orders through the despatch and delivery stages.

DeeMcCart / CI_PP5_Jeweller

User Story: SO_15 Extend Boutique Ado models & framework #50

Assumptions or Pre-Requisites:

Acceptance Criteria: (Must be completed before task is moved to 'Done')

Enhancements