EERE Web Standardization: The Story Behind EERE’s First Enterprise Web Template Part 1 Interlab Nov. 5, 2003 Menlo Park, CA Heidi Rex and Shauna Fjeld, NREL
EERE Web Standardization: The Story Behind EERE’s First Enterprise Web Template Part 1 Interlab Nov. 5, 2003 Menlo Park, CA Heidi Rex and Shauna Fjeld,
Dec 22, 2015
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
EERE Web Standardization: The Story Behind EERE’s First Enterprise Web Template
Part 1
Interlab Nov. 5, 2003
Menlo Park, CA
Heidi Rex and Shauna Fjeld, NREL
OutlineScopeManagement Buy-InStandardization GroundworkStandardization ImplementationProcessCommunicating the DecreeImpacts of the Project
ScopeEERE’s Web site was inconsistent and fragmented, and
NREL’s Web team had the solution: standardization.
This team was charged with developing the structure and process that is envisioned to change over 15,000 EERE Web site pages.
Management Buy-InTiming is everything
E-Government Strategy – 2/2002
EERE reorganization – 4/2002
Quote from OMB – 9/2002
OMB article
Standardization GroundworkBranding
Common terminology/navigation
Standardization GroundworkBranding
– Consistent corporate image
Standardization GroundworkBranding– Needed prioritization on what to brand
Example: DOEEEREOffice of Weatherization and Intergovernmental ProgramsState Energy ProgramConservation Update – Newsletter
Standardization GroundworkBranding
– Branding benchmark study
Standardization GroundworkBranding:
Benchmarking study offered three branding models Model 1 – Master brand
EPAModel 2 – Integrated brandingMicrosoftModel 3 – Sub brandDiscovery
Standardization GroundworkCommon terminologyInformation architect perspective
– Common elements can create a more satisfying user experience
– Common navigation and terminology should be used in large, complex Web sites
No common terminologyUser?
Potential
Business
Partner >
Site A
RFPs
Site B
Contracting
Opportunities
Site C
Proposals
Site D
Our
Solicitations
Site E
Contracts &
Proposals
With common terminologyUser?
University
Researcher >
Media
Person >
Investor >
Site A
RFPs
Late-breaking Technology News
Technology
Road Map
Site B
RFPs
Late-breaking Technology News
Technology
Road Map
Site C
RFPs
Late-breaking Technology News
Technology
Road Map
Site D
RFPs
Late-breaking Technology News
Technology
Road Map
Site E
RFPs
Late-breaking Technology News
Technology
Road Map
Standardization Implementation• Technical issues – will be covered in Part II• Mock up • Template today
– FreedomCAR & Vehicle Technologies Program
Solar Key
Standardization Implementation• Consistent domain and file naming conventions• Quality assurance checklist• Standards philosophy:
– Standards are created by a committee– We take extra pains to explain the “why,” the context,
and the reasons for the standards, as much as possible
• Standards and Guidelines Web site
Process• Without a process, template and guidelines will not
work
• GE Web style guide– Professional style guide– Poor execution– Guidelines gone bad
Communicating the EdictEERE Standards and Guidelines list serve• List serve gives updates to the standards and announces
new sites going live, new rules, and new regulations• Now have 150 people on the list• Effective communication tool
Impacts of the ProjectAll contractors and laboratories that support EERE can use
the template, and EERE corporate can still be assured: – Its brand is being maintained– Its sites are accessible and 508-compliant– Its sites are useable across the organization
Impacts of the ProjectThis project separates the content from the delivery mechanism – efficient because
people who know the content do not need to know how to code html pages.
This standardization with consistent corporate image, common terminology and naming conventions, and the new process have set EERE up for a content management system.
Related Documents
