THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
These are a list of some initial requirements for the updating of the existing website at http://ofbiz.apache.org
Initial Requirements
- OFBiz Logo - needs to be better quality and resolution to be improved. (NOTE: OFBiz registration in progress so need to be aware that TM may change to Registered Trademark at some point in the future / May need to prepare graphics for both)
- Menu navigation to be moved to the top of the screen as there is space
- Keep menu options visible (i.e no drop down menus)
- Restructure / re-write webpage text (Is there too much? Would it be easier to link to a features page?)
- Have a separate section for potential service providers / developers (e.g if you are a developer .....)
- Have a separate section for end users (e.g if you are an end user ......)
- Remove News section and replace it with OFBiz blog
- Keep Twitter feed
- Make website responsive and available on different media types (e.g monitor, tablets, smart phones?)
OFBiz Demo - Do we reduce it to link to only 1 demo (e.g the current stable release) or do we have one demo for developers and another demo tailored for end users? (Could be handled by the 'if you are a developer.....' and 'if you are an end user .....' logic)
Jacques Le Roux: We could also reduce to last stable and instead of "old" show the current consolidating branch. But initially the idea was to show only released branches (though the trunk is accessible but not from the site).
One demo for developers and another tailored for end users could be a nice idea but would need some work I'm not sure the community is ready to give...One page design that could highlight different aspects of OFBiz
- OFBIz framework
- OFBiz ERP
- OFBiz eCommerce
- Must conform to ASF Guidelines as follows:
Jacques Le Roux: We have that already but:
the security page is linked from a vulnerabilities anchor in our download page. Jacopo did that, I like it.
IIRW, we had a link to the main ASF homepage in the footer but it's no longer there. We would put it back (not hard to maintain once done on every page).
Whatever main navigation system your project website uses, it must feature certain links back to key pages on the main www.apache.org website. These links should appear in whatever main navigation system your site uses on all top level pages for the project or subproject.
"License" should link to:
http://www.apache.org/licenses/"Sponsorship" or "Donate" should link to:
http://www.apache.org/foundation/sponsorship.html"Thanks" should link to:
http://www.apache.org/foundation/thanks.html"Security" should link to either to a project-specific page detailing how users may securely report potential vulnerabilities, or to the main http://www.apache.org/security/ page
All projects must feature some prominent link back to the main ASF homepage at
http://www.apache.org/De
Who will visit the Site?
Try to identify the types of users that will come to the site and try to log the type of information they will want
| Who Could Visit the Website | Background | What are they looking for? | |
|---|---|---|---|
Chief Exec Officer (CEO) Chief Finance Officer (CFO) | They are looking for a new platform and want to see if OFBiz could meet their requirements They need information to be able to make a business level decision They want to understand the risks / challenges / benefits | What marketing / business documentation is available? What features does OFBiz have? What are the licencing requirements? Who else is using OFBiz? (More specifically what businesses like them) What Service Providers are available? (Do they speak their language?, Are they close by? etc) What are the benefits? What are the risks? What are the challenges? | |
Chief Information Officer (CIO) Chief Technology Officer (CTO) | They want to evaluate any potential new platform Want to find out if it could fit in with their existing company landscape Is it a good match to his staff capabilities to support et |
Same as CEO / CFO requirements What is the technology and architecture? What frameworks are used? What documentation is available? What are the integration capabilities? Can we implement it ourselves or do we need a Service Provider? | |
| Adhoc User / Potential New User | They have heard about OFBiz and want to find out what OFBIz is They dont know what OFBiz and have been referred via a search They are researching OFBiz as a possible solution They are looking for a Service Provider (Might split these up into different stories / flows through the site...) | What is OFBiz? Why should they be interested in it as a user? How can it help them What are the benefits (user perspective)? What are the main features What does it look like How do they use it Who is using it (References) How can they download it How can they install it | |
| Adhoc Developer / Potential New Developer | They have heard about OFBiz and want to know what it is and what it can do They want to know how to use it
| What is OFBiz? What is technology and architecture? Why should they be interested in it as a developer? How can it help them? What are the benefits (technical / developer perspective)? What does it look like? How do they use it? How can they download it? How can they install it? What technical documentation is available? What are the best practises for development? What is the data model? What APIs exist? What support is available if they have any issues? | |
| Existing User | |||
| Existing Developer | |||