311-data
311-data copied to clipboard
Review Wiki and determine if they belong in the Home or Sidebar
Dependency
- [ ] E1796.A2: Propose new format for Home and Sidebar, see #1796
Overview
We need to review every page in our wiki and determine if they belong in the Home and/or Sidebar so that our public resources are prepared for launch
Action Items
- [X] In a comment, list and group all pages by category (using title as criteria)
- [ ] In a comment, list all pages needed in Sidebar
- [ ] In a comment, list all pages needed in Home
- [ ] In a comment, list all pages that belong on neither, and are simply "floating"
- [ ] Populate the Sidebar and Home with respective places within the markdown provided in R1.02
Resources (Replaces links when E1796.A2 is ready)
- E1796.A2 Resources 1.01 (todo) high-level structure of Home and Sidebar 1.02 (todo) markdown of Home and Sidebar
WIP: Deliverable 1
All pages, grouped by category
Sidebar
- [ ] Home
- [ ] Join Us
- [ ] Deliverables
- [ ] Prototype Proposals
- [ ] Resources
- [ ] Resources Home
- [ ] Other 311 Tools
- [ ] Visualization Exploration
Interview Notes
- [ ] 20200305 UX Interview w Thomas D
- [ ] 20200414 NC Workshop Meeting Minutes
- [ ] 20200810 UX Interview (Elida Mendez)
- [ ] 2023 Data Server Not Functioning PostMortem
- [ ] March 2020 311 MVP Alpha UX Interview Notes
Guides
- [ ] Creating an Issue Template
- [ ] How to Communicate with the Team
- [ ] How to Create Issues
- [ ] How to Join the Engineering Team
- [ ] How to Read and Interpret Labels
- [ ] How to Write a UX Research Issue
- [ ] How to Write an Issue for a Data Scientist
- [ ] How to Write an Issue for a UI UX Designer
- [ ] How to Write an Issue for an Engineer
- [ ] How to Write Issues for Product Managers
- [ ] Introduction to Our Product
- [ ] Introduction to Our Users
Teams
- [ ] Joining the 311 Team
- [ ] Joining the Data Science Team
- [ ] Joining the Product Management Team
- [ ] Joining the UI UX Research Team
- [ ] Joining the UI UX Team at 311 Data
- [ ] Onboarding New Team Members
- [ ] Positions We Need
Unsorted
- [ ] August 2019 Agenda
- [ ] Data Science Recruiting
- [ ] Deliverables
- [ ] Diff Dashboard
- [ ] Existing Tools
- [ ] Initiative ROI
- [ ] July 2019 Agenda
- [ ] RequestStatus
- [ ] September 2019 Agenda
- [ ] Software Development Engineer Test
- [ ] Storing Data in the Repository for a "Frontend Only" Web App
- [ ] Team
- [ ] Team Photos
- [ ] Training for User Interviews
- [ ] UI UX (Product) Designer 311 Data, Hack For LA
- [ ] Visualization Exploration
Structure of the Wiki HOME: >
Join Us, Intro to Our Product, Intro to our Users, Team, Positions We Need, Joining the 311 Team, Joining Product Team, Joining Data Science, Joining UI/UX Research, Joining UI UX Team at 311 Data (Design team? - reformat), How to Join the Engineering team (Joining the Dev team?)
SIDE BAR: the rest I believe can go in the sidebar.
This ticket is ready to be picked up, reviewed with @cottonchristopher 👍
Home Page:
Home Page Intro - No link, Image of the 311-data (Logo)
- Project Definition (No link, Info below)
The 311 Data project seeks to empower local Neighborhood Councils to improve the ideation and analysis of their initiatives using the wealth of publicly available 311 data. We partnered with the Los Angeles Department of Neighborhood Empowerment and LA Neighborhood Councils to co-create and iterate analysis and tools (see 311-Data.org) to provide neighborhoods with actionable information at the local level through real time visualizations and comparison tools.
-
Introduction to Our Product (Product Overview)
-
When and where do we meet (No Link- info below)
Product Planning: 1st Wednesday each month - 7:00 PM (PST) - Team Leads and PMs General Team Meeting: Wednesday - 7:00 PM (PST) - All Members Product Team Meeting: Thursdays - 7:00 PM (PST) - Product Managers, Leads (per request) Dev Team Meeting: Saturdays - 10:00 AM (PST) - Developers, Dev Leads
Sidebar
Home Page Info and links
Join the 311-data Team
Meet the team:
When and where do we meet? Product Planning: 1st Wednesday each month - 7:00 PM (PST) - Team Leads and PMs General Team Meeting: Wednesday - 7:00 PM (PST) - All Members Product Team Meeting: Thursdays - 7:00 PM (PST) - Product Managers, Leads (per request) Dev Team Meeting: Saturdays - 10:00 AM (PST) - Developers, Dev Leads
- Positions We Need
- Onboarding New Team Members
- Joining the 311 Team
- Joining the Data Science Team
- Joining the Product Management Team
- Joining the UI UX Research Team
- Joining the UI UX Team at 311 Data
Guides
Writing Specific team Issues
- How to Write a UX Research Issue
- How to Write an Issue for a Data Scientist
- How to Write an Issue for a UI UX Designer
- How to Write an Issue for an Engineer
- How to Write Issues for Product Managers
Team Specifics
Resources
- Resources Home
- Other 311 Tools
- Deliverables
- Storing Data in the Repository for a "Frontend Only" Web App
- Agendas: link to agendas could go here. We only have July Aug Sept for 2019?
Interviews
Floating: Not sure where they go bc I didn't see any information on them that I could understand
@cottonchristopher - those last 3 interview docs as well as the NC workshop meeting minutes will be moved out of the wiki as a result of existing research ops tickets. Feel free to ignore them.
I would ask however that we get the top level research page listed once we've had a chance to create it.
Here's the ticket with details: https://github.com/hackforla/311-data/issues/1958
Thank you for that information @jberzowska Will definitely make space for "top level research page". Thank you for the heads-up.
Update: 3/19/2025 I have the layout completed in a work doc. I wanted to make sure i understood the layout/format of R1.02 markdown. before transferring to a comment below. Unsure if I am referencing the correct R1.02
Beginning to assemble the Wiki page this is the start of a rough draft. Will resume after the mandatory hiatus. Thank you @ryanfchase for label updates.
Home Page: 311- Data
Project Definition The 311 Data project seeks to empower local Neighborhood Councils to improve the ideation and analysis of their initiatives using the wealth of publicly available 311 data. We partnered with the Los Angeles Department of Neighborhood Empowerment and LA Neighborhood Councils to co-create and iterate analysis and tools (see 311-Data.org) to provide neighborhoods with actionable information at the local level through real time visualizations and comparison tools.
Introduction to Our Product (Change Ticketing Requests to Service Requests) Welcome to our digital product, designed to empower Neighborhood Council members in Los Angeles with data-driven insights into their community. Our platform visualizes ticketing requests and provides analysis that can help each council tackle big issues affecting the 40,000 people they represent. By leveraging data, our product aims to promote transparency, accountability, and informed decision-making at the local level.
At our digital product, we believe that access to information is critical for effective governance. That's why we've created a platform that provides Neighborhood Council members in Los Angeles with a comprehensive view of ticketing requests in their area. By analyzing this data, our product can help Council members identify patterns and trends, prioritize issues, and allocate resources more effectively. Our ultimate goal is to facilitate community-driven solutions to the challenges facing LA neighborhoods.
Our digital product is a powerful tool for Neighborhood Council members in Los Angeles who are committed to making a difference in their communities. With our platform, council members can gain a deeper understanding of the ticketing requests in their area, identify areas of concern, and work together to address the underlying issues. By providing data-driven insights, our product can help council members make informed decisions that benefit the 40,000 people they serve. Join us in our mission to create a more transparent, accountable, and responsive local government.
Learn More about our Product https://github.com/hackforla/311-data/wiki/Introduction-to-Our-Product - https://github.com/hackforla/311-data/wiki/Introduction-to-Our-Users
Joining the 311 Team -Meet the team:
- https://github.com/hackforla/311-data/wiki/Team
- https://github.com/hackforla/311-data/wiki/Team-Photos -https://github.com/hackforla/311-data/wiki/How-to-Communicate-with-the-Team
When and where do we meet? Product Planning: 1st Wednesday each month - 7:00 PM (PST) - Team Leads and PMs General Team Meeting: Wednesday - 7:00 PM (PST) - All Members Product Team Meeting: Thursdays - 7:00 PM (PST) - Product Managers, Leads (per request) Dev Team Meeting: Saturdays - 10:00 AM (PST) - Developers, Dev Leads
- https://github.com/hackforla/311-data/wiki/Onboarding-New-Team-Members o Recruiting: o https://github.com/hackforla/311-data/wiki/Data-Science-Recruiting
- https://github.com/hackforla/311-data/wiki/Joining-the-Data-Science-Team
- https://github.com/hackforla/311-data/wiki/Joining-the-Product-Management-Team
- https://github.com/hackforla/311-data/wiki/Joining-the-UI-UX-Research-Team o https://github.com/hackforla/311-data/wiki/Training-for-User-Interviews
- https://github.com/hackforla/311-data/wiki/Joining-the-UI-UX-Team-at-311-Data (Name change: Joining the UI-UX Team)
- https://github.com/hackforla/311-data/wiki/How-to-Join-the-Engineering-Team o https://github.com/hackforla/311-data/wiki/Software-Development-Engineer-Test
- https://github.com/hackforla/311-data/wiki/Positions-We-Need
SideBar Guides https://github.com/hackforla/311-data/wiki/Creating-an-Issue-Template https://github.com/hackforla/311-data/wiki/How-to-Create-Issues https://github.com/hackforla/311-data/wiki/How-to-Read-and-Interpret-Labels
https://github.com/hackforla/311-data/wiki/How-to-Write-a-UX-Research-Issue https://github.com/hackforla/311-data/wiki/How-to-Write-an-Issue-for-a-Data-Scientist https://github.com/hackforla/311-data/wiki/How-to-Write-an-Issue-for-a-UI-UX-Designer https://github.com/hackforla/311-data/wiki/How-to-Write-an-Issue-for-an-Engineer https://github.com/hackforla/311-data/wiki/How-to-Write-Issues-for-Product-Managers
Team specifics https://github.com/hackforla/311-data/wiki/UI-UX-(Product)-Designer---311-Data,-Hack-For-LA https://github.com/hackforla/311-data/wiki/Data-Science-Recruiting https://github.com/hackforla/311-data/wiki/Training-for-User-Interviews
Resources: https://github.com/hackforla/311-data/wiki/Resources-Home https://github.com/hackforla/311-data/wiki/Existing-Tools ( same as Other tools) https://github.com/hackforla/311-data/wiki/Deliverables (same as Diff DashBoards) https://github.com/hackforla/311-data/wiki/Storing-Data-in-the-Repository-for-a-%22Frontend-Only%22-Web-App Agendas by Month are we going to upload agendas for all months- July August Sept only
(Title) Home Page:
311- Data
311 Data logo
Project Definition
The 311 Data project seeks to empower local Neighborhood Councils to improve the ideation and analysis of their initiatives using the wealth of publicly available 311 data. We partnered with the Los Angeles Department of Neighborhood Empowerment and LA Neighborhood Councils to co-create and iterate analysis and tools (see 311-Data.org) to provide neighborhoods with actionable information at the local level through real time visualizations and comparison tools.
Learn More about our Product
https://github.com/hackforla/311-data/wiki/Introduction-to-Our-Product - (title) Introduction to our Product (Change Ticketing Requests to Service Requests) #Introduction to Our Product https://github.com/hackforla/311-data/wiki/Introduction-to-Our-Users (title) Introduction to Our User #Introduction to Our Users
Learn more about our Project
• 311-Data Figma • 311-Data Sytem Architecture
Join Us:
OnBoarding
o Role Specific Onboarding Developer UI/UX Design Team UI/UX Research Team Data Scientist Product Manager
How To Guides
- How the Hack for LA Kanban Board Works
- How to: Navigate Github
- How to: Format/Write an issue
Issues by Role
- role: product management
- role: frontend
- role: UI/UX Design
- role: UI/UX Research
- ready for prioritization
Project Leadership Guides
• Recruiting: How to Recruit • Onboarding New Members • Creating New Issue Templates -Project Board Management (For PMs)
- Check for missing labels Feature Size Role Milestone no project
Project Resources and Repositories
This is the Homepage, Just wanted to make sure that it looked ok and that I was able to make a few changes as I did. @ryanfchase
@cottonchristopher thank you very much for this -- I've updated the Action Items to reflect the diff between your latest comment and the current Wiki Home
I started off by making some of these edits, but I think I'll need your help to complete this work. I've checked off the action items that I've completed (and I added the date), I'll leave the rest for you (or just lmk if you need help).
Moving this back to Prioritized Backlog for you to pick up.
-
[ ] Possible Section for PM section Product Management Board Management (Links to new pages (that need to be created) or to current pages
- Product Board Review: (which section we review first, second, before meetings)
- Ticket Review: Formatting: "Need to , so that", Dependency check, blocker check, Label appropriateness by board section.
- Weekly Audit: Label Check
-
[ ] Should we remove the "Recruiting" section since "How to Recruit" is under "How to Guides", and it only has Bullet points of team names, Or are we adding more to it? If we do keep it should we move above "Onboarding" section
Just need one last review with product Team to close this ticket and clear the release.