Fusp website proposal short
-
Upload
alexander-brown -
Category
Technology
-
view
539 -
download
0
description
Transcript of Fusp website proposal short
The New FUSP WebsiteEmpowering YOU
Alexander P. Brown
and the Website Committee
Agenda
• The Problem: Keeping website up to date, Newsletter editor burnout, Website not best for browsing.
• The Solution: Common Information System
• Demo new Website
• Plan for Finishing Content Updates
Problem: Publications
• Publications:– Monthly Newsletter (Chris B.)– Weekly Bulletin / Order of Service (Louise)– Website (Alex)– Website Calendar (Louise)– Archives– Internal contact lists, Meeting agendas, policy
• Website is primarily static, newsletter & order of service section updated monthly
Problem: Information Sources
• Information Sources:– Committee Chairs– Minister– Director RE– Committee Members– Congregation Members– UUA / District Newsletters, Websites
• Communicated Via different methods and organized.– Emails– Paper to Folder – Snail Mail
Newsletter /Order of Service /
Web Calendar
Chris Receivesand Categorizes
Chris / Louise Edit& Format
Publications
Alex Reformats for Web
Memberswith Information
to share
Problem: The Current Process
Duplication of Effort
Bottlenecks & Burnout
P.N.S.D.Alex,
Thanks for the gentle reminder.
A funny family joke has evolved over the last four months:
The printed newsletter arrives, and invariably someone says, "Hey, your newsletter arrived! Do you want to see it?"
The joke is that my family knows quite well by now that the LAST thing I want to see after a week of working on editing the blasted thing is the actual newsletter. After 20+ hours, I am not only dreading seeing the thing ever again, but also dreading the certainty that if I do read the final printed version, I will find yet another mistake that I missed the first dozen times I read through it!
I say all that by way of explanation. I've been extremely tardy in sending you your copy each month.
Chalk it up to PNSD (Post-newsletter-stress-disorder).
I'll try to send you your copy just before I collapse this month!
- CB
Problem: Static Website
• Static content does not draw members to site
• Newsletter format not best format for web browsing
• Website primarily for visitors, not members
• How do we open up site for members?
Proposed Solution
• The new website is a tool to help us manage this information so that:– Content is not lost, – Content gets editing attention (+double-check) – Content is forwarded to appropriate
publications– Website is up-to-date & dynamic– Congregational notices are on website, but
not public (private)
A Tale of Two Websites
• Public Website – Organized to appeal to new visitors.. Who are
we? What do we do? How can I get involved?– No longer static, publicly advertised events
• “Friends of Fusp” Website– Members and “friends” register / log-in– Organized by Committee – Contains Private Committee and
Congregational info (Meeting minutes, docs)
Collaborative Content Management
Email Email
Karin / Louise / Chris Receivesand Categorizes
Newsletter /Order of ServiceChris / Louise
FormatPublications
Publishers ReviewArticle and Authorize
for Publication
Snapshot ofpublication
outline extracted
Article Formatted,Categorized and
Submitted onWebsite
Article Appears onWebsite
“Authorized” Memberswith Information
to share
Common Myths
• New system does not require you to get the newsletter content online.
• New system does not require everyone to know how to update the website.
• People will not be posting inappropriate information to website.
New Information Flow
• Committees each have a section of Website under “Friends of FUSP”
• Each committee decides on the – layout / modules / tabs for their section.– Destination publications for each module
(Newsletter/Order of Service/Website)
• Secretary for each committee updates the website or forwards updates to Web Editor (Karin G.) monthly.
Guinea Pig: Green Sanctuary
• Heather Brown assigned “Editor” Role for Green Sanctuary Page
• Heather Updates Content
• Content Appears on Public Website– News– Social Action
• Chris downloads content for Newsletter @ e-content submission deadline
Publishing Demo
Joe Worship Committee Secretary needs to add description of upcoming sermon1. Login
2. Switch to staging view of content to edit
3. Add & submit article describing sermon
4. Karin receives notification and Approves
5. Karin Publishes
6. Chris Publishes in Newsletter
Look and Feel
• Public Web Site– Should reflect color and diversity of
membership– Pictures, Pictures, Pictures – Clean and easy to read, not cluttered
• “Friends of Fusp”– Organized by Committee structure– Owned by each committee
• Look and Feel can be changed (skins)
Go-Live Timeframe
• Committees Identify Corrections / Updates to Public Site (by February 1)
• New site goes live Feb 1st • Committees appoint a “Secretary” or Editor to
update site (by Feb 1st)• Committees Identify what they want on the
“Friends of FUSP” site. (by Feb 12th)• February is still old process for Newsletter • Can we do March with new process? • Newsletter content deadlines remain the same.
Summary
• Internet-connected Web of Existence
• Register on the Site
• Appoint your editor for your press releases (fight PNSD)
• Help us fill out existing Public and Committee sites. (Pictures!)
More Information
• QUESTIONS?
• Current Prototype can be found from link on current FUSP website… http://www.fusp.org/desktopdefault.aspx