Making a reusable code package based on the success of the Apps.com grid
In the Apps.com portfolio piece, I talked about how a mobile-first responsive grid was needed for that site. Due to the success of the implementation, the code was stripped out, made generic, and refined into a drop-in code package that could be used in any project.
Writing good documentation
This turned into something of an internal "open source" project that had to be treated like any other open-source project. A GitHub repository was made with documentation, examples code, and a working demo.
For the written documentation, I had to approach this knowing that some people would be entirely unfamiliar with how a grid like this works. The language and examples are meant to be understood by both newcomers and those familiar with the system and just need specifics.
For the more experienced, a QuickStart guide and inline comment documentation was included. Many developers chose this route and were instantly able to start, as they knew what to do but had never been provided a company-wide platform to imlement.
And for the real aficionado, all code had plentiful commenting and explanation throughout, both for implementation but also for maintenance by future owners.