Open SamHyler opened 2 years ago
NO MEETING TODAY - ALL SICK OR OUT OF OFFICE
[Research Updates]
[SOT]
[Figjam]
[October 13, 2023] Agenda and Notes Attendees • Yasmin • Cheryl • Curtis • Sam
Notetaker ☐ Yasmin ☐ Curtis ☐ Sam
Accountability and Support Check • [ ]
Recurring items: • [ ]
New Meeting Items ☐ New member intros ☐ Content Team Overview + Flow ☐ Alexis & Cheryl off boarding ?
FYI • [ ] Notes from Meeting Task Items: • [ ] Items for next week's agenda ☐ SOT discussion ☐ Emma sync with Sam and Curtis
[General Notes ]
[New SOT System (Copy Doc)]
[V&T Updates]
Cheryl has joined the team! UX writing role is now closed to incoming Hack LA volunteers.
Takeaways from EOY Reflection: Sam is very happy with how the team has grown thus far. Curtis has enjoyed the collaboration on the team so far.
Figma Walkthrough: Sam walked Thea through the main EA Figma page
Team updates: Yaz is basically done with Credits Page issue. Waiting on more icons/cards to edit. Yaz will work on SOT and alt-text during holiday break.
V&T exercise: Team finished up a couple of brainstorming sections for V&T. Will work on finishing up entirely after the holiday
Happy Holidays !
[x] Welcome Back !
[x] Who can take notes?
[x] Content Leadership Transition
[x] Monday's Dev / Design / Product @ 4:30 pm PST meeting is now Monday's PM meeting @ 4:00 pm PST
[x] V & T exercise will resume next meeting
[ ] Alternate Text + Best Practices
Who's worked with alternate text ?
Informative vs. Decretive
[ ] Content + Design Collaboration Process
Sam is in the midst of PHD and will be offloading work to Curtis and Emma. Put questions in Slack and Curtis and Emma will answer ASAP.
On Mondays, the PM and Dev meetings will be made into one meeting (will be at 4:30 pm PST).
Every meeting going forward, we will take on a portion of our voice and tone exercise. We can also tackle this async as well.
Emma and Yaz will continue working on Alt-text and decide whether we need to do an app-wide audit. Will probably need to create a separate issue for accessibility.
Content and Design Collab Process
Trying to come up with a better way to collab with design. Thinking about treating each issue like a sprint.
Yaz will share Source of Truth next meeting.
Voice and Tone Exercises: Will resume next week
-[ ] Resume V & T Exercise
[x] Who can take notes?
[x] Team Stand Up & Issue Updates (15-30 minutes) (Assigning ourselves to Issues and Github Procedure) (#965 & #231)
[ ] Yas SOT Walkthrough : https://docs.google.com/spreadsheets/d/1c_Kv_T1yER-hHckNl5zkGrlGaLNCE_AeZE6Jjmn8IK0/edit#gid=2080474274
[ ] FAQ Page Language Complex ? : https://expungeassist.org/faq
[ ] New Road Map Layout : https://www.figma.com/file/SRsM0BvWhtmFwpg23bKTLB/EA-Collaboration-(Design%2FContent)?type=whiteboard&node-id=3738-9686&t=el6jCjDPGaTWrlve-0
[x] Figma at 75% Capacity (Brainstorm Solutions for Friday Content/Design Sync)
[ ] V & T exercise
[ ] Google Reminder is still showing old Zoom Meeting Link (Curtis working on solution)
[ ] Discuss SOT in Content/Design Sync or All Teams Meeting
[ ] Current Issues : Alt Text , About Page (FAQ + Header Page)
[ ] Do we need Alt Text because our pages are Illustration Heavy) .
Helpful screenreader link: (https://getbootstrap.com/docs/4.0/utilities/screenreaders/)
Ask Dev about Altext and Accessibility need , requirements, functionality , and legality
Possibility utilize other Hack for LA Product Teams to gage Alt Text and Accessibility (Food Oasis)
[ ] SOT Walkthrough w/. Yas
A point of reference for Design and Engineers
Page level : All the content thats on the page , not pop up content
Currently includes all of the pages that are on the master page
Message Page (content thats generated from users action, headers)
Create Documentation around adding to SOT , also add to "How to Write An Issue" Github issue *
[ ] Possible new Design + Content Syn meeting time and structure Content writer feed back : In terms of collaboration , teams would like to talk to each other outside of main meeting times (Possible thread)
What’s helpful in a meeting space ?
[ ] Who can take notes?
[ ] Team Stand Up & Issue Updates (15-30 minutes)
[ ] V & T Exercise - Team exercises moved to next week 2/29 , Async Updates
[ ] Friday Content + Design Sync Meeting Feedback : https://hackforla.slack.com/archives/C06KMFDM9PZ/p1708572979168029
[x] Who can take notes?
[x] New Member Intro
[x] New Issue Writing Doc : https://github.com/hackforla/expunge-assist/wiki/How-to-Create-Issues
[x] Gather Missing Info for Content Guidelines : https://github.com/hackforla/expunge-assist/issues/1170
[ ] Sam & Emma Standup (Who Are We Copy, LP Ideas, About Me & FAQ Ideas)
[ ] V & T Exercise
[x] Who can take notes?
[x] Stand Ups (15-30 minutes) (Any one need any help?)
[ ] Enhance Friday Sync Plan
New How to Create Issues Doc & Process : https://github.com/hackforla/expunge-assist/wiki/How-to-Create-Issues
Submitting Ask Bonnie form for Privacy Policy template (Curtis)
[ ] Who can take notes?
[ ] Stand Ups (15-30 minutes) (Any one need any help?)
[ ] Sync Proposal : https://docs.google.com/document/d/1Nb6dHrHbdZ4ZSSAWSUKSTFie30awP1xTTQNA6iFUpRE/edit?pli=1
[ ] V & T Additions
New How to Create Issues Doc & Process : https://github.com/hackforla/expunge-assist/wiki/How-to-Create-Issues
Sync Proposal : https://docs.google.com/document/d/1Nb6dHrHbdZ4ZSSAWSUKSTFie30awP1xTTQNA6iFUpRE/edit?pli=1
Content stand up for Claudia's work on the 404 error page - team provided feedback. Needs more collaboration with dev to understand why the 404 error page would occur.
Content stand up for Cheryl's "About Us" page redesign - team provided feedback. Need more understanding on what "partner with us" actually means.
Worked on qualifying the words chosen for the Voice and Tone.
Attendees
Notetaker
Accountability and Support Check
Recurring items: New Meeting Items
FYI New How to Create Issues Doc & Process : https://github.com/hackforla/expunge-assist/wiki/How-to-Create-Issues Sync Proposal : https://docs.google.com/document/d/1Nb6dHrHbdZ4ZSSAWSUKSTFie30awP1xTTQNA6iFUpRE/edit?pli=1
Notes from Meeting
Content Standups:
Claudia- 404 Page- Claudia did some edits and, after some feedback, chose an option for the 404 page copy.
Claudia is going to take on the “Oops!” page issue. Going to merge it with the 404 page issue.
Cheryl- Had some edits and notes from the feedback last week. Emma shared additional notes from Sam.
Yaz- Privacy Policy looks good. Emma will ping Curtis to try to get it in front of Bonnie for their meeting. Should show it off to Dev as well.
Emma- Wants to start working on content guidelines. There will be multiple sections, including research terminology, grammar, trauma informed language, differences between voice and tone, etc.
If we have any ideas on what to add into the content guidelines, feel free to add them in.
Yaz will take on Advice page issue.
Items for Next Week's Agenda
Attendees
Notetaker
Accountability and Support Check
Recurring items: New Meeting Items
FYI New How to Create Issues Doc & Process : https://github.com/hackforla/expunge-assist/wiki/How-to-Create-Issues Sync Proposal : https://docs.google.com/document/d/1Nb6dHrHbdZ4ZSSAWSUKSTFie30awP1xTTQNA6iFUpRE/edit?pli=1
Notes from Meeting Claudia : 404 Page & Oops page
Dev/d Syd Input :
Cheryl : About us Page : Research racialize individual term and inclusive language
Items for Next Week's Agenda
Attendees
Notetaker
Accountability and Support Check
Recurring items: New Meeting Items
FYI New How to Create Issues Doc & Process : https://github.com/hackforla/expunge-assist/wiki/How-to-Create-Issues
Notes from Meeting Goal Date for Stakeholder Prep - Mid June Follow up on Monday about the Privacy Policy Template during PM meeting About page has been moved up to the next milestone and ready for a re-design. Advice and Oops page pending additional information and teaming up with design. To be brought up at the all teams meeting.
Items for Next Week's Agenda
Attendees
Notetaker
Accountability and Support Check
Recurring items: New Meeting Items
FYI New How to Create Issues Doc & Process : https://github.com/hackforla/expunge-assist/wiki/How-to-Create-Issues Research Team Glossary: https://docs.google.com/document/d/1D19tbPqQkFzHYF2GemsZDDdMjbUM6jh6E6ArYWS-WIo/edit#heading=h.n5tb1h4qmf0f
Notes from Meeting
Items for Next Week's Agenda
Attendees
Notetaker
Accountability and Support Check
Recurring items:
New Meeting Items
FYI New How to Create Issues Doc & Process : https://github.com/hackforla/expunge-assist/wiki/How-to-Create-Issues Research Team Glossary: https://docs.google.com/document/d/1D19tbPqQkFzHYF2GemsZDDdMjbUM6jh6E6ArYWS-WIo/edit#heading=h.n5tb1h4qmf0f
Notes from Meeting
Content standups
Claudia: Refinement of error message strategy. Avoiding blaming language such as "You refreshed the page" in favor of "the page refreshed" (appropriate use of passive in this case).
Is "the declaration" the correct terminology (vs. "the declaration letter"? Will be addressed in Sylvia's presentation).
Cheryl: Looked over Sylvia's presentation deck. Awaiting the conclusion of Sylvia's presentation and her suggestions.
General onboarding discussion: Is the request for "proper punctuation" exclusionary and inaccessible? The most important part is making sure there are periods and complete sentences instead of run-on sentences.
Are "profanity" and "slang" too similar? Is "profanity" an accessible word?
"Cussing" is too informal; might go with "swearing." Might be too California-specific.
Tooltips might help with giving in-tool writing advice. Sam will check with Sydney about coding tooltips and auto-capitalization tools.
Should there be a Go Home button? What page do we want the user to return to?
Research on best practices for optimal character counts is just starting; anyone should feel free to contribute.
Content guidelines will be content's main priority for Stakeholder 2.
Items for Next Week's Agenda
Attendees
Notetaker
Accountability and Support Check
Recurring items:
New Meeting Items
FYI New How to Create Issues Doc & Process : https://github.com/hackforla/expunge-assist/wiki/How-to-Create-Issues Understanding Expungement in CA: https://docs.google.com/presentation/d/1MGeAWeTl3C_Eg6rsrmzdzsc_vX2aY3YX-ODdVlDe21o/edit#slide=id.p Maria's survey: https://docs.google.com/forms/d/e/1FAIpQLSfTYCz7-88F1GwuVDSlwf6Ks-kSM9bmUxQnDSUKccQv6NNH7Q/viewform Missing pieces for content guidelines: https://docs.google.com/document/d/13GrI0nrf4JZJVULP8er_pNw0xAEOjvd_F6KjvLoOp1A/edit#heading=h.1tungtdu1hxe
Notes from Meeting
Items for Next Week's Agenda
Attendees
Notetaker
Accountability and Support Check
Recurring items:
New Meeting Items
FYI New How to Create Issues Doc & Process : https://github.com/hackforla/expunge-assist/wiki/How-to-Create-Issues Understanding Expungement in CA: https://docs.google.com/presentation/d/1MGeAWeTl3C_Eg6rsrmzdzsc_vX2aY3YX-ODdVlDe21o/edit#slide=id.p Maria's survey: https://docs.google.com/forms/d/e/1FAIpQLSfTYCz7-88F1GwuVDSlwf6Ks-kSM9bmUxQnDSUKccQv6NNH7Q/viewform Missing pieces for content guidelines: https://docs.google.com/document/d/13GrI0nrf4JZJVULP8er_pNw0xAEOjvd_F6KjvLoOp1A/edit#heading=h.1tungtdu1hxe
Notes from Meeting Notes:
Privacy Policy- Bonnie doesn’t have it yet, but is still working on it.
Facilitating Meetings- Still need some help with facilitating meetings for content
Dev Handoff procedure- Sam has some things to discuss about dev handoff process
Open Sync- For the past couple of weeks, there have been discussions about how the overall process can be improved. Go into the Figjam to voice your opinions.
Content Standups:
Claudia- She is working on her final version. Now is wondering where to send for approval.
Cheryl- Reached out to Sylvia about Github issue. Will try to resolve and try to get the notes out.
Yaz- Christina brought up the idea of placeholder text in the input fields. Putting it there could influence answers.Content agrees that placeholder text may not be beneficial.
Items for Next Week's Agenda
Attendees
Notetaker
Accountability and Support Check
Recurring items:
New Meeting Items
FYI New How to Create Issues Doc & Process : https://github.com/hackforla/expunge-assist/wiki/How-to-Create-Issues Understanding Expungement in CA: https://docs.google.com/presentation/d/1MGeAWeTl3C_Eg6rsrmzdzsc_vX2aY3YX-ODdVlDe21o/edit#slide=id.p Missing pieces for content guidelines: https://docs.google.com/document/d/13GrI0nrf4JZJVULP8er_pNw0xAEOjvd_F6KjvLoOp1A/edit#heading=h.1tungtdu1hxe Keep Updating the SoT: https://docs.google.com/spreadsheets/d/1c_Kv_T1yER-hHckNl5zkGrlGaLNCE_AeZE6Jjmn8IK0/edit?pli=1#gid=368137937
Notes from Meeting
Notes:
Items for Next Week's Agenda
Review assignments for each team member
Emma: Bonnie did her stakeholder review last Friday. Watch the ~ 2-hour video if you can; you can skip the developer section; detailed notes in summary of issue.
Prioritize content guidelines, then start on Bonnie's stakeholder review.
The board migrated to a new version - struggling to understand what it means for us. Bookmark new link and wiki.
Next: finish source of truth
Grammar guidelines beginning
For example: Avoid exclamation points, contractions, and semicolons
Punctuation on bullets: punctuate full sentences.
Sentence length, character count
Which pronouns: you or I?
One idea per sentence; what is the ideal paragraph length? Will the generator automatically space sentences?
]
Review assignments for each team member
Review assignments for each team member
Review assignments for each team member
[ ] Check in: Does Friday All Teams time still work? Check yes or no on the main slack channel
[ ] Next Friday Afternoon is the org meeting with Bonnie - discussing project direction
[ ] Discussed team charter briefly from Maria. Will go over it next Friday at All-teams in more depth
[ ] Style Guide - Cheryl presented https://gist.github.com/cherylcline/c9019d799b531bf3d5ac185410d342e8 Pros: maintained by experts and is comprehensive. Can be a foundation for our work, and we can make deviations where necessary. Neither guide is free, will look for options. AP - we will likely start with AP as it is favored by websites. Is a little outdated and was made for newspapers. Chicago gives more detail but is prefered for book publishing. Next 2 meetings we will dedicate the hour to looking at AP.
[ ] New meeting time is set going forward, will adjust as team needs change.
[ ] Next two meetings dedicated to looking at AP style guide and working on those with our Content Guidelines (CG).
[ ] AP style guide
Review assignments for each team member
Review assignments for each team member
Review assignments for each team member
Review assignments for each team member
Review assignments for each team member
Later/ Strategy work
-Still looking for 1-2 PMs as a PM onboarded but took a short-term contract.
-New writer onboarded, still recruiting 1-2 others.
-Claudia presents new iterations of "the page refreshed" wording.
-Three terms Sam is working on finalizing:
Declaration letter vs letter
Expungement vs record clearance vs ceiling reduction
What do we call people who are seeking expungement?
Review assignments for each team member
Short informal meeting, Sam and Melissa attending. Handled some new member questions and tasks. Assigned Key terms tasks and Hero banner tasks.
Review assignments for each team member
[ ] Note taker?
[ ] Updates from PM/Leads ?
[ ] Recruitment
[ ] Issue status check
[ ] Stand ups?
[ ] FYI https://docs.google.com/spreadsheets/d/1uajit1EJKIKGd6wqQz6XC-GTYTycDo1Ea-fzAiBxCqs/edit? and https://github.com/hackforla/expunge-assist/issues/1461pli=1&gid=0#gid=0
[ ] Issues needing reassignment soon, needs Content to run strategy together with Design: https://github.com/hackforla/expunge-assist/issues/981 and https://github.com/hackforla/expunge-assist/issues/982 have high level discussions attached.
-Team Introductions
Sam
-still looking for a content design lead
-have one more new content designer coming on
-will talk with UXR for some follow up research/input on the three key terms. Want to ensure accessibility for this user base.
-"Bonnie's List" reviewed with team for future reference
-Team Charter all members please read through and speak with Sam if any questions or concerns. Please sign if no questions or concerns.
-Sam is writing a "blurb" to include in the team charter to describe what the content team does. Presented to tam for feedback.
Cheryl
https://github.com/hackforla/expunge-assist/issues/1502
-Following up with design on spacing. Get prototype of copy into Figma for review.
Melissa -presented discrepancies between SOT and Figma -will add pages not in SOT to the spreadsheet -involvement screen under parenting - placeholder currently says "text" in Figma, nothing in spreadsheet - will create a ticket to resolve, to change Figma to match website (0). Add to spreadsheet. -some other action items for me to update the SOT based on Figma -Sam will investigate Credits page and follow up to determine next steps -Melissa to send summary of inconsistent copy to Sam for further review
New Assignments Three Key Terms - Expungement #1629 - assigned to Melissa
Improve the instructions on the Advice page #981 - assigned to Cheryl
Review assignments for each team member
[ ] Note taker?
[ ] Updates from PM/Leads ? - reminder leading meetings
[ ] Recruitment
[ ] Issue status check
[ ] Team charter https://docs.google.com/document/d/1wdqbY_f67lsDrvIEnyupjWNonEXVTQqvjBGZtpV0EVU/edit?tab=t.0#heading=h.a5p3rbm5hzo2
[ ] Stand ups?
[ ] https://github.com/hackforla/expunge-assist/issues/1631. people with criminal records, individuals with eligible criminal convictions, applicants who are writing a letter to a judge
[ ] Hero banners
[ ] https://github.com/hackforla/expunge-assist/issues/231 Bonnie will work on creating a template for this in December, so we will have this issue as Super High Prio in Jan. This is a MUST do in order to launch to partners.
New How to Create Issues Doc & Process
Missing pieces for content guidelines
Keep Updating the SoT at the end of every issue!
Review assignments for each team member
Do you need an issue? Please take a CG issue: https://github.com/hackforla/expunge-assist/issues/1286
[ ] https://github.com/hackforla/expunge-assist/issues/231 Bonnie will work on creating a template for this in December, so we will have this issue as Super High Prio in Jan. This is a MUST do in order to launch to partners.
New How to Create Issues Doc & Process
Missing pieces for content guidelines
Keep Updating the SoT at the end of every issue!
Notes November 14 2024 Expunge Assist
No updates from PMs Recruitment: Still looking for at least one UX writer
Issues:
Content guidelines have been dragging over the year; hope to finish up by the end of the year
Issues 981, 1502 Use overview cards in Design Sandbox > Anita in Figma file
Sam will try to create a Loom demonstrating Design/Dev handoff
Claudia: Will take a content guideline issue
Melissa: Will also take one. Has finished onboarding. Interested in rewriting banner copy with a higher-level value proposition.
Don't close issues until other teams have been pinged.
Sam will present tomorrow at the all-teams meeting on terminology research (declaration and other terms) through plain language and accessibility lenses.
Review assignments for each team member
Do you need an issue? Please take a CG issue: https://github.com/hackforla/expunge-assist/issues/1286
[ ] https://github.com/hackforla/expunge-assist/issues/231 Bonnie will work on creating a template for this in December, so we will have this issue as Super High Prio in Jan. This is a MUST do in order to launch to partners.
New How to Create Issues Doc & Process
Missing pieces for content guidelines
Keep Updating the SoT at the end of every issue!
Overview
This issue tracks the running agenda for the Content team weekly meetings (Tuesdays 11AM PST)
Reply in the comment using this format to create weekly agenda.
Format