{"action":"opened","issue":{"url":"https://api.github.com/repos/publiclab/plots2/issues/4301","repository_url":"https://api.github.com/repos/publiclab/plots2","labels_url":"https://api.github.com/repos/publiclab/plots2/issues/4301/labels{/name}","comments_url":"https://api.github.com/repos/publiclab/plots2/issues/4301/comments","events_url":"https://api.github.com/repos/publiclab/plots2/issues/4301/events","html_url":"https://github.com/publiclab/plots2/issues/4301","id":391226549,"node_id":"MDU6SXNzdWUzOTEyMjY1NDk=","number":4301,"title":"Planning for holistic improvements","user":{"login":"esylvan","id":3617884,"node_id":"MDQ6VXNlcjM2MTc4ODQ=","avatar_url":"https://avatars1.githubusercontent.com/u/3617884?v=4","gravatar_id":"","url":"https://api.github.com/users/esylvan","html_url":"https://github.com/esylvan","followers_url":"https://api.github.com/users/esylvan/followers","following_url":"https://api.github.com/users/esylvan/following{/other_user}","gists_url":"https://api.github.com/users/esylvan/gists{/gist_id}","starred_url":"https://api.github.com/users/esylvan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/esylvan/subscriptions","organizations_url":"https://api.github.com/users/esylvan/orgs","repos_url":"https://api.github.com/users/esylvan/repos","events_url":"https://api.github.com/users/esylvan/events{/privacy}","received_events_url":"https://api.github.com/users/esylvan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-14T18:55:04Z","updated_at":"2018-12-14T18:55:04Z","closed_at":null,"author_association":"NONE","body":"PROBLEM: Public Lab has many amazing projects that are all available on the PL website. But users, especially new or lightly engaged ones, might be confused by what they can do.\r\n\r\nGOAL: We want people to find it easy to come to the site, find a sub-community they want to engage with, and then know what they can do with the community. Our approach can be guided by two key main takeaways we want people to get from the site:\r\n\r\n- what is Public Lab and what does Public Lab do\r\n- what can I/a given user do with Public Lab\r\n\r\nIn particular we want to provide this clarity for topical and regional communities of practice.\r\n\r\nAPPROACH: Public Lab's user interface would benefit from a holistic review of what could be improved. Here is one potential approach we can discuss. \r\n* create very brief user stories for key user goals on the site. Examples\r\n  * new user who wants to know what happens at Public\r\n  * new user who wants to engage in a particular location or project\r\n  * existing user who wants to to engage in a particular location or project\r\n  *  existing user receives a notification about something they followed and follows a call to action based on it\r\n  *  better examples?\r\n* Based on these stories, develop guidelines for specific sets of pages or interactions, such as what to do with different notifications\r\n* Create issues that define the implementation of these guidelines\r\n* when PL contribute to areas that have been reviewed, ask them to link to/review the stories and link to/follow the guidelines developed.\r\n  *  existing user \r\n      \r\n"}}
{"actor":{"display_login":"esylvan"}}