-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Content for Contact form #1211
Comments
curious where this issue lies. Are we still doing it? @anitadesigns @jyehllow @vanessaavviles |
As of right now, we had removed any buttons/links for folks to contact us. I believe we also removed the placeholder email we displayed on the footer and the FAQ page. We had removed them since Bonnie suggested we create a Contact Form, which later I got more clarification on even before having an option for folks to Contact Us, we need to develop a process for checking and responding to emails. I say we should talk about this in the next PM/Lead meeting and whether we would like to continue with a Contact form or revert to displaying our EA email @sydneywalcoff @SamHyler @emmathrash @jyehllow @mariaweissman @sylvia-nam @vanessaavviles |
Content and Design discussed, this will be Design led and Content will do a check after. |
@SamHyler @TechWriterMelissa following up on this issue. @eruan8888 last updated #1210 stating that Yaz would take a look at the Contact Form copy. Since this was right before the break, has there been any changes on who from Content would work with Ellie on this? |
I haven't heard of any yet, lets see tomorrow! |
Updated milestone: currently there is no way to contact EA on the website, this is a must before stakeholder review 2.0 and thus the milestone stands. |
Dependency
Overview
In collaboration with a UX designer, create content for a "Contact Us" page that includes a Contact form. Discuss and brainstorm with a UX Designer on the information the contact form should include and format of the page.
Action Items
dependency
labelready for design lead
labelnew Issues
column on project boardResources/ Notes
The text was updated successfully, but these errors were encountered: