“Like”-able Content: Spread Your Message with Third-Party Metadata
Giving content proper structure is one of the most important things we can do—because the more structure we have in our content, the freer it becomes. Most of the time, structured content’s classifications and divisions allow for the content’s presentation on a multitude of platforms. By breaking content down into its natural components, we ensure current and future compatibility and display in a wide range of devices and environments. Third-party metadata schemas, like Facebook’s Open Graph protocol and Twitter Cards, build on this ideal. And they are quickly becoming part of what it means to have a modern and complete online presence. Facebook’s Open Graph protocol, or OG (not to be confused with rapper Ice-T’s 1991 album, “O.G.”), builds on the notion of compatibility by way of appropriately breaking down content into chunks, but from a platform-specific point of view. Twitter also rolled out a metadata scheme of its own , called Twitter Cards. These metadata protocols ...
absence
action
activity
applications
association
attribution
authorship
billion
classification
cms
comments
compatibility
competition
complexity
consistency
content-y
creation
cuuute
description
development
devices
difference
dissection
division
dublin
efficiency
elements
encouragement
entity
environment
evolution
experience
extension
facebook
fashion
flexibility
ford
foundation
function
gifs
google
governance
gravity
hey
html
ice-t
implement
implementation
importance
improvements
influence
linkedin
luckily
microsoft
million
mustang
navigation
navigator
netscape
niceness
notion
options
organization
ownership
palm
parity
performance
placement
preparation
presence
presentation
privacy
pro
relationship
science
section
selection
similarities
situation
solitaire
sooo
truncation
twitter
url
version
windows
Inside the Tech of SpaceX's Homegrown Rocket Engine
An anonymous reader writes with this excerpt from a look at the engine behind SpaceX's Falcon rocket, the Merlin: "The rockstar of SpaceX may be Elon Musk, but the lead man behind the fire power is Tom Mueller. He is the Vice President of Propulsion Development and founding employee at SpaceX. Musk sought Mueller out in 2001 when Musk decided to build his own rockets instead of buying some from the Russians. Musk caught wind of a rocket engine Mueller built in his garage and 'apparently had a religious experience' once he saw it. If you didn't know, Elon Musk used $100 million of his Paypal money to start SpaceX. That money was used to build the Merlin engine Mueller had designed. The Merlin engine is the first new American booster engine in ten years and only the second in the last 25 years."
american
development
elon musk
experience
falcon
merlin
million
mueller
paypal
propulsion
russians
spacex
tom
vice president
Found more than 1 month ago on channel
Slashdot
Responsive Comping: Obtaining Signoff without Mockups
If you’re making websites, chances are you’ve given some thought to what constitutes a responsive-friendly design process—and you’ve probably found that adding a mockup for every breakpoint isn’t a sustainable approach. At least, that’s what happened at my company, Bearded , where we had spent years creating websites in Photoshop or Illustrator, having those mockups approved by our clients, then recreating those designs with CSS. Until now. A few months ago, we stopped making static image-based mockups in favor of designing with code. This is not a new idea—heck, Andy Clarke was arguing for in-browser design in 2008 . But new or not, you may still be mystified at where to begin—or feel unmoored and disoriented at the prospect of giving up the approach you’ve long relied on. But fear not, gentle reader. Let’s take a look at our new mockup-less web design process and see just how easy it can be to get that Photoshop monkey off your back, and have a fresh new beginning with ...
aahomecare
adjustments
american
andy
association
audience
clarke
cms
collaboration
communications
comping
css
decision
development
discussion
diversion
elements
enhancements
environment
experience
experiment
fluidity
functionality
git
heroku
hey
homecare
html
implement
impressions
information
instance
interaction
invitation
location
luckily
membership
navigation
nope
opinion
opportunity
organization
perfection
photoshop
practice
priority
question
reaction
revision
rss
samantha
sass
selection
signoff
situation
sparkbox
statement
technology
twitter
url
urls
warren
webkit
yep