the production-ready merge candidate#34
Open
monicataccoli-byte wants to merge 2 commits into
Open
Conversation
✅ Deploy Preview for workshopnavigator ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR focuses on stabilising and consolidating the Workshop Navigator frontend into a single backend-connected facilitator workflow.
During the MVP/demo phase, several prototype and UI-exploration pages were created to test layout directions and facilitator workflows. Some of these included hardcoded/demo data structures used primarily for presentation and design experimentation.
After reviewing the current application flow, the decision was made to continue building from EventDetailsPage.jsx because it is already integrated with the live backend/API architecture, including:
• real event fetching
• facilitator dashboard integration
• live event codes
• attendee join flow
• QR code generation
• poll/event API integration
The visual/layout concepts from FacilitatorEventDetailsPage.jsx remain valuable and will continue to inform styling improvements, however the working backend-connected architecture from EventDetailsPage.jsx provides a safer long-term foundation for completing the application as a fully functional portfolio project.
This approach also helps:
• reduce merge conflicts
• avoid duplication of facilitator workflows
• remove stale/demo-only logic
• minimise conflicting prototype architectures
• preserve currently working event creation and join flows
Additional stale/demo PRs containing overlapping styling changes and dependency lockfile changes (package-lock.json) are recommended for closure to avoid unnecessary conflicts during final stabilisation.