U.S. Department of Energy - Energy Efficiency and Renewable Energy

Communication Standards and Guidelines

Process and Approvals for Development of EERE Web Sites

To ensure that all EERE Web sites have a consistent professional look, navigation, and appropriate information architecture, all Web sites being developed must go through a required review and approval process through the Office of Technology Advancement and Outreach (TAO) before being published.

Download and print the graphical, high-level overview of this process for quick reference as you work on your Web sites (PDF 385 KB). Download Adobe Reader.

Training on Managing EERE Web Projects

For in-depth training on this process, view the presentation from the January 30, 2008, Webinar on Managing EERE Web Projects (PowerPoint 976 KB).

Listen to the audio from the webinar.

Text version.

EERE Web Development Process

Once the DOE Project Lead designates the Project Team, the Team begins by reviewing the Web Guidelines on the EERE Communications Standards Web site.

Phase I — Concept Development

Careful planning and a detailed project charter will allow you to define the scope and address any technical or content issues up front.

1. Hold Kick-Off Meeting

   The DOE Project Lead and the Project Team hold a kick-off meeting to determine the following:

   • Site purpose
   • Audience
   • Project scope
   • Budget (includes budget for site maintenance)
   • Schedule
   • Roles
   • Statistics needs
   • Whether news and events database is needed
   • Any unique application needs. See the Web Applications and Databases standards.

   Important: Please notify the Web Template Coordinator of your intention to build a site as soon as possible to ensure that resources and staff will be available when you need them. The Template Coordinator will help you determine who is coding your site.

2. Write Charter

   Create and submit a project charter detailing what was decided in the kickoff meeting. Download the template and learn more about project charters.

   • Specify requirements for special applications such as databases, dynamic pages, and animations and get approval from Web site server provider. See the Web Applications and Databases standards for the requirements and approvals needed. Contact the Web Template Coordinator to discuss your special applications.
   • If you plan to design a blog to support your project, see the blog management and maintenance requirements in the EERE Blog Policy. Your project charter should reflect these requirements.

3. Identify Content

   Create a content outline or content inventory to help you identify the content for your site.

4. Create Draft Architecture

   Develop a draft of the site architecture and navigation labels for use in mockups. See Navigation and Common Terms for guidance. We recommend consulting the EERE Information Architect to help you with this step. If your project is a subsite of a Program Web site, work with the DOE Project Lead and his/her Project Team to determine how the subsite will be integrated into the Program Web site.

5. Create Graphical Mockups

   Develop graphical mockups of the home page, several second-level pages, and a subsite page. All sites will go into one of the approved EERE Templates and the RedDot Content Management System unless otherwise authorized by the EERE Web Manager. For new sites and redesigns, work with the Web Template Coordinator to determine which template is best for your site.

6. Determine URL

   • For guidance on URLs, see standards for domains and file naming conventions and directory structure.

   • All new EERE Web sites (including conference sites) must be located on EERE's servers unless there is a specific reason justifying an alternative location. The EERE Web Manager must approve any requests for sites not located on EERE servers.

Phase II — Content

Content drives the architecture. In this phase, complete your content so you can determine the final architecture of the site.

1. Write Content

   Write the content for your Web site.

   • Follow the EERE Style Guide
   • See the Web Content Guidelines and use the to ensure that your content meets the standards for elements such as headers, intro text, subheaders, and photo captions and alt text.

2. Optimize Content

   Optimize your content for search engine ranking. See overview or contact the EERE Search Specialist for additional help.

3. Select Images and Documents

   Select any charts, graphs, photos, PDFs, or Word documents that will be included in the center content. Format according to standards for graphics and native files.

4. Finalize Architecture

   Develop final architecture and navigation labels based on final content.

Phase III — Production

Below are the basic steps for coding and site production.

1. Create Graphics and Prepare for Production

   • Determine whether NREL, EES, or contractor creates navigation and header graphics with the Web Template Coordinator. Develop graphics per graphic guidelines.

2. Prepare Content for Coding

   • If EES is coding your site, request EES requirements prior to providing content and graphics.

3. Code the Site

   • Determine with the Web Template Coordinator whether NREL, EES, or the contractor codes site.
   • Use the QA Checklist to ensure the site meets EERE technical standards.

Phase IV — Approval and Site Publishing

When coding is completed, contact the Web Template Coordinator to schedule QAs and reviews and make final changes before sending a site live.

1. Schedule QAs

   Schedule a Quality Assessment (QA) review of code and content with the Web Template Coordinator and content reviewers (allow 5 business days for QA reviews).

   • Technical
   • Template
   • Content (Content provider)
   • Search/Optimization

2. Make Changes

   Make changes based on the results of QAs.

3. Coordinate Pre Go-Live Tasks

   • Notify the Web Template Coordinator of any necessary bookmark notices or redirects (as needed)
   • Determine a go-live date.

4. Program Review

   Have DOE review the site. Make changes based on their feedback.

Phase V — Maintenance and Ongoing Refinements

Maintenance of your site includes keeping content current, tracking Web site statistics, assessing user feedback, and planning for future changes.

1. Write a Maintenance Plan

   Maintenance plans must be submitted for all sites and subsites. Download the template and learn more about maintenance plans.

2. Consider Further Site Analysis

   Usability testing and content analysis are valuable tools that can help you refine and improve your sites.

   • Usability testing can help you refine a site's information architecture and navigation
   • Content analysis can help you identify content gaps, duplication, and other areas for improvement.

3. Stay Informed

   The EERE Web Standards are regularly updated to meet the changing needs of the EERE Web community. New hardware and software technologies may also be implemented for the EERE Web site as needed. Subscribe to receive updates check the Communication Standards Blog to stay apprised of the latest updates.