Skip to content
Find file
Fetching contributors…
Cannot retrieve contributors at this time
89 lines (76 sloc) 4.3 KB
<!DOCTYPE html>
<html manifest="manifest.appcache">
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, minimum-scale=1.0">
<title>Come Aboard</title>
<link rel="stylesheet" href="styles.css">
<body id="come-aboard">
<header role="banner">
<a href="index.html"><img src="assets/fflogo.png" alt="Future Friendly" title="Future Friendly"></a>
<h1>Come Aboard</h1>
<p>You are part of this thing. When you <a href="thinking.html">go future friendly</a>, you help your own work and you offer an example to others, too. Here are some things you can do.</p>
<section id="philosophy-first">
<h2>Put philosophy before technique</h2>
<p>Future-friendliness describes design principles, not specific techniques. Individual techniques will evolve, thrive, and then decline. No single method, technology, or workflow is perfect for all projects. Don't be religious about techniques. Instead, be passionate about future-friendly values.</p>
<section id="call-it-by-name">
<h2>Call it by name</h2>
<p>Use the term "future friendly" when you discuss work that follows these design principles. There is power in a name, and popularizing this phrase is part and parcel of popularizing the ideals behind it. Share the love: use the <a href="">#ffly</a> hashtag, and emblazon your stuff with the Future Friendly logo (<a href="assets/ffly.eps">.eps</a> or <a href="assets/">.ai</a>).</p>
<section id="spread-word">
<h2>Spread the word</h2>
<p>Introduce future-friendly thinking to your peers, employees, and managers. Share this site with them. As you advocate, understand that new ways of thinking often meet resistance. Strive to understand where that resistance comes from. Frame the benefits according to your colleagues' personal goals—for example, business value, empowering users, reaching a larger audience, easing long-term maintenance, whatever matters most to them.</p>
<section id="techniques">
<h2>Select techniques that are future friendly</h2>
<p>Examine your project's goals, and adopt a process and approach that accomplishes those goals while following future-friendly principles. This website purposely describes only those broad ideals, but the <a href="thinking.html">Thinking</a> page links to resources for action and education. The authors of this site frequently write in detail about current future-friendly approaches, and we invite you to get acquainted with our work and share your own with us:</p>
<section id="signatories">
<li><a href="">Andrea Trasatti</a></li>
<li><a href="">Brian LeRoux</a></li>
<li><a href="">Bryan Rieger</a></li>
<li><a href="">Brad Frost</a></li>
<li><a href="">Jason Grigsby</a></li>
<li><a href="">Jeremy Keith</a></li>
<li><a href="">Josh Clark</a></li>
<li><a href="">Luke Wroblewski</a></li>
<li><a href="">Lyza D. Gardner</a></li>
<li><a href="">Scott Jehl</a></li>
<li><a href="">Scott Jenson</a></li>
<li><a href="">Stephanie Rieger</a></li>
<li><a href="">Tim Kadlec</a></li>
<section id="learn-more">
<h2>Learn more</h2>
<p>Learn more by following Future Friendly on Twitter at <a href="">@future_friendly</a> or <a href="">this list of future-friendly practitioners</a> assembled by <a href="">Dave Olsen</a>.</p>
<nav role="navigation">
<li><a href="index.html">Home</a></li>
<li><a href="thinking.html">Thinking</a></li>
<li><a>Come Aboard</a></li>
<footer role="contentinfo">
<li>We're <a rel="license" href="">Creative Commons friendly.</a></li>
<li><a href="">Talk to us.</a></li>
Something went wrong with that request. Please try again.