# Presentation: 735206

## Code 400 Webmasters Quarterly Review February 12, 2004

***Code 400 Webmasters Quarterly Review****** February 12, 2004***

## Agenda - Why are we here today? 

**Discuss Agency initiatives, GSFC Web Council & Webmasters Group Activities and Planning. (Emma)**
**Discuss Code 400’s response to meet requirements, best practices, guidance and how to pass compliance review. (Cecilia)**
**Demo how we (NASA/GSFC/400) are walking the talk. What it looks like in the real world. (Emma)**
**Where do we go from here?  (All)**

***Cecilia Czarnecki***

***Agenda - Why are we here today? ***

## Introduction

**About the Webmasters Group & the Web Council**
**Accomplishments**
**What are the pressures we face? (The big picture)**
**Plans for the coming year**
**What you can do**

***Emma Antunes***

## About the Webmasters Group & the Web Council

**Webmasters Group **
- Started in 1996, chartered by CIO
- User group, focused on community education
- Monthly presentations, brown bags
- Web site:
- _[http://webmaster.gsfc.nasa.gov/](http://webmaster.gsfc.nasa.gov/)_
- 2 mailing lists:
- _[www-announce@majordomo.gsfc.nasa.gov](mailto:www-announce@majordomo.gsfc.nasa.gov)_
- _[www@majordomo.gsfc.nasa.gov](mailto:www@majordomo.gsfc.nasa.gov)_
**Web Council**
- Started in 2002, chartered by CIO
- Management group, focused on policy and governance
- Members are representatives from each directorate

***Emma Antunes***

## Accomplishments

**Webmasters Group Accomplishments**
- Presentations on:
- NASA Look & Feel
- Section 508
- Knowledge Management
- Writing for the Web
- XML
**Web Council Accomplishments**
- Registration of over 1300 public web sites
- Answered 2 of the big 3 questions (third answer coming soon!)
- What sites do we have?
- Who are our webmasters?
- Are our sites in compliance with Federal law?
- Clean up of the port 80 list
- Internal Search Engine Business Case

***Emma Antunes***

## What are the pressures we face? 

**A whole lot of rules and regulations!**

***Emma Antunes***

## WWW Regulations and Policies

**Federal Legislation**
- Privacy Act of 1974, as amended
- Computer Security Act of 1987
- Paperwork Reduction Act of 1995
- Clinger-Cohen Act of 1996
- Electronic Freedom of Information Act (EFOIA) Amendments of 1996
- Section 508 of the Rehabilitation Act Amendments of 1998
- Children's On-line Privacy Protection Act of 1998 (COPPA)
- Government Paperwork Elimination Act of 1998
- Section 646, Protection Of Citizens’ Privacy On Federal Web Sites, Treasury And General Government Appropriations Act, 2001 (P.L. 106-554, December 21, 2000)
- E-Government Act of 2002
- Homeland Security Act of 2002
- Executive Order 12862, Setting Customer Service Standards
- Executive Order 13011, Federal Information Technology
- Executive Order 13166, Improving Access to Services for Persons With Limited English Proficiency
**OMB/Dept. of State/Dept. of Commerce**
- Privacy Policies and Data Collection on Federal Web Sites (OMB “Cookie” memo)
- Privacy Policies on Federal Web Sites, OMB, June 2 1999
- OMB Circular No. A-130, Management of Federal Information Resources.
- U.S. Export Administration Regulations (EAR)
- International Traffic in Arms Regulations (ITAR)
- Memorandum for Chief Information Officers and Federal Webmasters: Top Privacy Principles for Federal Web Sites (GSA)
- OMB Information Quality Guidelines (October 1, 2002)

**NASA HQ**
- NPD 1382.17, Privacy Act - Internal NASA Direction in Furtherance of NASA Regulations
- NPD 1440.6, NASA Records Management.
- NPG 1441.1, NASA Records Retention Schedules.
- NPD 2190.1, Procedures and Guidelines for the NASA Export Control Program
- NPG 2190.1, Procedures and Guidelines for the NASA Export Control Program
- NPD2800.1, Management of Information Technology
- NPG2800.1, Management of Information Technology
- NPD2810.1, Security of Information Technology
- NPG2810.1, Security of Information Technology
- NPG 2200.2, Guidelines for Documentation, Approval, and Dissemination of NASA Scientific and Technical Information
- NPD 2220.5, Management of NASA Scientific and Technical Information
- Designated Internet Home Page Naming And Ownership  (CIO Executive Notice 08-95)
- NASA Public Affairs Internet Communications Policy, Oct 95
- Policy for Retention of Internet Services Server Log Files (CIO Executive Notice 23-97, based on Schedule 2, Item 13 of the NASA Records Retention Schedule,)
- Guidance on Implementation of Information Technology (IT) Security Warning Banners (CIO memo dated October 10, 1997)
- Guidance on Implementation of NASA Website Privacy Statement (CIO memo dated June 1, 1998)
- Logo Policy (Associate Administrator for Public Affairs memo dated June 2000)
- NASA Web Site Registration and Internet Policy (Dated 11/15/01)
**GSFC**
- Authorized Use of the Internet, the World Wide Web (WWW) and Related Internet Services (Center Announcement #95-02)
- GSFC Policy and Responsibilities for the Use of the World Wide Web (WWW) Technology  (Center Announcement #95-04)

***Emma Antunes***

**Notes:**
Some of these regulation involve criminal liability for noncompliance
There’s a lot of risk for us in not paying attention to these

## What are the pressures we face? (The big picture)

**Public**
- Increased expectations for the reliability, usability, and quality of NASA sites
**Federal**
- Focus on privacy, security, accessibility, and e-government
- Service to citizens
- Do more for less (OMB)
**Agency**
- OneNASA
- Common look and feel
- Focus on content, not design
- Greater attention to web management
- Push to centralize (both content & infrastructure)
- NASA Web Managers charter to be approved soon

***Emma Antunes***

**Notes:**
Public - risk to our reputation (every web site is the public face of NASA)
Potential litigation

Web management is important - we need to look at managing a web project the same as any other software project
Running a web site is a professional skill
Can 1/4 time webmasters keep up? A code 900 review of their major web sites found that those with less than 1 FTE were not effective. Shouldn’t we have engineers and scientists provide content and do their jobs, rather than be part-time webmasters?

## Plans for the coming year

**Develop Strategic Plan for Goddard’s web environment**
- Goal
- Create a vision for how we want Goddard’s web environment to be in the future
- Common Themes
- Greater attention to project management; professional approach to web development
- Web shop to go to for services, webmasters, development support
- Review/Approval of Web Sites
- Resources for Webmasters (Tools, training, templates, testing)
- Support for centralization where it’s appropriate
**Review all public sites for compliance with NASA Policy and Federal Law**
- Trust, but verify.
**Provide more support for Section 508 Testing & Compliance**
- LIFT Machine pilot: $6K  Full version: $50K
**Proceed with Internal Search Engine Evaluation**
- Google for Goddard: $220K/2 years
**Encourage use of common NASA look & feel**** **

***Emma Antunes***

**Notes:**
Having a strategic plan allows us to take advantage of opportunities as they arise, to understand the impact of agency & federal initiaitves, and to work towards a better web environment. The council currently is made of volunteers and doesn’t have its own budget. I’d like to see that change in the future, as web management gets more attention 

Manage your web site as you would any other project. What is its projected lifecycle? Cost? Benefit? Is there a better way to do it? How successful is your message?

## What you can do

***What you can do***

**Be active in the webmasters community**** **
- Join the mailing lists and come to our presentations. The next presentation is Feb 25, on Using XML for Web Content.
**Become familiar with web policy**
**Manage your web site as you would any other project. What is its projected lifecycle? Cost? Benefit? Is there a better way to do it? How successful is your message?**
**Take a professional attitude towards your web site; it’s the public face of NASA**
**Use the NASA Look & Feel **
**Separate content from presentation**

***Emma Antunes***

## Use the NASA Look & Feel

**Why?**
- Achieve and maintain a high standard for content presentation
- Provide a consistent user experience with improved navigation
- Strengthen NASA brand and make easy to identify an official NASA site
**Consistent but Flexible**
- Different levels of “Affinity”
- Some areas are more fixed
- Site navigation concept
- Fonts
- Header, footer, background color
- Some areas are more flexible
- Information architecture
- Section navigation
- Inside layout
**Portal Style Guideline Specifications & other Portal info**
- http://www.hq.nasa.gov/pao/portal/

***Emma Antunes***

**Notes:**
Is it a requirement? No. Do we strongly recommend it? Yes. Management will expect you to justify why you don’t use it, not the other way around. Look at industry - it makes business sense, and it makes it easier for users to navigate and find things

295 developing an application to generate graphics, templates on the fly, so you don’t have to buy font & fireworks

## NASA & GSFC sites using the new look & feel

**NASA.gov **http://www.nasa.gov/home/index.html
**JPL **_**[http://www.](http://www.jpl.nasa.gov/index.html)**__**[jpl](http://www.jpl.nasa.gov/index.html)**__**[.](http://www.jpl.nasa.gov/index.html)**__**[nasa](http://www.jpl.nasa.gov/index.html)**__**[.gov/index.html](http://www.jpl.nasa.gov/index.html)**_
**NASA (Flash example) **_**[http://www.](http://www.nasa.gov/missions/timeline/index.html)**__**[nasa](http://www.nasa.gov/missions/timeline/index.html)**__**[.gov/missions/timeline/index.html](http://www.nasa.gov/missions/timeline/index.html)**_
**Mars **_**[http://](http://marsprogram.jpl.nasa.gov/)**__**[marsprogram](http://marsprogram.jpl.nasa.gov/)**__**[.](http://marsprogram.jpl.nasa.gov/)**__**[jpl](http://marsprogram.jpl.nasa.gov/)**__**[.](http://marsprogram.jpl.nasa.gov/)**__**[nasa](http://marsprogram.jpl.nasa.gov/)**__**[.gov/](http://marsprogram.jpl.nasa.gov/)**_
**Mars Rovers **_**[http://](http://marsrovers.jpl.nasa.gov/home/index.html)**__**[marsrovers](http://marsrovers.jpl.nasa.gov/home/index.html)**__**[.](http://marsrovers.jpl.nasa.gov/home/index.html)**__**[jpl](http://marsrovers.jpl.nasa.gov/home/index.html)**__**[.](http://marsrovers.jpl.nasa.gov/home/index.html)**__**[nasa](http://marsrovers.jpl.nasa.gov/home/index.html)**__**[.gov/home/index.html](http://marsrovers.jpl.nasa.gov/home/index.html)**_
**KSC Mars site  http://www.ksc.nasa.gov/elvnew/merb/index.htm**
**Academy of Program & Project Leadership (APPL) http://appl.nasa.gov/home/**
**GSFC Webmaster **_**[http://webmasters.](http://webmasters.gsfc.nasa.gov/)**__**[gsfc](http://webmasters.gsfc.nasa.gov/)**__**[.](http://webmasters.gsfc.nasa.gov/)**__**[nasa](http://webmasters.gsfc.nasa.gov/)**__**[.gov](http://webmasters.gsfc.nasa.gov/)**_
**Code 400 current:  **_**[http://](http://fpd.gsfc.nasa.gov/index.html)**__**[fpd](http://fpd.gsfc.nasa.gov/index.html)**__**[.](http://fpd.gsfc.nasa.gov/index.html)**__**[gsfc](http://fpd.gsfc.nasa.gov/index.html)**__**[.](http://fpd.gsfc.nasa.gov/index.html)**__**[nasa](http://fpd.gsfc.nasa.gov/index.html)**__**[.gov/index.html](http://fpd.gsfc.nasa.gov/index.html)**_
**Code 400 New: **_**[http://](http://fpd-dev.gsfc.nasa.gov/code400update/index.cfm)**__**[fpd](http://fpd-dev.gsfc.nasa.gov/code400update/index.cfm)**__**[-dev.](http://fpd-dev.gsfc.nasa.gov/code400update/index.cfm)**__**[gsfc](http://fpd-dev.gsfc.nasa.gov/code400update/index.cfm)**__**[.](http://fpd-dev.gsfc.nasa.gov/code400update/index.cfm)**__**[nasa](http://fpd-dev.gsfc.nasa.gov/code400update/index.cfm)**__**[.gov/code400update/index.](http://fpd-dev.gsfc.nasa.gov/code400update/index.cfm)**__**[cfm](http://fpd-dev.gsfc.nasa.gov/code400update/index.cfm)**_
**GOES current: **_**[http://goes.](http://goes.gsfc.nasa.gov/)**__**[gsfc](http://goes.gsfc.nasa.gov/)**__**[.](http://goes.gsfc.nasa.gov/)**__**[nasa](http://goes.gsfc.nasa.gov/)**__**[.gov/](http://goes.gsfc.nasa.gov/)**_
**GSFC Goes New : **_**[http://goes2.](http://goes2.gsfc.nasa.gov/)**__**[gsfc](http://goes2.gsfc.nasa.gov/)**__**[.](http://goes2.gsfc.nasa.gov/)**__**[nasa](http://goes2.gsfc.nasa.gov/)**__**[.gov/](http://goes2.gsfc.nasa.gov/)**_** **** **
**Recruiting  (Under Development) **_**[http://webmaster.](http://webmaster.gsfc.nasa.gov/~emma/nasalook/OHRrecruitsite.jpg)**__**[gsfc](http://webmaster.gsfc.nasa.gov/~emma/nasalook/OHRrecruitsite.jpg)**__**[.](http://webmaster.gsfc.nasa.gov/~emma/nasalook/OHRrecruitsite.jpg)**__**[nasa](http://webmaster.gsfc.nasa.gov/~emma/nasalook/OHRrecruitsite.jpg)**__**[.gov/~](http://webmaster.gsfc.nasa.gov/~emma/nasalook/OHRrecruitsite.jpg)**__**[emma](http://webmaster.gsfc.nasa.gov/~emma/nasalook/OHRrecruitsite.jpg)**__**[/](http://webmaster.gsfc.nasa.gov/~emma/nasalook/OHRrecruitsite.jpg)**__**[nasalook](http://webmaster.gsfc.nasa.gov/~emma/nasalook/OHRrecruitsite.jpg)**__**[/](http://webmaster.gsfc.nasa.gov/~emma/nasalook/OHRrecruitsite.jpg)**__**[OHRrecruitsite](http://webmaster.gsfc.nasa.gov/~emma/nasalook/OHRrecruitsite.jpg)**__**[.jpg](http://webmaster.gsfc.nasa.gov/~emma/nasalook/OHRrecruitsite.jpg)**_
**CDDIS (Under Development)  **_**[http://](http://cddisa.gsfc.nasa.gov/nlf/cddis_nlf.html)**__**[cddisa](http://cddisa.gsfc.nasa.gov/nlf/cddis_nlf.html)**__**[.](http://cddisa.gsfc.nasa.gov/nlf/cddis_nlf.html)**__**[gsfc](http://cddisa.gsfc.nasa.gov/nlf/cddis_nlf.html)**__**[.](http://cddisa.gsfc.nasa.gov/nlf/cddis_nlf.html)**__**[nasa](http://cddisa.gsfc.nasa.gov/nlf/cddis_nlf.html)**__**[.gov/](http://cddisa.gsfc.nasa.gov/nlf/cddis_nlf.html)**__**[nlf](http://cddisa.gsfc.nasa.gov/nlf/cddis_nlf.html)**__**[/](http://cddisa.gsfc.nasa.gov/nlf/cddis_nlf.html)**__**[cddis](http://cddisa.gsfc.nasa.gov/nlf/cddis_nlf.html)**__**[_](http://cddisa.gsfc.nasa.gov/nlf/cddis_nlf.html)**__**[nlf](http://cddisa.gsfc.nasa.gov/nlf/cddis_nlf.html)**__**[.html](http://cddisa.gsfc.nasa.gov/nlf/cddis_nlf.html)**_
**GSFC (Under development) http://webmaster.gsfc.nasa.gov/emma/gsfc/index.html**
**Wallops http://ww3.wff.nasa.gov/wfcwf/responses.php**
**GISS Publications: http://pubs.giss.nasa.gov/**

***Emma Antunes***

## Separate Content from Presentation

**Why?**
- Supports changing technology
- Supports mandates from management w/ regard to presentation
**How?**
- XML & XSLT
- Server Side Includes
- Templates
- CSS

***Emma Antunes***

## What’s in it for us?

- Provides ”visual affinity” across 400, within Goddard and across NASA - Strengthens NASA Website “brand”
- Provides a professional, polished interface
- Puts us ahead of the curve – Code 400 viewed as innovators and team players
- As early adopters, we will help steer the GSFC policies and guidelines
- Will help us to meet requirements of website reviews (internal and external)
- Web pages will be easier to develop and maintain
- Web pages will be easier to use and access to information faster due to more consistent content and navigation across organizations
**Public will have more positive view of NASA/GSFC/Projects Directorate**

***Cecilia Czarnecki ***

## What can you do now?

**Review  existing sites for short-term usability and compliance fixes. Look for:**
- Inconsistent information and navigation
- Internal information on external pages and vice versa
- Organization-centric sites – this is confusing for non-NASA/Goddard users
- Out of date, conflicting information including launch dates, contact information, news items, etc.
- Responsible NASA officials and other required information not consistently or correctly presented
- Outdated content and designs, inappropriate content, broken links, 508 non-compliance
- Don’t know when you have been directed to a non-NASA site – no exit message presented
- Difficult to know if site is an ‘official site’
- Professionalism – consider using OneNASA banners for quick turn around solution
- Security Issues – Work with your Systems Administrators and CSO’s to reduce web vulnerabilities - http://www.owasp.org/documentation/topten - Center Security Recommended Site

***Cecilia Czarnecki***

## Participate in OneNASA Look and Feel Workshop – sign up sheets are on the table outside the door
Attend GSFC Web masters meetings hosted by Emma
Go to webmaster@gsfc.nasa.gov to review policies and regulations
Begin to develop a project plan for incorporating OneNASA Look and Feel, regulations, policies/guidelines, and best practices into your websites – focusing on recommendations from the GSFC and Code 400 Web Strategic Plans
Volunteer (or risk being recruited) to serve on Code 400 Web Council
Volunteer to assist in development of Code 400 Web Strategic Plan 
Meet with your IT and  Program/Project Management to generate support and promote these initiatives, especially to support implementation of GSFC and code 400 Web Strategic Plan.

**Attend GSFC Web masters meetings hosted by Emma**
**Go to webmaster@gsfc.nasa.gov to review policies and regulations**
**Begin to develop a project plan for incorporating OneNASA Look and Feel, regulations, policies/guidelines, and best practices into your websites – focusing on recommendations from the GSFC and Code 400 Web Strategic Plans**
**Volunteer (or risk being recruited) to serve on Code 400 Web Council**
**Volunteer to assist in development of Code 400 Web Strategic Plan **
**Meet with your IT and  Program/Project Management to generate support and promote these initiatives, especially to support implementation of GSFC and code 400 Web Strategic Plan.**

***What else can you do ?***

***Cecilia Czarnecki ***

## Web Initiativesand Code 400 Management 

**Code 400 Senior Management Supports These Efforts**
**Met with Peg Luce and Jim Greaves on 2/2/2004 -  enthusiastic support for implementing initiatives**
**Will brief Dolly and Krista 2/19/2004 to solidify Senior Management Support for Strategic Planning effort and to promote these initiatives through Code 400 Program and Project Managers**
**Discussion, Questions & Issues?**

***Cecilia Czarnecki***