Skip to content

Instantly share code, notes, and snippets.

@triblondon

triblondon/README.md

Last active August 29, 2015 14:13
Download ZIP

Revisions

  1. triblondon revised this gist Jan 23, 2015. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,6 +1,6 @@
    #Early draft of Edge conf 5

    **This was a discussion of the schedule for Edge 5, which is now finalised. See [the website](https://edgeconf.com/2015-london) for details**.
    **This was a discussion of the schedule for Edge 5, which is now finalised, and the information below is out of date. See [the website](https://edgeconf.com/2015-london) for current details**.



  2. triblondon revised this gist Jan 23, 2015. 1 changed file with 4 additions and 1 deletion.
    5 changes: 4 additions & 1 deletion README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,6 +1,9 @@
    #Early draft of Edge conf 5

    See [the website](https://edgeconf.com) for details of what Edge is and has been in past editions. This document describes our plan for Edge 5, which will be in London in around the beginning of July 2015. Details to be announced shortly!
    **This was a discussion of the schedule for Edge 5, which is now finalised. See [the website](https://edgeconf.com/2015-london) for details**.




    ##Format

  3. triblondon revised this gist Jan 22, 2015. 1 changed file with 2 additions and 1 deletion.
    3 changes: 2 additions & 1 deletion README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -54,4 +54,5 @@ There'll be a breakout on each of the panel topics, but we also have capacity to
    - Extensible web manifesto: is it really working any better than before?
    - Service worker patterns and best practices
    - 'Installing' web apps
    - Data driven performance: Everyone seems to be selling a RUM product these days. Graphs everywhere. NavigationTiming and ResourceTiming are becoming more important, lots of sites are monitoring and optimising their load times, doing things like optimising above-the-fold first render time, rather than more traditional metrics like the load event. And the [Nav Error Logging](https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationErrorLogging/Overview.html) and Beacon APIs are imminent to make instrumentation even easier, so it's worth discussing how these worlds intersect: what is worth monitoring, what's the performance impact, how are new standards helping, what additional work could be done to help (eg aggregators like segment.io).
    - Data driven performance: Everyone seems to be selling a RUM product these days. Graphs everywhere. NavigationTiming and ResourceTiming are becoming more important, lots of sites are monitoring and optimising their load times, doing things like optimising above-the-fold first render time, rather than more traditional metrics like the load event. And the [Nav Error Logging](https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationErrorLogging/Overview.html) and Beacon APIs are imminent to make instrumentation even easier, so it's worth discussing how these worlds intersect: what is worth monitoring, what's the performance impact, how are new standards helping, what additional work could be done to help (eg aggregators like segment.io).
    - CSS and the DOM: the forgotten technologies
  4. triblondon revised this gist Jan 20, 2015. 1 changed file with 3 additions and 2 deletions.
    5 changes: 3 additions & 2 deletions README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -32,7 +32,7 @@ Current top picks from panel topic suggestions:

    * **Components and modules:** Upgrade paths to web components. Is React in competition with WC and why? How can web components share styles and common code efficiently? Is web components a viable solution to a module system for CSS?

    * **Data driven performance:** Everyone seems to be selling a RUM product these days. Graphs everywhere. NavigationTiming and ResourceTiming are becoming more important, lots of sites are monitoring and optimising their load times, doing things like optimising above-the-fold first render time, rather than more traditional metrics like the load event. And the [Nav Error Logging](https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationErrorLogging/Overview.html) and Beacon APIs are imminent to make instrumentation even easier, so it's worth discussing how these worlds intersect: what is worth monitoring, what's the performance impact, how are new standards helping, what additional work could be done to help (eg aggregators like segment.io).
    * **Progressive enhancement:** ES6's syntax incompatibility with ES5 makes it hard to roll out easily. Transpilers help today but what about when some browsers support all the syntax? What about ES7's syntax incompatibilies with ES6? With such a long tail of web tech development, is there a progressive enhancement 'baseline' below which everything breaks and we don't care anymore?

    ##Breakout sessions

    @@ -53,4 +53,5 @@ There'll be a breakout on each of the panel topics, but we also have capacity to
    - Front end development workflows
    - Extensible web manifesto: is it really working any better than before?
    - Service worker patterns and best practices
    - 'Installing' web apps
    - 'Installing' web apps
    - Data driven performance: Everyone seems to be selling a RUM product these days. Graphs everywhere. NavigationTiming and ResourceTiming are becoming more important, lots of sites are monitoring and optimising their load times, doing things like optimising above-the-fold first render time, rather than more traditional metrics like the load event. And the [Nav Error Logging](https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationErrorLogging/Overview.html) and Beacon APIs are imminent to make instrumentation even easier, so it's worth discussing how these worlds intersect: what is worth monitoring, what's the performance impact, how are new standards helping, what additional work could be done to help (eg aggregators like segment.io).
  5. triblondon revised this gist Jan 19, 2015. 1 changed file with 7 additions and 4 deletions.
    11 changes: 7 additions & 4 deletions README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -26,13 +26,13 @@ Edge 5 will feature a single track of 4 sequential panel discussions on topics o

    Current top picks from panel topic suggestions:

    * **Security:** HTTP2 and ServiceWorker both HTTPS only, the announcement of the new letsencypt.org cert authority, the recent Sony leak and standards efforts to unify private browsing mode and access to device APIs. Also post Charlie Hebdo the efforts of the UK gov to ban encryption. What's a reasonable expectation of privacy and how can technology help validate it?
    * **Security:** HTTP2 and ServiceWorker both HTTPS only, campaigns for TLS only, the announcement of the new letsencypt.org cert authority, the recent Sony leak and standards efforts to unify private browsing mode and access to device APIs. Also post Charlie Hebdo the efforts of the UK gov to ban encryption. What's a reasonable expectation of privacy and how can technology help validate it?

    * **Front end data:** Client side data - indexeddb, caches API, Blob storage, all gaining ground, and applications increasingly do more complex things with data in the browser. Also: sync - websockets, fetch, serviceworker, notifications. Let's explore use case and patterns for managing complex data storage, search, indexing and sync in the browser.

    * **Components and modules:** Upgrade paths to web components. Is React in competition with WC and why? How can web components share styles and common code efficiently? Is web components a viable solution to a module system for CSS?

    * **Data driven performance:** Everyone seems to be selling a RUM product these days. Graphs everywhere. NavigationTiming and ResourceTiming are becoming more important, lots of sites are monitoring and optimising their load times, doing things like optimising above-the-fold first render time, rather than more traditional metrics like the load event. And the Beacon API is imminent to make instrumentation even easier, so it's worth discussing how these worlds intersect: what is worth monitoring, what's the performance impact, how are new standards helping, what additional work could be done to help (eg aggregators like segment.io).
    * **Data driven performance:** Everyone seems to be selling a RUM product these days. Graphs everywhere. NavigationTiming and ResourceTiming are becoming more important, lots of sites are monitoring and optimising their load times, doing things like optimising above-the-fold first render time, rather than more traditional metrics like the load event. And the [Nav Error Logging](https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationErrorLogging/Overview.html) and Beacon APIs are imminent to make instrumentation even easier, so it's worth discussing how these worlds intersect: what is worth monitoring, what's the performance impact, how are new standards helping, what additional work could be done to help (eg aggregators like segment.io).

    ##Breakout sessions

    @@ -45,9 +45,12 @@ There'll be a breakout on each of the panel topics, but we also have capacity to
    - Animation
    - Semantics: No-one actually cares how semantic the URL is?
    - WebRTC
    - The New JavaScript. ES6/ES7/fetch. Path to adoption, tooling.
    - The New JavaScript. ES6/ES7/fetch/promises. Path to adoption, tooling, patterns and best practices
    - Responsive images
    - Responsive design / element queries: What next for RWD? How to make existing practices easier, new things to respond to (screen width is dumb, respond to target typographic measure?)
    - [Constraints](http://t.co/jikbF61vj1) (layout and motion)
    - [Navigation transitions](https://docs.google.com/a/ft.com/document/d/1B1kxg6oaiDalf0f-141DMY3abNFzCQUbouiB0wO3cmU/edit)
    - Front end development workflows
    - Front end development workflows
    - Extensible web manifesto: is it really working any better than before?
    - Service worker patterns and best practices
    - 'Installing' web apps
  6. triblondon revised this gist Jan 15, 2015. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -6,6 +6,7 @@ See [the website](https://edgeconf.com) for details of what Edge is and has been

    Edge 5 will feature a single track of 4 sequential panel discussions on topics of universal importance and topicality to the web community, followed by lunch and then 12 breakout sessions across 4 tracks, in which face to face discussions of specific current and future web topics can be had in boardroom style with groups of up to 50.

    ```
    0945 Intro
    1000 Panel session 1 (45 mins)
    1050 Panel session 2 (45 mins)
    @@ -19,6 +20,7 @@ Edge 5 will feature a single track of 4 sequential panel discussions on topics o
    1800 Closing keynote (20 mins)
    1820 Thank yous and charity info
    1830 Dinner and party
    ```

    ## Panel sessions

  7. triblondon revised this gist Jan 15, 2015. 1 changed file with 2 additions and 1 deletion.
    3 changes: 2 additions & 1 deletion README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -47,4 +47,5 @@ There'll be a breakout on each of the panel topics, but we also have capacity to
    - Responsive images
    - Responsive design / element queries: What next for RWD? How to make existing practices easier, new things to respond to (screen width is dumb, respond to target typographic measure?)
    - [Constraints](http://t.co/jikbF61vj1) (layout and motion)
    - [Navigation transitions](https://docs.google.com/a/ft.com/document/d/1B1kxg6oaiDalf0f-141DMY3abNFzCQUbouiB0wO3cmU/edit)
    - [Navigation transitions](https://docs.google.com/a/ft.com/document/d/1B1kxg6oaiDalf0f-141DMY3abNFzCQUbouiB0wO3cmU/edit)
    - Front end development workflows
  8. triblondon revised this gist Jan 15, 2015. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion README.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,4 +1,4 @@
    #Edge conf
    #Early draft of Edge conf 5

    See [the website](https://edgeconf.com) for details of what Edge is and has been in past editions. This document describes our plan for Edge 5, which will be in London in around the beginning of July 2015. Details to be announced shortly!

  9. triblondon renamed this gist Jan 15, 2015. 1 changed file with 0 additions and 0 deletions.
    0 gistfile1.txt → README.md
    View file
    File renamed without changes.
  10. triblondon created this gist Jan 15, 2015.
    50 changes: 50 additions & 0 deletions gistfile1.txt
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,50 @@
    #Edge conf

    See [the website](https://edgeconf.com) for details of what Edge is and has been in past editions. This document describes our plan for Edge 5, which will be in London in around the beginning of July 2015. Details to be announced shortly!

    ##Format

    Edge 5 will feature a single track of 4 sequential panel discussions on topics of universal importance and topicality to the web community, followed by lunch and then 12 breakout sessions across 4 tracks, in which face to face discussions of specific current and future web topics can be had in boardroom style with groups of up to 50.

    0945 Intro
    1000 Panel session 1 (45 mins)
    1050 Panel session 2 (45 mins)
    1135 Break
    1200 Panel session 3 (45 mins)
    1250 Panel session 4 (45 mins)
    1335 Lunch
    1500 Breakout sessions 1, 2, 3, 4 (4 x 60 mins)
    1600 Breakout sessions 5, 6, 7, 8 (4 x 60 mins)
    1700 Breakout sessions 9, 10, 11, 12 (4 x 60 mins)
    1800 Closing keynote (20 mins)
    1820 Thank yous and charity info
    1830 Dinner and party

    ## Panel sessions

    Current top picks from panel topic suggestions:

    * **Security:** HTTP2 and ServiceWorker both HTTPS only, the announcement of the new letsencypt.org cert authority, the recent Sony leak and standards efforts to unify private browsing mode and access to device APIs. Also post Charlie Hebdo the efforts of the UK gov to ban encryption. What's a reasonable expectation of privacy and how can technology help validate it?

    * **Front end data:** Client side data - indexeddb, caches API, Blob storage, all gaining ground, and applications increasingly do more complex things with data in the browser. Also: sync - websockets, fetch, serviceworker, notifications. Let's explore use case and patterns for managing complex data storage, search, indexing and sync in the browser.

    * **Components and modules:** Upgrade paths to web components. Is React in competition with WC and why? How can web components share styles and common code efficiently? Is web components a viable solution to a module system for CSS?

    * **Data driven performance:** Everyone seems to be selling a RUM product these days. Graphs everywhere. NavigationTiming and ResourceTiming are becoming more important, lots of sites are monitoring and optimising their load times, doing things like optimising above-the-fold first render time, rather than more traditional metrics like the load event. And the Beacon API is imminent to make instrumentation even easier, so it's worth discussing how these worlds intersect: what is worth monitoring, what's the performance impact, how are new standards helping, what additional work could be done to help (eg aggregators like segment.io).

    ##Breakout sessions

    There'll be a breakout on each of the panel topics, but we also have capacity to run six more, specialised breakouts on niche topics, since there would be a total of 12 breakout sessions. Suggestions so far include:

    - Automation: The web platform seems to have more automation tooling than virtually any other. Is that a good thing? Is it solving the wrong problem? Is it overcomplication? It is making it easier to put up with messy solutions?
    - Capturing data: UX of form design, new data capture elements, if selects are bad news for UX how can we make making good forms easier?
    - Payments: HTTP 402, W3C web payments initiative
    - Testing
    - Animation
    - Semantics: No-one actually cares how semantic the URL is?
    - WebRTC
    - The New JavaScript. ES6/ES7/fetch. Path to adoption, tooling.
    - Responsive images
    - Responsive design / element queries: What next for RWD? How to make existing practices easier, new things to respond to (screen width is dumb, respond to target typographic measure?)
    - [Constraints](http://t.co/jikbF61vj1) (layout and motion)
    - [Navigation transitions](https://docs.google.com/a/ft.com/document/d/1B1kxg6oaiDalf0f-141DMY3abNFzCQUbouiB0wO3cmU/edit)