...
- Information architecture and website design
- Creation of a new identity and visual identity
- Removal of dash in JA-SIG
- JA-SIG no longer stands for Java Architectures, as we move beyond Java to more general open source and collaboration in higher education IT
- Design and development of a brand and logos
- Logo for JA-SIG itself
- Logo for JA-SIG Member Institution
- Logo for JA-SIG Commercial Affiliate
- Migration of existing website content into a new CMS demonstrating the new brand, logos, and especially information architecture
- ja-sig.org and uPortal.org [See comment -Jonathan]
- Implementation of a Contact Us page / section including a web form for sending email. This to be initially implemented to email the Board, who will then route the messages where they really need to go.
...
- Content in the Confluence wiki. While small units of content may tactically be pulled up to the website layer (committer listings, e.g.), vast swaths of Confluence wiki content (e.g., the uPortal manual) are not to be included in this effort
- the CAS website (http://www.ja-sig.org/products/cas/). While the CAS website would benefit from additional attention and might welcome migration off of Hypercontent, since it is better architected and designed, the margin of benefit to be gained in revisiting it now is thinner. The idea is to execute on ja-sig.org and uportal.org and then re-assess. [See comment -Jonathan]
- Extending JA-SIG branding to web applications and sites other than the managed content specifically to be architected here. Creation of graphics and branding that can be used to apply this branding elsewhere is in-scope, but to control scope creep, actual execution of that branding is to either be undertaken on the side as a volunteer effort, or to be subsequently tacked after this scope of work has succeeded.