When you have out-of-band processing in a web app, how do you let users know
that the status of a task has changed? Depending on your front-end client,
there are a few different approaches you might take.
Google Analytics is great for gathering data on who uses your web
application, but becomes worthless if spam sessions start infesting your
data. Here's how we've tried to combat the problem for oddbird.net.
Transmitting objects between web processes and worker processes is a
requirement of many modern web apps. Given that the safest way to do so is to
use a serialization format that only includes primitive data types, how can
we send custom objects around?
Living Style Guide documentation on the web
is a difficult problem,
gaining a lot of attention in the last few years.
Let's take an in-depth look
at one way to store patterns directly in Sass,
and generate documentation automatically.
Code documentation is ideally written as close to the actual code
as possible, but compiled into a comprehensive set of documentation
that includes code from all languages in use. Here's how we intend
to do that.
We want the convenience of a client-side single-page application using our
MV* frameworkof choice, but don't want to sacrifice the SEO and UX
benefits of rendering the initial markup on the server. And while we're not
tech stack. Here's our attempt to have the best of both worlds, all the while
keeping duplication of logic or code between the front-end and back-end
worlds to a minimum.
It was a pleasure speaking at
CSSConf 2016 in Boston!
Here are some of my notes from the event –
coverig everything from
creativity and the Bauhaus movement
to SVG 2 internals,
CSS grid layouts,
and custom properties
(e.g. CSS-native variables).
I included links to slides and video
SQLAlchemy defaults to implicitly opening a new transaction on your first
database query. If you prefer to start your transactions explicitly instead,
I've documented here my explorations in getting that to work.
Susy Next alpha 5 is out, and loaded with changes.
We now require Sass 3.3,
we no longer require Compass,
and there have been major syntax improvements.
We're getting real close to launch,
and we'd love to know what you think.
Play around, and let us know!
A few new features have landed in Susy 1.0.7,
even as we work on more integrated syntaxes for 2.0.
The isolate() and isolate-grid() mixins
help you manage the worst effects of
while bleed() helps you break items out of the box.
The off-canvas layout pattern
for responsive web design
has been getting all the attention lately,
and I've had several people ask
how Susy might play along.
I'll show you how easy it is,
and how much flexibility Susy can add
along the way.