{"action":"reopened","issue":{"url":"https://api.github.com/repos/freenode/web-7.0/issues/135","repository_url":"https://api.github.com/repos/freenode/web-7.0","labels_url":"https://api.github.com/repos/freenode/web-7.0/issues/135/labels{/name}","comments_url":"https://api.github.com/repos/freenode/web-7.0/issues/135/comments","events_url":"https://api.github.com/repos/freenode/web-7.0/issues/135/events","html_url":"https://github.com/freenode/web-7.0/issues/135","id":143017327,"number":135,"title":"UX: Lack of anchors for linking","user":{"login":"Fuchs","id":5671757,"avatar_url":"https://avatars0.githubusercontent.com/u/5671757?v=4","gravatar_id":"","url":"https://api.github.com/users/Fuchs","html_url":"https://github.com/Fuchs","followers_url":"https://api.github.com/users/Fuchs/followers","following_url":"https://api.github.com/users/Fuchs/following{/other_user}","gists_url":"https://api.github.com/users/Fuchs/gists{/gist_id}","starred_url":"https://api.github.com/users/Fuchs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Fuchs/subscriptions","organizations_url":"https://api.github.com/users/Fuchs/orgs","repos_url":"https://api.github.com/users/Fuchs/repos","events_url":"https://api.github.com/users/Fuchs/events{/privacy}","received_events_url":"https://api.github.com/users/Fuchs/received_events","type":"User","site_admin":false},"labels":[{"id":347026791,"url":"https://api.github.com/repos/freenode/web-7.0/labels/UX","name":"UX","color":"00cc00","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":19,"created_at":"2016-03-23T16:51:59Z","updated_at":"2018-05-17T06:40:32Z","closed_at":null,"author_association":"MEMBER","body":"As discussed on IRC, if multiple pieces of information  (e.g. registering a nick, identifying to it and nick expiration) are kept on the same page, for the sake of linking to it  (either from project documentation, IRC or whatever else) it would be nice to have anchors. \n\nA different approach would be having separate pages for that kind of information, from an UX point of view I highly discourage that as some information depends on other information or, based on context, can be part of a workflow.\n"}}
{"actor":{"display_login":"svbeon"}}