Product Orientation

Problem

A visitor of an open-source-project hits on the website. The visitor is intrested into the Product of this open source project.

The visitor has to filter many irrelevant information, which subjects the Project - the he reaches finally the Product download and documentation.

Abstract Rule

  • Missing modularity is an entry barrier.

Suggestions

  • Increase the product-orientation and modularity of a project
    • especially on the website and the project infrastructure.
  • Seperate Content for Users (Product) and for Contributors (Project)

General Validity Template

The Case-Study "Jam Beans" demonstrates a fictional open-source project, which has [currently] the following main sections:

"Home | Project | Product | Support | Community | Vendors | About"

Although the Jam Beans Case-Study deals with a large-scale open-source system, the website organization has a general validity. You can drop e.g. the Community and Vendors sections. Product Website Evaluation

  • The 20sec Website Test

Practical Examples

As an practical example of product-orientation, a well known open-source product: