Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Website » Design and Functional Targets to date
Design and Functional Targets to date [message #562820] Mon, 09 May 2005 16:58
Andrew Geraghty is currently offline Andrew GeraghtyFriend
Messages: 30
Registered: July 2009
The purpose of this document is to outline design and functional targets
identified to help drive the web site architecture and planning phase of
project phoenix. The following targets are as related to the discovery
process thus far: the established project objectives, audience personas,
benchmark analysis discussions and content audit. This is the initial draft
to allow for comments and discussion.

Conceptual Information Architecture
This initial stab at the first level of the sites information architecture
comes out of a card sorting exercise. It serves to provide a convenient way
to segment design and functional targets into logical sections. See attached
PDF for and enhanced view.

Design & Functional Targets
a.. a new site information architecture that provides clear categorization
of content
b.. unambiguous and quick access to desired information
c.. contextual linking and provisioning of information throughout the site
d.. consistent vocabulary used for links and menus throughout the site
that meets the need of a broad range of parishioners) that may or may not
employ a glossary of terms for 'non experts'
Content / Audience Specific Portlets
a.. creation of content specific portlets (e.g. news, featured 'community
specific' downloads, featured collaborations/discussions, featured
technologies, featured tasks)
b.. creation of audience specific resource portlets (i.e. New Visitors,
Users, Committers, Contributors, Plug In Developers, Members)
a.. DHTML menus (either cascading or rollover style), must be handicap
b.. employ content tabs for longer content sections (i.e. about the
c.. scrollable lists of content (e.g. articles and news portlets)

Eclipse Knowledge Base

a.. creation of a centralised repository, likely database driven, to
collect and distribute data throughout the site and project
b.. the eclipse community will be solicited to contribute articles and
content to the KB

Consolidated News & Headlines Area

a.. news section for project news, community headlines & project news
b.. news items consist of a: headline, a date , one line summary and
perhaps author for easy viewing
c.. featured headlines will link to the complete article
d.. creation of scrollable news portlets to be provided as RSS feeds for
distribution throughout the site

Community Area

a.. area that build and promotes sense of community within user groups
b.. contents displayed to allow user to identify their role (who they
are); e.g. community specific portlets "resources for"
c.. opportunity to profile the "meritocratic ladder"
d.. opportunity to feature the experts and promote their work (e.g.
developers) this aligns with the Eclipse development process

Core Community Collaboration

a.. consolidation of newsgroups, mailing list and other collaboration
tools into one navigate-able section
a.. creation of discussion groups (forms) with nested navigation and
unique presentation
b.. creation of a menu system to navigate discussions
c.. creation of 'scratchpad tools' (e.g. Blogs, Wikis)

Download Area

a.. provide access to all downloads in one location
b.. access to software downloads, development tools and updates

Foundation 'About' Area

a.. aggregates Foundation content

References & Support Area

a.. access to foundation, project and inter-project support and contact
info in one place
b.. provide common point of access to all technology specific support
c.. aggregates software FAQ and training
d.. provides links to third party support

Projects Area

a.. provide common point of access to all project information including:
news, project sites, projects stats, roadmaps, lifecycle info, change
tracking and release plans

Contact Info

a.. acts as a unified directory of contacts that all pages of the site can
refer to
b.. email forms available for feedback so email can be sorted and directed
to the appropriate contact
RSS Feeds
a.. creation of RSS (RDF Site Summary) that allow community members to
read through the content they want at their convenience
b.. feeds can be integrated into project sites or even community bogs

Universal Search

a.. universally placed search
b.. recommendation - powered by google

Universal Accessible Content

a.. including: Legal & Terms of Use | Privacy | License Info | Feedback
Request | Contact

Step By Step Instructions

a.. creation of step by step how to info (e.g. Getting Started with
Eclipse: STEP 1 - download the software, STEP 2 - Install Eclipse, Step 3 -
Read the overview ..)
b.. opportunity to improve compliance and lead to happier users

Printable Versions

a.. provide printable version of content

Previous Topic:Design and Functional Targets to date
Next Topic:front page layout
Goto Forum:

Current Time: Tue Apr 23 20:13:37 GMT 2019

Powered by FUDForum. Page generated in 0.01587 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top