{"action":"opened","issue":{"url":"https://api.github.com/repos/maban/styleguides/issues/126","labels_url":"https://api.github.com/repos/maban/styleguides/issues/126/labels{/name}","comments_url":"https://api.github.com/repos/maban/styleguides/issues/126/comments","events_url":"https://api.github.com/repos/maban/styleguides/issues/126/events","html_url":"https://github.com/maban/styleguides/issues/126","id":70273275,"number":126,"title":"Update URL on filter","user":{"login":"bradfrost","id":383701,"avatar_url":"https://avatars.githubusercontent.com/u/383701?v=3","gravatar_id":"","url":"https://api.github.com/users/bradfrost","html_url":"https://github.com/bradfrost","followers_url":"https://api.github.com/users/bradfrost/followers","following_url":"https://api.github.com/users/bradfrost/following{/other_user}","gists_url":"https://api.github.com/users/bradfrost/gists{/gist_id}","starred_url":"https://api.github.com/users/bradfrost/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bradfrost/subscriptions","organizations_url":"https://api.github.com/users/bradfrost/orgs","repos_url":"https://api.github.com/users/bradfrost/repos","events_url":"https://api.github.com/users/bradfrost/events{/privacy}","received_events_url":"https://api.github.com/users/bradfrost/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/maban/styleguides/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-23T01:01:44Z","updated_at":"2015-04-23T01:01:44Z","closed_at":null,"body":"It would be great to update the hash in the URL (i.e. `styleguides.io/examples.html#branding`) so that we can link to a particular flavor of style guide. \r\n\r\nWithout looking at the logic, I think this would require having each filter be mutually exclusive. As in, you wouldn't be able to search for branding+code, but I don't see that as being a core use case any way. Being able to filter and see all branding *or* all code style guides would be more of a primary use case."}}