SSDS Plone Meeting
Plone
1. Why?
Corporate Strategy
UoL moving all website into the Plone System
User Friendly
Student
Design a website with immediacy of information is of the highest importance
Staff
Use a web system that doesn't require specialist skills to make web content. 'Anybody' can write web content
Website Redesign
A chance to rethink website
2. Plone
- Content Mangement System
- Web 2.0 ethos
3. Design
Appearance
- Main body of page
- navigation
- Portlets
- SLC Template
- The Future: Plone 3
Structure
All SSDS sites will be designed around a set structure. This will give users a sense of familiarity.
4. Plone Content Features
Pages
- For written content
- HTML Based - Fast Loading
- Insert images
- Advanced Content
Forms
- Used for users to send information directly to you from the Website - Contact Us
- Feedback
- Suggestions
- Booking
Events
- Schedule events through website, which automatically updates.
Blogs
- Used as a News Reel
- RSS
Smart Content
- Content can be filtered based on criteria e.g Word in title, or a type of content
- Saves having to produce large number of webpages
- Can be used to contextualise content
Locked Down Content/Intranet
- Content can be kept private to select users
Permission
- Owner/Manager
- Editor/Member
- Reader
- Public
5. SSDS Objectives, Plans and Procedures
Objectives
- To have a fully integrated website, linking all services together, sharing web content
- The website needs to be consistent in structure and appearance across all services
- The opportunity for web content to grow as when needed and is future proofed.
Plans
- What do we want to put online...everything?
- Present equal opportunities to all student Campus or DL.
- Have information where student will look for it.
Procedures
- New Content
- Proof reading
- Recording changes to sturcture
- Permission Tracking
- Back Up
![[The University of Leicester]](unilogo.gif)


