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

YJN: Pre-workshop stakeholder meeting notes #134

Open
Rabia2219 opened this issue Feb 23, 2023 · 5 comments
Open

YJN: Pre-workshop stakeholder meeting notes #134

Rabia2219 opened this issue Feb 23, 2023 · 5 comments

Comments

@Rabia2219
Copy link
Member

Overview

REPLACE THIS TEXT -Text here that clearly states the purpose of this issue in 2 sentences or less.

Action Items

REPLACE THIS TEXT -If this is the beginning of the task this is most likely something to be researched and documented.

REPLACE THIS TEXT -If the issue has already been researched, and the course of action is clear, this will describe the steps. However, if the steps can be divided into tasks for more than one person, we recommend dividing it up into separate issues, or assigning it as a pair programming task.

Resources/Instructions

REPLACE THIS TEXT -If there is a website which has documentation that helps with this issue provide the link(s) here.

@Rabia2219
Copy link
Member Author

Rabia2219 commented Feb 23, 2023

For stakeholders regarding the Info Architecture

  1. Has the advisory board changed?
  2. Draft Terms of Service
  3. Miro map: revise to match the pages so it can be made interactive
    4. Mariana's title and LinkedIn
  4. Help Edin with LinkedIn
  5. We will explain why some pages are hidden
  6. Inform that the font in the legal content documents will be changed to Open Sans
  7. Ask about naming: Knowledge is Power vs Know Your Rights

@Rabia2219

This comment was marked as outdated.

@Rabia2219
Copy link
Member Author

Rabia2219 commented Feb 27, 2023

Documents needed for pre-workshop meeting

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Feb 27, 2023

Review

General Updates and Next steps

  • The Figma: Font, Style and Status Guide Style
  • All the content from the current website has been copied to the architecture site
    • The volunteers and intern images have been completed
    • We don't have control of the forms and access to the responses (they are not owned by any of the project emails). We have reached out to Olivia and Chali and they also don't have access. We are doing one last check with you to see if you have access. If not, we will need to recreate the forms.

Content and Navigation Updates

In order to validate the site navigation architecture, we reviewed representative samples of content

Resources section

  • Folder reviewed: Resources
  • Determinations made during the review:
    • The content in the resources section will need to be made into separate pages on the site instead of putting it into a dropdown on one page, so that we can create headings and subheadings to make the information more accessible.
  • Demo: Resources | Resources for LGBTQ+ Youth

Help Me>Police Encounters

  • Folder reviewed: Help Me>Police Encounters
  • Determinations made during the review:
    • The content will need to be broken down further, so that it will be easier to digest for site visitors
  • Demo:
    • Alternate version of YJN: Website Navigation Plan Current | Proposed
    • Alternate versions of the documents (moving some content around) in the 1.0 folder
    • Alternate page layout on the Google sites website navigation Current | Proposed

Pre workshop prep

KIP

Review mostly finished pages from site
Review proposed new content navigation structure/breakdown
  • Go through 1.0 Police Encounters section ALT documents and YJN: Website Navigation Plan Current | Proposed to verify that the new structure is:
    • Legally correct
    • The information is in a chronological order, from the perspective of the end user
    • Free of duplicative information (meaning, everything is in its proper place and easy to find, for the user, so it does not need to be repeated in other headings or subheading body text)
  • Estimate this review will take 4–8 hours

HfLA YJN team

  • Add KIP team as editors to the site
  • Create documentation about all the editing Formatting topics we will be covering
    • Adding Heading and Subheading sections from the template (so that formatting stays consistent)
    • Adding citations
    • Site breakage
      • Minor: Referencing the Figma file if the formatting is accidentally changed
      • Catastrophic: Backup and how to roll back the site if it gets broken
  • Create instruction videos that can be referred to later
    • citations
  • Adding documentation to the YJN WIKI Stakeholder page

Workshop

To be scheduled after

Post workshop KIP

Review legal content

  • Review all the content in sections 1 (Help Me) and section 2 (Resources) and break down content into hierarchical structure as defined by Police Encounters and LGBTQ+ pages. Updating the YJN: Website Navigation Plan
  • For example, Sections 4 & 5 needs some clarification (possibly additional documents or reworking of the ordering of the documentation) including:
    • an overview of the order that things happen in for the user
    • a list of hearings/court appearances with their definitions
    • indication in each hearing/court appearance description document with which of the judge's options are available at this stage
  • We estimate the section reviews and edits will take KIP team 8-12 hours per section + an overall review of 8 hours once all content is done. (80 hours)

Create a Terms & Conditions

See example:

Post Workshop HfLA YJN team

  • once the YJN: Website Navigation Plan has been updated, and It's July, the HfLA team can review the content & navigation plan to see if info architecture is ready for the site.
  • We estimate the section reviews and edits will take HfLA team 8–12 hours per section + an overall review of 8 hours once all content is done. (80 hours). We will send each section for review as we finish it, unless we think there is some information to rearrange between sections (e.g., section 4 and 5 might take longer and require meetings HfLA to understand the material well enough to make navigation architecture decisions.)

@Rabia2219 Rabia2219 self-assigned this Feb 27, 2023
@Rabia2219
Copy link
Member Author

2023-02-28 Agenda

Notes

  • content copied as is except on slide 4
  • left notes where needed
  • all links on slide as well as in speaker notes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New Issue Approval
Development

No branches or pull requests

2 participants