• All in the Memory -- bookkeeping services
• Arabella -- a dynamic musical duo
• Bytesmiths Editions -- large, archival, fine-art photography on unusual materials
• Bytesmiths Press -- artists' services: web design/hosting, jury slides, giclee reproductions, opening announcements, brochures, etc.
• Champagne Beadworks -- handcrafted jewelry and beadwork
• Crafted By Carol -- handcrafted jewelry and beadwork
• Dana Fontaine -- unique photography-derived art
• Dymond Graphics -- note cards, pet/people photography
• Fountains & Funktini -- glass art and more from Beth Keenan and JoAnn Rawley
• Gemini Gypsy -- Carole Good-Hanson's fused glass frames
• Mary Kollman Fine Art -- lovely floral watercolor originals
• Primrose Studio -- terra cotta switch plate covers and wall art
• Ratso's Studio -- astoundingly realistic bronze sculpture
• The Spiral Gallery -- local artists exhibit in the Oregon Cascades foothills
• The Roaming Artist -- info and resources for artists "on the road"
• Van Dyke Sepias -- Jan Van Dyke's nostalgic sepia toned photography
• Veggiemog -- life and times of Kelly O'Toole's Unimog, running on biodiesel
• Village of Willamette Arts Festival -- annual visual/performing arts festival, third weekend of September
• Whitehorse Designs -- Gwen Miller's beadwork and fused glass
• West Linn Arts Commission -- city support for the arts

Documentation Needs

- Link expression of design with implementation of design -- documents live with the code they describe, and the document is the specification for the code. This "Knuthian" concept is key to any successful design doc strategy; anything less, and "doc synch" is a big problem.

- Must be simple to use, if you expect it to be used with any rigor. The less integrated it is, the harder it is to use, and the more likely your project will slip back into "code it, then design it, then document it" habits.

- Enforcement may be appropriate when you have developers who are used to documenting their work after implementation (or not at all!). Automatic release controls may be imposed according to presence or absence of required project documentation. Must be supported by tools, such as comment counters and format compliance checkers, to avoid surprises at integration time.

- Seamless integration with code privacy -- users must only be able to change documentation for the code they are able to change. Documentation viewing permission must be controlled separately from the code it documents. This is necessary to preserve encapsulation during re-use.

[ prev | top | next ]