personal-projects/personal-portfolio
Template
1
1
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

[Sprint 10] feat: Add component IDs and enable contact form fields #92

New Issue
Closed
opened 2026-02-01 18:17:38 +00:00 by lmiranda · 0 comments
lmiranda commented 2026-02-01 18:17:38 +00:00
Owner
Copy Link

Overview

Enable the currently disabled contact form fields and add component IDs required for Dash callback interaction.

Files to Modify

  • portfolio_app/pages/contact.py

Acceptance Criteria

  • All form inputs have unique IDs (contact-name, contact-email, contact-subject, contact-message, contact-submit)
  • All form fields are enabled (disabled=True removed)
  • "Coming Soon" alert is removed
  • Feedback container added for success/error messages (id: contact-feedback)
  • Hidden honeypot field added (id: contact-gotcha) for spam protection
  • Form renders correctly in browser

Technical Notes

  • Follow DMC component ID conventions
  • Add id="contact-feedback" as empty dmc.Stack for feedback placement
  • Honeypot field should be hidden with CSS (position: absolute, left: -9999px)
  • Keep form layout structure unchanged

Labels

type/enhancement scope/frontend priority/medium size/S

## Overview Enable the currently disabled contact form fields and add component IDs required for Dash callback interaction. ## Files to Modify - `portfolio_app/pages/contact.py` ## Acceptance Criteria - [ ] All form inputs have unique IDs (contact-name, contact-email, contact-subject, contact-message, contact-submit) - [ ] All form fields are enabled (disabled=True removed) - [ ] "Coming Soon" alert is removed - [ ] Feedback container added for success/error messages (id: contact-feedback) - [ ] Hidden honeypot field added (id: contact-gotcha) for spam protection - [ ] Form renders correctly in browser ## Technical Notes - Follow DMC component ID conventions - Add `id="contact-feedback"` as empty dmc.Stack for feedback placement - Honeypot field should be hidden with CSS (position: absolute, left: -9999px) - Keep form layout structure unchanged ## Labels `type/enhancement` `scope/frontend` `priority/medium` `size/S`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/personal-portfolio#92
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?