{"action":"created","issue":{"url":"https://api.github.com/repos/canonical-webteam/practices/issues/70","repository_url":"https://api.github.com/repos/canonical-webteam/practices","labels_url":"https://api.github.com/repos/canonical-webteam/practices/issues/70/labels{/name}","comments_url":"https://api.github.com/repos/canonical-webteam/practices/issues/70/comments","events_url":"https://api.github.com/repos/canonical-webteam/practices/issues/70/events","html_url":"https://github.com/canonical-webteam/practices/pull/70","id":337320738,"node_id":"MDExOlB1bGxSZXF1ZXN0MTk4NTQxNzQ2","number":70,"title":"Remove progressive enhanacement general rule","user":{"login":"squidsoup","id":130286,"node_id":"MDQ6VXNlcjEzMDI4Ng==","avatar_url":"https://avatars0.githubusercontent.com/u/130286?v=4","gravatar_id":"","url":"https://api.github.com/users/squidsoup","html_url":"https://github.com/squidsoup","followers_url":"https://api.github.com/users/squidsoup/followers","following_url":"https://api.github.com/users/squidsoup/following{/other_user}","gists_url":"https://api.github.com/users/squidsoup/gists{/gist_id}","starred_url":"https://api.github.com/users/squidsoup/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/squidsoup/subscriptions","organizations_url":"https://api.github.com/users/squidsoup/orgs","repos_url":"https://api.github.com/users/squidsoup/repos","events_url":"https://api.github.com/users/squidsoup/events{/privacy}","received_events_url":"https://api.github.com/users/squidsoup/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-01T20:46:22Z","updated_at":"2018-07-02T14:07:36Z","closed_at":null,"author_association":"NONE","pull_request":{"url":"https://api.github.com/repos/canonical-webteam/practices/pulls/70","html_url":"https://github.com/canonical-webteam/practices/pull/70","diff_url":"https://github.com/canonical-webteam/practices/pull/70.diff","patch_url":"https://github.com/canonical-webteam/practices/pull/70.patch"},"body":"While progressive enhancement is possible in an isomorphic react app, this is technically impossible for us given that we are unable to use node serverside. Even without the node restriction, universal react apps are significantly more complex, for potentially little gain.  I don't think this rule is pertinent now."},"comment":{"url":"https://api.github.com/repos/canonical-webteam/practices/issues/comments/401817148","html_url":"https://github.com/canonical-webteam/practices/pull/70#issuecomment-401817148","issue_url":"https://api.github.com/repos/canonical-webteam/practices/issues/70","id":401817148,"node_id":"MDEyOklzc3VlQ29tbWVudDQwMTgxNzE0OA==","user":{"login":"barrymcgee","id":505570,"node_id":"MDQ6VXNlcjUwNTU3MA==","avatar_url":"https://avatars0.githubusercontent.com/u/505570?v=4","gravatar_id":"","url":"https://api.github.com/users/barrymcgee","html_url":"https://github.com/barrymcgee","followers_url":"https://api.github.com/users/barrymcgee/followers","following_url":"https://api.github.com/users/barrymcgee/following{/other_user}","gists_url":"https://api.github.com/users/barrymcgee/gists{/gist_id}","starred_url":"https://api.github.com/users/barrymcgee/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/barrymcgee/subscriptions","organizations_url":"https://api.github.com/users/barrymcgee/orgs","repos_url":"https://api.github.com/users/barrymcgee/repos","events_url":"https://api.github.com/users/barrymcgee/events{/privacy}","received_events_url":"https://api.github.com/users/barrymcgee/received_events","type":"User","site_admin":false},"created_at":"2018-07-02T14:07:36Z","updated_at":"2018-07-02T14:07:36Z","author_association":"CONTRIBUTOR","body":"I do not think this should be removed, but it should be amended with the caveat you outline above, i.e. - while the core functionality of certain Javascript-driven product apps is difficult to replicate without server-side rendering, we aspire to develop using the principles of progressive enhancement wherever possible.\r\n\r\nAlso, even where the above is true - `<noscript>` etc should be utilised to ensure no user gets a white, blank because JS excecution has failed.\r\n\r\nAfterall, our biggest site (ubuntu.com) and the majority, if not all, of our marketing sites are initially rendered server-side where this principle should continue to absolutely apply. "}}
{"actor":{"display_login":"barrymcgee"}}