Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Application Form Content, Styling, and Basic Validation #559

Closed
8 tasks done
stmcpeters opened this issue Jan 31, 2025 · 1 comment · Fixed by #538
Closed
8 tasks done

Application Form Content, Styling, and Basic Validation #559

stmcpeters opened this issue Jan 31, 2025 · 1 comment · Fixed by #538

Comments

@stmcpeters
Copy link
Collaborator

stmcpeters commented Jan 31, 2025

Description

This issue involves implementing all the necessary questions and fields for the Techtonica application form. The form should include fields with proper input types, basic validation, and clear labels for accessibility. Additionally, it should be styled according to Techtonica's branding guidelines.

Why This Is Important

  • Ensures users provide data in the right format, improving data quality and reducing errors.
  • Styling the form according to Techtonica's branding ensures a consistent user experience and aligns with the organization’s visual identity.
  • Clear labels and validation messages make the form more accessible to all users, including those with disabilities.

Acceptance Criteria

  • Create a new route and view for the application form (if not already existent)
  • Before entering the form, there should be some descriptive information about the following headings, this can have placeholder text (to be updated by program staff later) for now but the descriptive headings are provided here: The Program, Pre-Req and Form Deadline, etc
  • Implement all necessary questions and fields.
  • Apply basic styling that follows Techtonica's branding guidelines.
  • Ensure fields use appropriate input types (e.g., <input type="email">, <input type="tel">).
  • Add basic validation (required fields, correct email/phone format, inline error messages).
  • Ensure form elements have clear labels for accessibility.
  • Submit a PR that merges into the mvp branch, not develop

Related Tickets

@daaimah123
Copy link
Collaborator

Whoever takes this issue will need to leave comments on #505 for any style decisions that are not yet documented

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants