Wireframes for work flow (overview of site and site specific pages)

[ExperimentsInHonesty]

Overview

We need wireframes for developers to build website from

Action items

• [ ] Create some new pages for expanded functionality
  • [ ] Chali
  • [ ] Marissa
  • [ ] Bonnie

Resources

Figma files CTI Site Map / Overview

[ExperimentsInHonesty]

@mw376707 suggested https://react-autosuggest.js.org/ custom render as way to do the autofill

[mw376707]

Example of how chosen tags could be populated on the page.

[mw376707]

Next wireframes:

• Directory page: Chali to design a directory page depicting all the orgs that have contributed to the index
• Refine the flow for searching projects in the database
  • Chali to cross check github repositories and ensure we have the current search page set up for a user to search projects efficiently.

Questions to be answered:

How will a user search for projects? (i.e by keyword) How will they want to filter their search (drop downs) (ideas: affiliation, last updated)

• About page

[chalimar]

[ExperimentsInHonesty]

RE the above image. Projets wont always use the organizes github org, they might have their own independant repository. If f that is the case we can find those by look for who has the topic tag of the org. For instance, Hack for LA has a project called public tree map, and its is located at https://github.com/Public-Tree-Map/public-tree-map.

So wording that should be added is: Open Oakland projects appear in other orgs repositories, see all.

[chalimar]

CTI Site Map / Overview

[chalimar]

Need screen for About / Overview Need screen for About / Searching the Index

[chalimar]

Update: User feedback of Donate to the CTI screen results

[chalimar]

Update: Manual Tag Submission Process

Screenshots of process added and refinement of some UI components (copy to clipboard icon added to generated tags)

[ExperimentsInHonesty]

@chalimar @Jeff-Enriquez will talk directly about the new mobile mockups

[chalimar]

Met with @Jeff-Enriquez and discussed changes based on Sunday's meeting:

Screens need to reflect our new Nav / Site Structure Mobile Nav / collapse & expand interaction Collaborate with @andrepetrop to develop mobile screens

[ExperimentsInHonesty]

@chalimar

1. Progress: continuing mobile, need to update site map
2. Blocks: none
3. Availability: normal
4. ETA: This week

[chalimar]

Updated Site Map of the Civic Tech Index:

[ExperimentsInHonesty]

@chalimar will add screen shots and mobile will be finished next week.

[chalimar]

Updated screenshots for adding projects to a repository from the manual submission.

[chalimar]

Pending Screens:

• [ ] Need to add success/confirmation page for Automated Submission Process
• [ ] Need to make unsuccessful page.

Mobile Screens still in progress:

• [ ] Project results
• [ ] Tag Generator

[arunprakash87]

@ExperimentsInHonesty will write text for success or reject pages in automated process

[ExperimentsInHonesty]

Automated Process not available text: To use the automated process you must have administrative rights on this GitHub repository. However you may still be able to use the manual process (depending on your access rights). If you have no access rights to this repository [needs to be finished. see issue #54 for what I am thinking] . I want to give them some positive action they can take.

Acceptance text: [I think we need to see this process in action so we can decide what questions we might need to answer, or next steps to give them]

Next steps for this is working on #54 and for issue #42 to get further along in development so that we can see what acceptance text might be necessary.

[chalimar]

Error State V1

[chalimar]

Success V1

[arunprakash87]

Error Messages : We were unable to find the repository you typed. Please verify and resubmit.
It looks like you do not have admin rights…

[chalimar]

[arunprakash87]

@chalimar :Just continuing working on tablet screens

[ExperimentsInHonesty]

review workflow to fix clunky screen

[jsachsman]

@chalimar would like to review this on Sunday's meeting 8/30

We will end up creating three processes with multiple screens, one path for owners, one path for admin/maintain, one path for contributors. Thoughts below

(Ready to add your Tags) -> Explanation screen: We've created an automated process to let you add topic tags to your repository but we need to ask a few questions first. If you don't know the answers you can use our (manual process) -> Q1: Are you the owner of this GitHub organization (list the name here)

• Definition of a GitHub organization
• How ownership works Actions: If yes, go to automated screen (incl. description of how process works and button) If no, to next question

Q2: Do you have admin or maintain rights on this GitHub repository (list the name here)

• Definition of different right types
• How rights work Actions: If yes, go to first screen of admin/maintain process If no, to first screen of contributor process

ALSO Need to add 'bookmark return' screen for when people click on a bookmark and get to the CTI - they might not know anything about the CTI, might want to go back to change tags, might want to continue with this process, we don't know

(another idea) Chart with organization of how owner and admin and maintain and contributors relate, click the link for which one you are?

[jsachsman]

@ExperimentsInHonesty will be sketching out the flow for this process in Figma, or possibly in cooperation with @jsachsman

[jsachsman]

This is blocked temporarily by #42

[ExperimentsInHonesty]

Meeting every sunday after cti general meeting and outline function of each feature/button and link.

[celeste-hub]

@ExperimentsInHonesty will go through every issue and hide what is resolved.

[giosce]

Is this issue about annotating the screenshots? If yes, last Sunday we asked Chali to convert the last Tag-Generator annotated screenshots from Google Slides to Figma. https://drive.google.com/file/d/19fDxAb8EhmL9ITwmfdcX8eK_X1U0N2SZ/view?usp=sharing

[ExperimentsInHonesty]

My update is

1. Progress: I finished hiding everything in the issue that was not relevant to us closing the issue and I opened the following issues and put some of the screen shots and text in them:

   • 180 Revise sitemap in figma

   • 181 Automated tag generator feasibility research

   • 182 Create Automated Tag Generator

   • 183 Create feature: Suggest tags based on similar tags used by other projects based on user provided tags

2. Blocks: none
3. Availability: after sunday meetings and fridays by appointment
4. ETA: probably another 4-5 hours of defining where things go and how they operate and then reviwing/discussing each item for database requirements (say 10 hours).

[ExperimentsInHonesty]

@Gio @Olivia-Chiong I came across this issue #54 that is closed and we need to put the decision about this into the wiki, and make sure we annotate the tag generator with the desired behavior.

[ExperimentsInHonesty]

@giosce @emecas on Sunday This issue is going to get cleaned up so that a designer can make a new round of mock ups that will match the new work flow.

[giosce]

I think the issue is the possibility to change the organization later in the process of generating the tags. I understand the goal of having a link/form that include the Organization name. To me, from a user experience point of view, it seems wrong to decide later to change, add or remove the Organization. Note that typically the organization name is part of the project/repo URL.

[ExperimentsInHonesty]

I reopened #54 and assigned @giosce

[giosce]

@ExperimentsInHonesty, I think Figma is completed now, let's have one last review on Sunday?

[Olivia-Chiong]

One more Sunday and we should be finished with this.

[Olivia-Chiong]

Issue closed as workflows for all pages have been completed