* Note: these are annotated slides aimed at making it easy to read and follow along with what I said during the session. The video will cover demos and the original unannotated deck.
I’ve been thinking a lot recently about the clash between idealism and pragmatism. I’ve been working on the Web for many years, and for much of that time I’ve tried to do things the ‘right’ way; standards-compliant, validated, mobile-first, responsive, accessible, clean, extensible, etc. I’m definitely not claiming that I’ve always succeeded, but the intention …
The Flux Architecture shows one effective way to achieve this. While in a React.js context, the pattern is essentially framework agnostic (and I'm sure that people have been doing this before Facebook).
Instead of a simple event bus, you implement something what Flux calls a Dispatcher.
A dispatcher is pretty much an event bus, but you can (optionally) enforce in what sequence the event is "dispatched" to its listeners.
Progressive enhancement has become a bit of a hot topic recently, most recently with Tom Dale conclusively showing it to be a futile act, but only by misrepresenting what progressive enhancement is and what its benefits are.
The bottom line is that Hypermedia has zero value, especially in the context of M2M (again, I am not talking about the Web’s Architecture when a human is in the loop). I am certain that someone somewhere will find an application (or two) that shows some value, just like any interesting software pattern, beyond that, hypermedia will be a big waste of time for most people, just like the uniform interface, the coupling of identity with access, http caching, verbs vs nouns, human readable documentation… have been thus far.
"When people are talking about web performance, they may talk about different aspects of the subject depending on their role and the task on hand. The real life is rather messy, so we use abstractions that let us get away from details not important for the moment. The same reality may look quite differently depending on how we look at it. Adjusting our view for our specific needs, we probably may highlight four major angles to look at web performance."
We want faster websites, and browsers are helping us get there—searching for patterns, analyzing behaviors, and guessing where users might click next. But we know our sites and users best, and we can use that insight to proactively nudge browsers along. Predictive browsing queues up resources before users even ask for them, creating a faster, more seamless experience. Santiago Valdarrama looks at the benefits and costs of three prebrowsing techniques at our disposal.
In a substantial, well-researched blog article, Drew Crawford lays out all the reasons why he believes mobile web applications are slow today and why he does not expect this dramatically improve in the near feature.
Sharing your scoops to your social media accounts is a must to distribute your curated content. Not only will it drive traffic and leads through your content, but it will help show your expertise with your followers.
How to integrate my topics' content to my website?
Integrating your curated content to your website or blog will allow you to increase your website visitors’ engagement, boost SEO and acquire new visitors. By redirecting your social media traffic to your website, Scoop.it will also help you generate more qualified traffic and leads from your curation work.
Distributing your curated content through a newsletter is a great way to nurture and engage your email subscribers will developing your traffic and visibility.
Creating engaging newsletters with your curated content is really easy.