Published articles
The following 6 articles by Chris Stoner have been published in ZATZ magazines.

A developer's quandary: Lotus DevCon or Lotusphere?
If you can only get to one conference a year, which one is it going to be? Chris Stoner gives you a quick breakdown of the benefits of each to assist you in making this important decision. [DominoPower Magazine, July 2000]

Keeping user credentials in a frameset
The way each Web browser handles the pages our sites serve up is important to understand, because the user experience is really based upon what they actually see, not what we intended for them to see. In this article, Chris Stoner goes "under the covers" to help shed a little light on the issue of caching credentials. [DominoPower Magazine, May 2000]

LotusScript agents and the Web
LotusScript Agents are powerful tools that can be used in a variety of ways. I often use them to move documents through an Approval Cycle by having the Approver click on a button to either Approve or Deny the document. This works well in Lotus Notes, but how do you get the same functionality over the Web? Chris Stoner explains that by using LotusScript Agents, it's really not that hard. [DominoPower Magazine, February 2000]

A Web browser development environment
Developer Chris Stoner (a.k.a. GreenJellyBean after her RAV4) was sitting in bumper to bumper traffic one day (presumably in the same RAV4) and thought up a cool new feature she'd like to see in Notes and Domino: a development environment you can use from a Web browser? In this "idea paper", Chris shares her thoughts on this innovative idea. [DominoPower Magazine, November 1999]

OLE automation primer
Ever wanted to manipulate your Notes data with another application, but didn't know where to start? This OLE automation primer will get you familiar with launching and manipulating another application from Notes using LotusScript. [DominoPower Magazine, September 1999]

Using one template for three different uses
Have you ever wanted to create one template that can support multiple renditions of itself? For some applications, you may be maintaining a bunch of templates that are basically the same. If you make a design change to one, then all need to be updated! The design of these templates can quickly get out of sync. A better solution, given this scenario, would be to have one common template that adapted to your needs. This article by Chris Brown (a.k.a. GreenJellybean) explains how to do just that. [DominoPower Magazine, June 1999]