How We Redesigned INN in 60 Days

inn_logo_blue_finalToday, INN announced that we have changed our name to the Institute for Nonprofit News (formerly Investigative News Network). This change reflects the organization’s refined mission and commitment to nonprofit journalism. You can read more about that in the official press release.

When we found out about the name change, it seemed like an ideal opportunity to refresh our visual identity and relaunch to reflect our updated mission and direction moving forward. The catch? We had a little less than two months to make it happen.

Here's a behind-the-scenes look at how we redesigned both and our visual identity during the last eight weeks.

Where we started

INN's focus has always been on providing services and support to our members. As such, our own web presence and branding hadn't really been a top priority.

Old INN home page


INN logo

When I joined INN as design director a few months ago, I wanted to take that opportunity to establish a stronger and more consistent visual identity — something that better reflected our commitment to forward-thinking journalism.

Planning and sketching

Our team met at INN headquarters in California to start hashing out goals for the project. We discussed design direction and everything we wanted INN's brand to represent. From these conversations, we put together the initial creative brief for the identity redesign (you can read the full creative brief on Google Docs).

Together, we also finalized the project summary for — a short guiding document that we write for all of our web projects. The summary identifies goals, features, stakeholders, timeline, and user profiles.

We decided that we wanted a bold and simplified visual identity, with a website to match. The former INN homepage was trying to do too much and made it hard for users to navigate. The INN brand was being applied inconsistently across our various properties and didn't evoke any sort of organizational personality.

With initial discovery and planning done, I jumped right into sketching.


I  filled up dozens of pages in my sketchbook, working through potential themes and shapes, killing my darlings left and right.


I started playing with blocks and geometric elements (representing pieces of a whole, like INN's members). Around this time, I also reached out to a Minneapolis-based designer, Anthony Lane, to work with me on developing the logo and to help us put together all of the collateral pieces that go with rebranding (think business cards and swag). Tony's clean, bold style was a natural fit with the design direction I envisioned.

Wireframes and building


While we worked on getting closer to our new logotype and symbol, we also needed to start building out the architecture of the new site. Working with Adam, I put together wireframes and presented a prototype to our project stakeholders (we used InVision to do this presentation remotely, which worked quite well).


(Feel free to browse all the wireframes.)

After incorporating excellent feedback from our CEO, Kevin Davis, we set to work on building the site. Adam used Largo to create the general framework and began developing the custom layouts.

As Adam dove into the code, I created some mockups and style tiles to point us in the right visual direction. Here's a glimpse of the mess I lived in as I worked on brand elements and web styles concurrently (one of many Sketch pages):


Visual identity

Meanwhile, Tony and I had homed in on a direction for our logo and presented it to the team. Starting from the building blocks concept, Tony suggested pursuing a flexible system — a living logo and identity that would reflect our mission.


Starting from a simple, three-block mark, we developed a full nine-mark system.


We got the go-ahead to pursue this direction and started to finalize typography, symbols and the color system. If you're a designer, you know that this part of the process involved a lot of back and forth that would look like nonsensical minutiae to anyone with a bird's eye view.

For the logotype, we were down to the wire choosing between GT Walsheim and FF Mark. Both are highly geometric and modern without being kitschy. We wanted something that would have personality while also standing the test of time. FF Mark won out over Walsheim — it felt like the stronger typeface overall, was less cartoonish, and had great readability at all sizes.

fonts_compareThe color system was also close to final at this point, inspired by the bold simplicity of the logo mark. We chose bright, saturated colors that would read well in print materials and on the web.

Screen Shot 2015-03-09 at 7.20.21 PM

We encountered some issues with the vertical space of the original logo in horizontal situations (specifically the website's navigation) and adjusted the lockups. The resulting system feels more balanced and will end up being more flexible in the long run.



With the colors and logo locked down, Tony and I started pulling together the guidelines for use (download the full PDF).





Launch and what comes next

Throughout this, Adam, Ryan and I were working on refining the functionality and styles of the new Laura took the lead on content strategy and revised almost every piece of copy throughout the site.

Screen Shot 2015-03-09 at 7.29.50 PM

The entire INN staff helped us edit, revise copy, test features, and QA the site to get it ready to launch today. It wouldn't have been possible without them.

Did we get to everything on our to-do lists? Not even close. But we're tackling this project like everything we do — iteratively, learning and refining as we go. We're looking forward to seeing how people respond and will use what we learn to adjust strategy over time.

Just for fun, you know I love a good before and after shot:



Many thanks to Tony Lane, the tech team and the entire INN staff for making this possible. I'd love to hear your thoughts or suggestions for our new site and visual identity. In the end, I think our new look exemplifies who we are aiming to be — bold, forward thinking, practical, and, above all, a community.


Join Us for Book Club at NICAR 2015

designJoin us for a very special NICAR edition of the News Nerd Book Club. We'll be gathering, IRL, on Thursday, March 5, from 11:20 a.m. to 12:20 p.m.

This month, we're reading The Design of Everyday Things by Don Norman. We'll talk about how design principles and the fundamentals of human psychology influence our understanding of the world — and the work we do as data journalists.

Plus? We'll *probably* have pie.

The book club gathering will be part of NICAR Conversations — a facilitated conversation track curated by Erika Owens and David Eads. Learn more about it here.

Design Feedback Tools for Remote Teams

Good design doesn't happen in a vaccuum. As a remote team, though, we don't get to sketch around a table together, see each other's whiteboards, or have other daily opportunities for in-person collaboration.

Instead, we mostly share screenshots in group chat and, sadly, a lot of ideas don't even make it that far. It can feel like a high barrier to entry to post something online for the team to review — just by uploading, it becomes *Important* even if it's a simple sketch.

But if we're not able to share work in progress, we miss out on the value and ideas of our teammates and can end up working toward disparate goals. I want to dismantle barriers and make feedback and conversation about design a regular, fun part of our team process. It's essential to share half-baked designs, interface sketches, and unpolished ideas — even more so because we don't inhabit the same physical space.

Everybody agrees our products and apps will be better for it, but like all things with remote work, it takes an intentional commitment. You have to build even casual feedback into your workflow. With that in mind, I've been testing a few design tools meant to help facilitate asynchronous design feedback and communication. Here are my notes and thoughts on the three products we've tried so far.

Red Pen


Overall, Red Pen was the fastest and most intuitive tool. This was also the service that everyone on the team actually tried and used successfully — the other two had much lower participation. This, more than anything else, is an indicator of its value. If nobody uses it, it's useless.


  • It's easy to share and comment on designs without having to create an account (plus the workflow for account creation is smart).
  • Easy to navigate through designs using keyboard.
  • Simple and fast commenting. All our team members contributed with ease.
  • Tells you who has seen a comment (e.g., "read by meredith") and a few other nice interface features like that.
  • Retains all versions of a design.
  • Browser and email notifications tell you when there are unread comments.


  • When we tested it there was no way to customize notification settings — some of us got email updates, some of us didn't, and it wasn't clear why. While the notifications were fairly intuitive, it would be nice to be able to adjust preferences.
  • No "view all comments" option, yet. They say they're working on this feature. Without it, there's no way to get an aggragate view of all feedback for a project.
  • No way to see all versions of a design at once.
  • There doesn't seem to be a way to easily download files (not a huge deal for us).
  • You can only upload png files.

Not seeing all the comments is actually a pretty big deal for me. As the lead designer, I want to be able to take all the feedback, consolidate and translate it into tasks (which live as tickets in GitHub or JIRA). Red Pen would work better for quick feedback on sketches and design ideas, less so for long conversations or contentious feature decisions.

Red Pen is also the most expensive of the tools we tested. I sent them a couple of emails about nonprofit rates and haven't heard back.



InVision is like the Photoshop of design feedback tools. It can do a lot of different things, and feels a bit bloated as a product (when looking solely for design feedback, at least). But they have put a lot of thought into the design and functionality of their suite of tools, and you can tell that this was created by and for designers.


  • You can draw/sketch on designs and toggle comments on and off.
  • Notification options can be set at a user level and changed with each comment.
  • You can build clickable prototypes using wireframe images.
  • Ablility to upload all the file types (or at least a lot of them) and vector handling. There is also a separate repo for assets.
  • There is a conference call feature for live design walkthroughs. We tested this recently with wireframes for a new site and it worked well.
  • The project history page has rich data — I'm not sure how practical any of it is, but it was fun to see.


  • Conversations are harder to access (a few clicks to see full thread).
  • Inviting people to comment takes a few more steps, and the sign up process is not intuitive.
  • Navigating between designs within a project, and between different projects, takes quite a bit of menu searching and clicking.

This is not a lightweight product, and while there are a lot of fun features, our team didn't consistently use — or even try — most of them. If we're attempting to cultivate a lower barrier to entry for feedback, this is not the tool I would choose.

InVision does offer nonprofit discounts for the more expensive payment tiers, and has been responsive and helpful when I've reached out.



Conjure fell somewhere in between InVision and Red Pen for me. It wasn't as feature heavy as InVision, but wasn't as fast or intuitive as Red Pen. There are a lot of nice elements, but it was the least used by our team during testing.


  • A nice way of highlighting particular areas of a design to comment on (drag to select).
  • Pro level is currently free during beta.
  • You are able to approve a project when the feedback period has ended.


  • There's a separate menu you have to click to see the full thread of a comment. You can't see responses to a primary comment on the design itself.
  • Adding collaborators is more complicated than other tools we tried.
  • Navigating between projects and designs is clunky.

Overall it comes down to what our team will actually use. InVision has so many great features, but it also feels needlessly complicated for the purposes of fast feedback. We don't need every single customization option when looking for quick opinions on a design direction. Red Pen, on the other hand, had the most intuitive interface and was the product everyone actually used while testing. It is opinionated in its simplicity and that works to its advantage here.

Despite the higher price and some interface limitations, Red Pen will likely be what we use for sharing sketches and mockups. As with so many things, the right tool is the one that people will use.

For clickable prototypes and more formal design presentations and walkthroughs, I will continue to use InVision. To me it feels more like a protoyping and client-services tool than a home for internal feedback. (For a detailed comparison chart of other prototyping tools, check out

Red Pen Conjure InVision
Pricing $30/month for 10 projects $25/month for unlimited projects (currently free in beta) $22/month for unlimited projects (one designer)

Nerd Alert: Issue Four



What we're reading this week

  Adam: As a distributed team we’re always on the lookout for tips to up our remote working game (Kaeti wrote up some of our tips a couple weeks ago). I’m not an extrovert but I still found this post by Automattic’s Steph Yiu on working remotely for extroverts to have a lot of great advice. As an added bonus, the post Steph links to at the end is another great read.

 Ben: Google offers web developers many tools to help figure out what’s making your page slow. Probably the most useful is PageSpeed Insights, which tells you how well your pages perform on desktop and mobile browsers.

  Kaeti: Designers and developers joke a lot about terrible client feedback (“make it pop,” anyone?). But if you’re getting vague, frustrating feedback it’s probably your fault. We can do a lot more as web professionals to teach people how to ask good questions and frame criticism in a way that’s productive for everyone involved in a project. This feedback framework is helpful both for clients and the folks building things.

  Meredith: Searching for navigation examples led me to this award winner,Trendviz. To visually explore their tool for news analysis, select a company (mostly pharmaceuticals) and navigate through their data — sorting by articles, topics, sources, relevance and tone of voice. They also published a white paper [pdf] about Big Data and its value (with a tool like theirs).

  Ryan: David Clark describes the importance of having a code style guide and how to incorporate automated style guide enforcement into your workflow with SCSS and SCSS-Lint. Clark breaks down each component part of SCSS, explaining his guidelines for each, some being well-established best practices and some being personal preference. He also includes a SCSS-Lint configuration file that will enable you to enforce his rules automatically.

  Will: A new year, a new GitHub streak. While the 365 day GitHub challenge might be overkill, there’s some good lessons to be learned from Brandon Amos who hit one straight year of contributions this week.

  Bert: We robots are nothing if not practical. (Psst, update your Git clients.)

This week's guest contributor: Abe Handler, software developer and data journalist with The Lens

Last week, I read a summary of the recently-released CIA report on torture in the Washington Post. The content of that report was of course unsettling — but the way the findings were presented really caught my attention. The Washington Post showed readers highlights from the document, and then made it easy to jump to the original quotes in context if readers wanted more details. A friend on Twitter told me that this document was an example of "stretchtext" — coined in 1967 by the same guy who came up with "hypertext." I'm thinking about how to bring more strechtext to my newsroom in the months ahead.

Each week we ask someone from outside our team to contribute a link, tool or idea. Are you our next guest star? We think you might be. Send us a note at


Work we admire by our journalism peers

From the digital team at The Times, Doctop.js allows you access to a Google Doc in the same easy way that Tabletop.js lets you use Google Sheets. Quite useful indeed.


Gather ye rosebuds

LISTEN: Lose a couple hours with this beautiful animated sound kit. (There are some flashing images, so take heed if you're sensitive to such things.)

COOK: The science of pie crusts.

GIF: This is our last newsletter of the year. See you never, 2014.

Nerd Alert: Issue Three


Half of the nerds are visiting INN's glamorous LA offices this week. They are probably stuck in traffic eating avocados at this very moment.


What we're reading this week

  Adam: The user experience and research teams at Huge published the first in a series of posts subjecting common design elements to rigorous user testing. In this first installment they look at the myth that your most important content needs to be placed “above the fold” because users don’t scroll. Their findings might surprise you.

 Ben: President Obama’s GitHub account doesn’t have the code he wrote for Hour of Code, but it does have nine months of tickets on sunlightlabs/us-laws, one for each bill passed since March 25.

  Kaeti: I love seeing how people work. This behind-the-scenes video shows designer Aaron Draplin tackle a logo challenge for a fictional construction company. You get to see his process from sketches to Illustrator mockups (with a lot of great advice along the way). It’s so worth the 16 minutes.

  Meredith: User experience research lives under a large umbrella. The Nielson Group’s framework and methods review may be useful both in identifying questions to pursue and designing studies.

  Will: If you’ve never heard of — the advent calendar for web geeks — you’re in for a treat. Written by some of the best developers out there, it’s a great way to catch up on best practices and new technologies that you might have missed during the year. Get caught up this month and keep a look out for new articles published each day in December.

  Bert: Margaret Atwood really gets me.

This week's guest contributor: Tom Nehil, MinnPost

Vi Hart and Nicky Case’s Parable of the Polygons is not only a timely reminder of the way small biases can create big effects when multiplied across society, it's also a great example of using interactivity to tell a story in a way that's more effective than words alone. Interactivity with a purpose, not just because it's cool. (h/t: @zzolo)

Each week we ask someone from outside our team to contribute a link, tool or idea. Are you our next guest star? We think you might be. Send us a note at


Our projects, manifest

This week we hosted our News Nerd Book Club about Charles Wheelan's Naked Statistics. Read Meredith's recap post, and then vote about which book we should read next.

Want to know more about the book club? Check out this introduction and join us next month!


Work we admire by our journalism peers





Congratulations to the Chicago Tribune’s News Apps team on the 1.0 release of Tarbell, their static site generator.


Gather ye rosebuds

LISTEN: Visit NPR's Songs We Love for some of the best tracks of 2014. (Bonus, they open sourced the code for the app!)

GIF: 2014 is almost over.

Welcome to Nerd Alert: Issue One


Sign up to get Nerd Alert in your inbox every Friday.

Welcome to our very first newsletter. Have we made a terrible mistake? Is this the future of journalism? Only time will tell.


What we're reading this week

Adam: Derek Willis of the NYT writes, "Reporters and editors need to be better, stronger users of their publishing tools, not just to be effective at their jobs but to shape and inform the growth and improvement of those tools." This is something we think about a lot, particularly in our work on Largo. Many of the sites we work with still have only one or a few "web people" who do all or most of the publishing work and interaction with the CMS. But I’d argue strongly that everyone at your organization should at least know the basics, not just for efficiency’s sake but because it will also help you all to become better publishers (and give us better feedback).

Kaeti: For web folks and designers who haven’t yet jumped into the world of CSS preprocessors, this post by Molly Wilson at Sliced Bread Design is a clear and helpful introduction. The post assumes an intermediate level of CSS knowledge, but even total beginners can benefit from the overview.

And one more cool thing: Coolors is a fun tool to find color pairings and inspiration.

Meredith: Steve Losh, a programmer, suggests, "The purpose of technical documentation is to take someone who has never seen your project, teach them to be an expert user of it, and support them once they become an expert." We are building a framework for thinking about documentation and supporting users. The guidance offered here resonates, "teach, don’t tell."

Ryan: This week, INN added another member to the team — a shiny new chat bot, Bert. Bert is an instance of Hubot running on Heroku. You can find Bert's configuration here: Learn how having your own Hubot can make your life better:

Already have a Hubot instance of your own? Tweet us @INNnerds with your favorite Hubot scripts or fun chat room anecdotes.

Will: Ben Thompson of Stratechery talks about "internet scale," and reminds content creators that "the thing about Internet scale is it doesn’t just have to mean you strive to serve the most possible people at the lowest possible price."

And a bonus lunch link: Here's a fascinating cutaway of the Evening Star's office building in 1922.

Bert: Beep beep toot toot.

This week's guest contributor: Ted Han, DocumentCloud

Social media and sites like are an ever increasing component of how people read and process the news. Facebook and Twitter have made efforts to reach out to writers and news producers explicitly. But not all platforms are equally accommodating. Reddit as the self-styled "Front page of the internet" has had a particularly odd and complicated relationship with writers and news sites. The Atlantic found themselves banned site-wide on Reddit through their attempts to engage with Reddit's communities (they were later unbanned).

When reaching out on these platforms it's worth reading up on the norms and practices within the various communities they host. Reddit also stands out as peculiar here as they view themselves as a polity and actively experiment with how users and creators interact on the site. They’ve recently talked about ways to charge creators for posting to the site and also ways to distribute part of their revenue back to the community.

Want more links from Ted? Follow him @knowtheory.

Each week we ask someone from outside our team to contribute a link, tool or idea. Are you our next guest star? We think you might be. Send us a note at


Our projects, manifest

Screen Shot 2014-11-19 at 2.33.51 PM

Stealing the NPR app template for fun and (non-)profit — A couple weeks ago, our team launched its first news app (which you can find here). This week, we wrote about how we built it, how we pulled off a collaboration with this many orgs, and what we learned along the way.


Work we admire by our journalism peers

A server-less boundary service? What sort of witchcraft is this? Wherewolf, by Jenny Ye and Noah Veltman, allows you to display information (e.g., an election district) for a given geographic point.

Check out the repo for examples and code.


Gather ye rosebuds

LISTEN: Adam strongly recommends you listen to some Piedmont blues with Rev. Gary Davis.

COOK: Winter is upon us, but our hearts remember a warm summer day with drinks and tacos on a patio. Good thing we have this collaborative collection of taco recipes to see us through this dark season.

WATCH: The binge rewatch of Gilmore Girls continues (now available on Netflix). INN nerds are #teamjess.

GIF: Well this certainly gives us a lot to think about over the weekend.

Sign up to get Nerd Alert in your inbox every Friday.

How We Make Remote Work Work

The INN nerds are a distributed team, which means we work in different locations and time zones and sometimes in our pajamas. Working from home full time also means we have to think intentionally about communication, structuring our days and setting boundaries around our work.

Here are a few of the tips and resources we've found helpful as we learn how to work effectively as a remote team.

Use Your Words

Remote work requires varsity-level communication. Not only do you need to keep your colleagues informed about what you're working on, but you also need to speak up about challenges and frustrations. Lacking the ambient awareness of a shared physical space, your coworkers can't see if you're struggling or confused, or if you have bruised feelings because of a miscommunication. It's on you to proactively reach out and address things sooner rather than later.

To help facilitate this sort of openness, we start every day with a short standup meeting using Google Hangouts. This allows us to review what we're working on, set priorities and address obstacles. Our weekly team meeting gives us space to discuss the bigger picture stuff, review current projects and set priorities for the following week.

We use HipChat, Google Hangouts and other tools to stay in touch throughout the day. (See the full list of our favorite tools below.)


Remote work offers the flexibility of setting your own schedule, but it also means you can feel like you're working 24/7. We think it's important to set boundaries around our work each day. Work reasonable hours. Don't send or expect responses to non-emergency email after hours. When working in different time zones, don't feel bad about reminding a team member that a late afternoon meeting in their time zone might be well into the evening for you. Taking time to not work makes our working time more productive.

During the day, it's all too easy to get sucked into our screens and not blink for hours on end. To counteract this sort of faux-productivity, we take a lot of walks and other short breaks away from our screens. Snacks and coffee are important, too.


Building habits and routines can help prevent feelings of disconnect or isolation — and feelings of wanting to stay in bed and catch up on The Vampire Diaries. The advice is almost rote at this point, but for good reason: Have a dedicated space in your home where you "go to work." Take a shower. Put on pants.

Sometimes a change of scenery can help reset your focus. Take advantage of coworking spaces in your town or the tried-and-true coffee shop work session.

And most importantly: If something isn't working, or you start to struggle with lack of direction or motivation, speak up. You may work by yourself but you're not alone.

Face Time

While we're primarily remote workers, we like to see each other's faces in person a few times a year. There are some things that are just easier to do when we're all in the same room. These IRL meetups are essential for keeping us connected us a team. We tackle long-term planning and major projects, and build camaraderie over good meals and music and conversation.

Resources and Tools

  • There are great remote work tips in this Source article by Christopher Groskopf
  • Helpful tips on remote productivity
  • The books on remote work
  • HipChat: We use this as our group chat tool and always-on back channel
  • GitHub: For versioning and hosting our open source projects
  • Bitbucket: Versioning and hosting for Largo child themes for all the member sites we host. This allows us to add devs at member organizations to a repo just for their child theme so they can commit changes to a theme for us to review and push to production.
  • JIRA: For project management, planning sprints and iteration cycles, time tracking, and service desk features
  • Bee: Combines issues and tickets from JIRA, GitHub and others into a streamlined interface. Also offers time tracking and task prioritization.
  • Screenhero: Remote pair programming software
  • Google Hangouts: For meetings and daily scrum
  • Dropbox: For file sharing
  • 1password: For password management (synced to everyone's computers/devices using Dropbox)

Also, make sure to check out our growing list of tools and services (including many of the above) that offer discounts to nonprofits.

Real Life

We can spout best practices and advice all day, but the real life application can vary drastically depending on barometric pressure, how early you woke up to a crying baby (or puking cat), and countless other variables. One of the joys of remote work is that it makes room for the realities of life. As a team, we're choosing to trust each other and extend enough flexibility that a work day doesn't have to be an immutable cage.

[Full disclosure, I wrote this post in pajamas, curled up on my couch under a blanket.]

To illuminate more of the real-life applications of remote work advice, we'll soon be launching an occasional series of interviews with remote workers — starting with our own team — that will explore how different people make remote work work: what their set-up looks like, how they structure their days, and what they do in the face of frustrations or flagging motivation. We hope to collect honest portrayals of our modern working life and learn from each other in the process. Watch for more in this space soon.

Want to share your remote work experiences? Get in touch at

How Your Small Team Can Have A Big Impact: Lessons From ONA 2014

Making things happen with limited resources and a small team can be a challenge. It can also be an opportunity to experiment and think creatively. During our ONA panel on Friday, John Keefe of WNYC succinctly captured this sentiment with the sage advice: Do crazy sh*t sometimes. (In his case, that meant roadtripping to a cabin in the Catskills with his team in order to finish a major project.)

John, Adam and I share the experience of building and leading small news apps teams within our organizations and we've learned a lot along the way. We wanted to talk openly about our biggest obstacles and how we've tackled them — in order to make our work more effective and our working lives happier.

Here are a few of our ideas:

  • Break down ambitious projects and iterate. Figure out the most essential part of the project/idea and start by solving that problem. You can add features and build on the project in the future.
  • Check in regularly and be honest about obstacles. We can't get things done if we can't talk about what's preventing us from doing the work.
  • Attend the daily news meeting. If possible sit in the newsroom. Being present during the editorial process will encourage collaboration and make your news apps team more accessible.
  • Don't make people feel stupid. If you want to build momentum for news apps and special projects in your org, try not to talk down to your colleagues just because they have different skill sets. Instead, encourage skill sharing across departments, talk about what you're learning, and reach out to those who may be shy about approaching the team.
  • Say no and explain why. Inevitably you will have to say no — you're on a small team, after all. But when you do, explain why and include people by explaining your decision making process. Affirm ideas even you can’t immediately execute them.
  • Automate repetitive tasks. Think of it like a word processing macro. Anything you do over an over again can probably be automated, saving time and making your process more consistent. Writing simple automation scripts can also be a great way to learn some basic programming even if you’re not very technical (or at least is a way to start thinking like a programmer). Check out IFTTT for some ideas.
  • Document all the things. It can feel like a waste of precious time but it will save your butt in the future. Keep a simple txt file for a project and keep notes about what you've learned, bugs you've solved and your general process. This documentation will help you share your work with others and help you remember how the heck you built something.
  • Look to the community. There are so many excellent resources out there. Check out IRE/NICAR (and subscribe to NICAR-L). Explore some of the open source code that newsrooms are releasing. Read about how other teams make things over at Source. You don't have to reinvent the wheel, and this community is full of people who want to help.

Check out all of the slides below. Find our notes (and contribute your own ideas) on the Hackpad we put together. We know our ideas are only a small piece of this important topic and we'd like to keep building on the conversation.