This is a starter page to collect requirements or content which should be included as part of the web presence redesign effort.
Requirements for jasig.org site
See child page treating jasig.org requirements.
Requirements for uportal.org site
See child page treating uPortal.org.
Other requirements
I am skeptical of a need for automatic aggregation from events from other sites. If editing and entering news items is easy enough or well-managed enough, this might be implemented by specific, site-appropriate versions of these news items from elsewhere being included in the news on a particular site. I favor targeted, well-crafted communication rather than syndication of generic communication and suggest that an automatic aggregation requirement is partially a phantom requirement, deriving from the very poor experience we've had with news in HyperContent.
Once one has heroically gotten any of the sites to manage to include a news item, one wishes the other sites would automatically syndicate it, since it's not cheap, easy, or fun to go manually enter it in the next site. If it were cheap, easy, and fun to enter news items, and to even edit them to be audience-appropriate, then it may become very possible to put a uportal-flavored version of a generic conference announcement on the uportal.org site and a more general version of that announcement on ja-sig.org, rather than feeling the need to present identical news items in multiple places. Likewise, a uPortal release announcement on uportal.org might assume one already knows what uPortal is and focus on what makes the new release different, whereas a uPortal release announcement on ja-sig.org might focus less on the details and more on what uPortal is and the general message of project release progress.
So yes, absolutely, generic and specific news items are a requirement, but I wouldn't want to presume some particular automation need.
I think the content for these pages is the same as Jonathan outlined for the jasig.org site - i.e., identity, brand, information, marketing, communication outside JASIG, easy answers to FAQ.
Also, if the intended audience is users/potential users, maybe something about "Why uPortal?" What are the benefits that implementing institutions have had - so that someone contemplating implementation can understand why they might want to do utilize uPortal? Are there some "best practices/best usages" out there that might spur "potential use" thoughts among those who visit the web page?
Finally, the look/design really needs to be very user friendly and easy to navigate. If a potential user's first impression is that the Web site is difficult, they may infer the same about uPortal and not pursue it. (The old adage you never get a second chance to make a first impression.)
Updated by Jim Helwig
Jun 10, 2008 11:27
A few comments regarding the JASIG site:
A few comments regarding the uPortal site:
Jim, I've merged your ideas about registration and about listing of uPortal deployments into the uPortal.org requirements.
Jim, I've merged your idea about a CIO-targeted area of the jasig.org website into JASIG.org Requirements.