Writing blog posts and strong documentation for your open source projects is crucial for growing both a user and a contributor base. Your writing is the most effective way to communicate why and how people should use your project. But you’re a software engineer, not a content strategist. You may not know how you can effectively target the people you need to with your blog posts and documentation or how to accurately communicate the goals for your project.
Here’s your chance to improve your skills as you walk through the writing process with Alison Spittel. You’ll cover everything from deciding who you’re writing for to what happens after you press publish (or commit to GitHub). Then you’ll take a look at some projects that have great content strategies and discover how to understand who your target audience is—whether that’s new developers or specialized experts. Along the way, Alison will help you come up with blog post topics, explain how to make that content engaging and understandable, and show you how to reach that audience and grow a following.
You’ll leave with the following completed worksheets:
Ali Spittel is a programmer, teacher, writer, and a software engineer at DEV. You can read her writing, which had well over half a million readers last year, at dev.to/aspittel. She moonlights as a lead instructor at General Assembly. In addition to contributing to the open source DEV platform, Ali also maintains Learn Code from Us, a platform that highlights technical content creators who are members of underrepresented groups in tech. She’s also highly involved in the DC tech community, where she’s the tech director for Women Who Code, and she’s the founder of the Art + Code Collective and the Vue Vixens’ DC chapter.
For exhibition and sponsorship opportunities, email oscon@oreilly.com
For information on trade opportunities with O'Reilly conferences, email partners@oreilly.com
View a complete list of OSCON contacts
©2019, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • confreg@oreilly.com