2 This is a place holder for notes on the redesign of the openafs.org website.
4 In particular, the new site must be designed to be accessible to various groups of users who have very different needs. Here is a [[site outline|NewSiteOutline]] which should follow these requirements:
6 1. [[OpenAFS]] administrators
7 1. easy access to the "best" binaries (and perhaps source) for their server and client platforms
8 2. easy access to documentation (man pages, admin guide, wiki, etc.)
11 2. [[OpenAFS]] client end users
12 1. easy access to the "best" binaries for their client OS (perhaps auto-detected)
13 2. easy access to end user documentation
16 3. Senior managers and architects (CTO,CIO,...) of organizations performing long term planning for their organization who have doubts about the future and applicability of [[OpenAFS]] for their storage solutions OR who might want to fund development efforts
17 1. case studies / success stories
18 2. architectural white papers
19 3. development road map
21 4. Random individuals who want to know what this AFS thing is
23 1. Source code downloads
28 6. Development mailing lists
29 6. Governance and Communications