Create Automated Tag Generator

[ExperimentsInHonesty]

Overview

We need to create an automated tag generator in order to make it easier for people to add tags to increase the adoption of Civic Tech Index.

History

If this issue is in the prioritized backlog we have decided found that it is feasible to create the automated tag generator to integrate with the manual process/tutorial. See history of #181 for more details.

Dependency

Automated Tag Generator feasibility research #181

Action Items

• [x] Product and UI Design
  • [x] Define the workflow and how this fits into the current version of the manual tag generator wizard
  • [ ] Define the messaging (see resources for prior wording we might be able to reuse some of)
  • [x] Define the database requirements
  • [x] UI
  • [x] create lo fi mockups
  • [x] get signoff from product
  • [x] create hi fi mockups
• [x] Product
  • [x] Annotate mockups (can do this on lofi while hi fi's are being created)
  • [x] Create new issues for Front End, Back End / Database
  • [ ] Create Error State UI for unsuccessful submission to Tag Generator and CTAs for error handling for end user

Resources/Instructions

Text from when we were working on the issue originally to be used to make recommendation for implementation once feasibility research is done

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.

Error State V1

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

------ Notes on a possible process flow

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?

[mariastudnicka]

@chalimar Hey Chali, do we have a screen for this? I'm trying to assign an issue for @FarzanaPrianka. I'm wondering if we have this in our flow re: error states?