Viewing 0 current events matching “documentation” by Date.

Sort By: Date Event Name, Location , Default
No events were found.

Viewing 12 past events matching “documentation” by Date.

Sort By: Date Event Name, Location , Default
Sep 20, 2008
Calagator Documentation Sprint
CubeSpace [ *sniff* out of business 12 June 2009]

Join us to to work on the Calagator User Guide. This is a great chance to learn more about the project and help out with an important task. Previous code sprint participants and newcomers are all welcome to contribute.

Sep 13, 2012
Portland Perl Mongers -- h2xs is da bomb + dzil Pod::Weaver
Free Geek

speaker: Ian Dees + Joshua Keroes


➜ will cover what it's like for n00bs learning how to create a new Perl module, including:

  • Where rookies look for "Getting Started" information
  • Which tools we can readily find for the job
  • What kinds of questions we have about namespaces

What Ian would like to do to help:

  • Listen to your answers
  • Format them into some kind of guide (or supplement an existing one)
  • Hand it to a Perl expert to post in the right place
  • Commit to checking in a couple of times a year to keep the information current

You will be vastly enlightened, or horrified.


➜ will continue down the Dist::Zilla path of Automated Enlightenment and speak on Pod::Weaver.

In July, Duke Leto gave Portland an introduction to Dist::Zilla, demonstrating how it can help write, package, test, and release your modules; automating the boring stuff like figuring out prerequisites, automatically inserting and updating $VERSION's, getting rid of all those meta files and generating them automatically; all good ways to focus on the important stuff: the code.

This month, Joshua will show how Pod::Weaver can help automate the boring parts of writing documentation so you can avoid getting bogged down by boilerplate and focus on the important stuff there: the docs.

As always, the meeting will be followed by social hour at the Lucky Lab.

Apr 8, 2013
Write the Docs
through McMenamins Mission Theater & Pub

Write the Docs is a two-day conference focused on documentation systems, tech writing theory, and information delivery. It will be held on April 8-9 in Portland, Oregon.

Writing and maintaining documentation involves the talents of a multidisciplinary community of technical writers, designers, typesetters, developers, support teams, marketers, and many others.

This conference creates a time and a place for this community of documentarians to share information, discuss ideas, and work together to improve the art and science of documentation.

We invite all those who write the docs to spread the word:

Docs or it didn't happen!

May 5, 2014
Write the Docs
through Crystal Ballroom Website
Jun 10, 2014
PNSQC Presents: Cultivating Biological Documentation by Juliana Arrighi, and Lightning Talks
Glyph Cafe

Our meetup site.

Feb 3, 2015
Write The Docs PDX: Enabling Walkup Contributions to Your Project Documentation
eBay Community Lounge

Everett Toews, Developer Advocate at Rackspace Hosting, will share his experience using Git and Markdown to make it easier for the community to propose changes to their documentation. Please arrive by 6pm. I want to start sort of promptly, by 6:05. (I'll be there by 5:30.) The building entry doors will be locked at 7pm. I'll appreciate help cleaning up, so we can depart by 8:30.

A common complaint against many open source projects is documentation. Insufficient, incorrect, non-existent, hard to find, and difficult to update are things we typically all hear. There are a lot of different ways to tackle these problems. There's no silver bullet but one of my favorite tactics is lowering the barriers for absolutely anyone to contribute documentation.

Ideally, lowering the barriers means:

  • using a common and well understood documentation markup language

  • using documentation editors that are commonly available

  • not requiring your contributors to install and configure tools

  • providing a preview of the updates to make reviews reviews easier

Learn how Apache jclouds has enabled walkup contributions to our project documentation. We've benefited from better documentation, shorter review times, and building community through contribution.

Jun 9, 2015
Counterpoint: Don't Write The Docs
New Relic

The WTD NA conference is coming in May, so it's a good time to start planning for post-conference Meetups. We'll meet again on Tuesday June 9, when Diana Potter, the Senior Director of Customer Success at tells us when to say: "Don't Write The Docs".

When I started working as a Technical Writer, our local VP told me that to do my job well, I'd spend significant time testing and pushing for changes to our software. To me, that sounds like the essence of Diana's talk.

Diana manages's support/docs team. As such, I expect that her talk will interest Documentarians, Support Engineers, and Knowledge Base Creators. Here is the abstract of her talk:

Writing user facing documentation gives you a unique perspective on software. How does something work? Will the software explode when I push this button? Okay, now how do you explain that explosion to a user, in a way that makes sense and captures their attention?

What do you do, though, when that unique perspective illustrates areas of confusion? Why document something that's confusing? Fix the confusion!

Write the docs that make sense for the user and advocate for product changes on behalf of the "user" too.

How do you decide when it makes sense to document, and when it makes sense to dig in your heels and push for an internal change to the product? How can you use documentation to push for change? Come learn what I've learned, the processes I've put in place, and learn the following chant: "does this doc make sense?"

Sep 30, 2015

Hello! sildenafil , tadalafil ,

Aug 3, 2016
PDXRust: RustDoc For Everyone, and Bridging Ruby And Rust

There will be 2 talks this month!

Rustdoc for Everyone:

You don't have to be a great writer to create great documentation. There are simple techniques and rules you can follow to build documentation for your users. Rust ships with documentation tools, but not all crates take advantage of them. Documentation is the first way that developers interact with your code - great documentation sets your crates apart, helps users skip easy questions, and cuts down on bug reports. In this talk, we will explore techniques for writing great documentation.

Speaker Jeremiah Peschka has been breaking software since 2000 - he's been told this sounds impressive, but he thinks it might just make him feel old. He blogs over at and can be found on twitter and IRC as peschkaj. When Jeremiah isn't working with databases and Rust, he can be found playing video games, hanging out at food trucks, or napping at home.

Bridging Ruby and Rust:

Ruby is not the fastest language in the world, there is no doubt about it. This doesn't turn out to matter all that much – Ruby and its ecosystem has so much to offer, making it a worthwhile tradeoff a lot of the times.

However, you might occasionally encounter workloads that are simply not suitable for Ruby. This is especially true for frameworks like Rails, where the overhead wants to be as little as possible.

In this talk, we will explore building a native Ruby extension with Rust to speed up parts of Rails. What does Rust have to offer here over plain-old C? What kind of challenges would you run into when briding a dynamic langauge like Ruby with Rust? Let's find out!

Speaker Godfrey Chan is a member of the Rails core team and a co-author of Helix, a toolkit for implementing Ruby classes in Rust. He works at Tilde Inc, splitting his time between building Skylight and open-source consulting.

Other Information:

PDXRust meets on the first Wednesday of every month, from 6-8pm, at Mozilla's Portland space. The first hour is either lightning talks from group members or a more in-depth tutorial from a Rust expert, and the second hour is hacking and social time.

Join us in #pdxrust on ( with any feedback about what you'd like to see!

Remember that Rust's Code of Conduct defines the Rust community's expectations for participation.

Feb 8
Write The Docs PDX - Networking with a side of Write The Docs proposals
New Relic

NOTE: We'll be in New Relic's newest meeting room, on the 27th floor

The Write The Docs NA conference returns to Portland in May, and the deadline for proposals is February 10 (midnight PST).

For the third year, we'll give people who want to propose a chance to test things out, either by speaking briefly, or by brainstorming their proposals.

FYI, O'Reilly has an excellent guide to creating conference proposals, "Propose, Prepare, Present". If you navigate to, you can get the eBook version for free.

We'll start with a brief networking session from 6-6:30.

At 6:30, I'll make a few announcements. Anyone who wants to try out a "preview" of a conference talk (5-10 min), or just present their draft proposal for comments, can speak to the group (or ask questions) after that.

Mar 14
Write The Docs PDX - Learn About The Wacom User Help System
New Relic

Wacom -- a company which develops Pen Input hardware -- needed a user help system to move beyond static PDFs. Their solution was to separate product-specific PDFs into a series of, mostly common, HTML topic pages. These HTML file were, in turn, processed into a web deliverable package via Python scripting.

The solution is complex, as the Wacom system includes interrelationships between 150+ topics across over 30 products and 14 languages.

The solution required “a more technical Tech Writer” -- as it required knowledge of HTML
Excel Macros

Wacom implemented their solution by integrating their tech writer in their Engineering team. They also included a dedicated engineering resource to support design and development of their technical docs.

Speaker: Arthur Krebsbach, Windows Software Engineer

Apr 11
Write The Docs PDX - Preview Talks at Write The Docs 2017
New Relic

Save the date! We'll give people who are scheduled to speak at the Write The Docs 2017 conference a chance to rehearse their talks.