Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

NOTE: The new logo files done by HotWax are attached to this issue to help with style/visual choices.

Target Audiences

  1. Business Users
  2. Enterprise Architects
  3. Developers

Current Site Structure

http://ofbiz.apache.org/ 

What is OFBiz?

Project Overview
Is OFBiz for Me?
Feature List
Features Coming Soon
User List
User Stories
Brochures, etc
Documentation
Conference Videos
Framework Intro Videos

Demo Site

Stock Demo by HotWax Media and Contegix

eCommerce Demo
Management Apps

Download OFBiz

Getting Started (Read this first)
Source Access (Recommended)
Weekly Builds
Documentation
Copyright & License

Resources & Tools

dev Mailing List
user Mailing List
commits Mailing List
Issue Tracker (Jira)
Source Repository (SVN)
Main Documentation Page
Documentation (Confluence)
Doc Site: Wiki
Conference Videos
Open Source Projects&Standards

Old Resources

Old Mailing Lists
Old Issue Tracker (Jira)
Old Wiki
The Old Java.net Site
The Old SourceForge.net Site
Apache Incubator Status

Apache OFBiz Related Blogs

OFBiz and Open Source by David E. Jones
What's New in OFBiz by Si Chen

Apache OFBiz Communities

Locales

Germany
Thailand
United Kingdom
Netherlands

Industries

Government Travel

Service Providers

Complete Listing on Wiki
HotWax Media
Open Source Strategies, Inc.
Integral Business Solutions
Brainfood
Ant Websystems
Automation Groups International
Sykes Development Ltd
openTrends
Nereide
Agrenon GmbH

New Site Structure

Proposal One

Created by Jacopo. Feedback is welcome... feel free to change/add/remove information.

Main concepts:

  • No Header  Links/Tabs (or only two, one for the website and one for the documentation site)
  • A left side column of links in all the pages (always the same); the link to which the current page refers is highlighted
  • A very simple and minimal set of links (in the left column), something like this:

===Apache OFBiz===

  • Welcome
  • News
  • History
  • License

===Resources=== NOTE: just a draft at the moment...

  • Documentation
  • External Resources NOTE: pointing to a new page with external links to blogs, communities, old resources, demo sites etc...
  • Marketing NOTE: pointing to a page with testimonials, user lists etc...

===Download===

  • Releases
  • Trunk

===Community===

===Project Management===

  • Mission NOTE: the ASF Board Resolution
  • People NOTE: PMC members, committers, developers
  • Bylaws

Proposal Two

Proposal Three

Visual Design Goals/Ideas

To get things rolling, let's answer these questions that Si posed to the group last week as well as getting eveyone's general feelings on what they would be looking for in a redesigned OFBiz site. I think that having these questions answered as well as more input on the overall look and feel will give the designers a better chance at hitting the mark.

NOTE: I have linked out to Si Chen's original email which called out many of the following points - in case anyone wants to check the origin of any questions in particular.

What does OFBiz stand for?

  1. What are the core values and principiles of the project? - Si Chen
  2. Why are they better for developers and users of OFBiz? - Si Chen
  3. How can we articulare our information in a way that gets people behind the philosophy and the framework? - Si Chen

General Design Comments

  1. It should be more "visual" but not overly graphical or fancy with flash or images, etc. I think open sourcers are looking for information, and something that looks overly commercial would not be right. - Si Chen
  2. We should play up more about the sites, products, and projects that use OFBiz. It's really great how many major commercial sites, products, and open source projects use OFBiz, and that should give us more credibility. - Si Chen
  3. We should consider two different target audiences: persons interested in using the system (out of the box features, user guides, case studies, etc...) and people interested in customizing/implementing the system (details about the framework, developer's guides and docs etc...); I think that we should clearly define the two areas of the web site's content. - Jacopo Cappellato