style: update miscellaneous step page - #120
Merged
Merged
Conversation
3 tasks
seangaaab
force-pushed
the
style/update-miscellaneous-step-page
branch
from
September 5, 2026 07:00
d9ce96e to
ec12faa
Compare
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
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.
📝 Overview
This PR updates the Miscellaneous Page in the PyCon registration flow to match the PyCon 2026 design specifications. It preserves existing form handling and validation while updating structure, styling, responsiveness, and field exclusions.
Closes #103
🚀 Type of Change
🎨 Visual, Styling & Responsive Validation
Required for all UI/Frontend changes.
text-[#FFF]).🔌 CMS Integration Checklist
Skip this section if no CMS API changes were made.
📸 Visual Evidence (Mandatory)
Important
Visual proof is required to demonstrate the UI changes. Please attach Before/After screenshots or screen recordings (GIFs/Videos) of the implementation, including responsive behaviors (resizing the browser).
You must provide evidence that you ran
npm run buildandnpm run start(ornpx serve) and tested the production build.Drag and drop screenshots/videos here:

Mobile
Tablet

Desktop

Screen.Recording.2026-09-03.170618.mp4
📋 Final Checklist
stageand resolved any conflicts.npm run buildandnpm run start).🧠 Extra Notes / Questions