User Story: Code Refactoring, Followup on Issues Spreadshet

EPIC:

As a role I can capability so that received benefit As a role I want to action to achieve desired outcome

Assumptions or Pre-Requisites:

Code in near-ready; this really represents a pre-validation stage where issues are resolved at a programming level before subjecting to user testing. Because of time constraints there will be a bit of an overlap with user testing but let's take it as it comes

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

[ ] Must have most of the items on the issues spreadsheet closed off.
[x] Would expect to have (most of) the items on the Kanban board covered, closed off or marked for future development.

Key Tasks

[x] Issue log spreadheet No17 horiznntal scroll bar shrink-to-fit=no
[x] Header - Issues relating to responsiveness and screen displays (mostly covered 21/02/24 with header size reduction & better navigation across different screen sizes)
[x] Footer - Issues relating to responsiveness and screen displays
[ ] Incomplete functionality (half-developed which needs finishing/ closing out)

Before changing task status to 'Review' or 'Done' please provide comment (and screenprints if appropriate) as documentary evidence of task completion

Review at time of project submission - a lot done but still considerable work needed to make the app properly viable.
The user signup, order-payment flows, engraving/personalisation, sizing, email communication working. Product admin console and order admin console working well. Highest-priority issues which remain at time of submission:

Responsiveness was 'broken' just before submission by applying a HTML validation fix which impacts the navbar for all pages
feedback form not sending via emailjs;
reviews created are submitted for moderation without pulling through the review score;
issues with firefox display on android phone (not seen with chrome on android phone);
tracker # cannot be entered on order admin console, must be entered on Django backend

Deadline reached & necessary to submit, however as this relates to a real-life implementation it is likely that I will take a branch from this project and correct the errors above, and use assessment feedback to address any other prioritised issues. This issue closed 03/03/24 - submission date

DeeMcCart / CI_PP5_Jeweller