Process and Approvals for Development of EERE Web Sites
Here you'll find the requirements and suggested process for developing Web projects on EERE. 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, with the guidance of the Project Review Team, before being published.
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.
-
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.
-
Complete the Project Information Form
For every new project, you will first need to fill out the project information form (MS Word 80 KB). This form provides a basic overview of what type of project you are planning. When it's complete, send it to the Project Review Team Facilitator.
- If you have never worked with the Project Review Team before, you will need to watch a short PowerPoint presentation about how to work with the Project Review Team. The Project Review Team Facilitator will organize a time for this presentation, if you require it.
- Justify any Non-Standard Elements: The form includes a list of all non-standard elements. You must write a justification for every non-standard element you want for your site. If you do not understand how to justify some of these, bring your questions to your meeting with the Project Review Team.
-
Meet with the Project Review Team
The Project Review Team Facilitator will arrange your project team's first meeting with the project review team. During this meeting you will discuss your plans for the project.
-
Write Charter
After meeting with the Project Review Team you will have enough information to develop your charter. Create and submit a project charter detailing what was decided in the meeting. Download the template and learn more about project charters.
- 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.
-
Develop Task List
The Project Review Team Facilitator will provide you with a list of tasks required to complete your project. Review this list and fill in a schedule.
-
Meet with the Project Review Team to review your Charter, Task List, and Schedule
- Send the completed charter, task list, and schedule to the Project Review Team in advance of the meeting.
- These items will be discussed during the meeting.
-
Identify Content
Create a content outline or content inventory to help you identify the content for your site.
-
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 Web Coordinator and the Program's Lead Contractor to determine how the subsite will be integrated into the Program Web site.
-
Create Graphical Mockups or Wireframes
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 OpenText 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.
Review and Approval Checkpoint
Ensure you have completed the following tasks before moving onto Phase II:
- Schedule monthly status meetings with the Project Review Team. These meetings should last throughout the entirety of the project. The Project Review Team Facilitator can help you arrange these meetings.
- The following elements must be approved by the Project Review Team before the project team begins production (see Phase 1, Steps 2 and 4)
- Project charter
- URL
- Task list
- Schedule
- Justification for non-standard elements
- Special application requirements.
- Your initial IA will need to be approved by the Web Template Coordinator.
Phase II — Content
Content drives the architecture. In this phase, complete your content so you can determine the final architecture of the site.
-
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.
-
Optimize Content
Optimize your content for search engine ranking. See overview or contact the EERE Search Specialist for additional help.
-
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.
-
Finalize Architecture
Develop final architecture and navigation labels based on final content.
Review and Approval Checkpoint
Ensure the following tasks are completed before moving onto Phase III:
- Submit wireframes or mockups to the Web Template Coordinator, who will coordinate approval.
- Receive approval for your final site architecture from the Web Template Coordinator.
Phase III — Production
Below are the basic steps for coding and site production.
-
Create Graphics and Prepare for Production
- Speak with your lead contractor to determine whether NREL, EES, or contractor creates navigation and header graphics. Develop graphics per graphic guidelines.
-
Prepare Content for Coding
- If EES is coding your site, refer to your EES Technical Contact for requirements prior to providing content and graphics.
-
Code the Site
- The Web Coordinator and Project Lead will determine whether NREL, EES, or the contractor will code the site.
- Use the QA Checklist to ensure the site meets EERE technical standards.
Review and Approval Checkpoint
Ensure the following tasks are completed before moving onto Phase IV:
- Perform a self-assessment on the coding using the QA Checklist.
- For applications not hosted on the central EERE infrastructure, ensure applications undergo a security scan as detailed on the Web Applications and Databases page.
Phase IV — Approval and Site Publishing
When coding is completed, your site or application will need to go through a QA and program review before it goes live.
-
Schedule QAs
Work with your EES Technical Contact to schedule the following QAs (allow 5 business days for QA reviews).
- Technical
- Template
- Content (completed by content provider)
- Search/Optimization
-
Make Changes
Make changes based on the results of QAs.
-
Coordinate Pre Go-Live Tasks
- Notify the EES Technical Contact of any necessary bookmark notices or redirects (as needed)
- Determine a go-live date and verify it with your EES Technical Contact.
-
Program Review
Have DOE review the site. Make changes based on their feedback.
Review and Approval Checkpoint
Ensure the following tasks are completed before moving onto Phase V:
- Ensure that all critical changes identified in QA have been made.
- Obtain review and approval from DOE reviewers.
- Obtain approval to go live through the Project Review Team, who will coordinate all approvals with the EERE Web Manager.
- Go live with site.
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.
-
Write a Maintenance Plan
Maintenance plans must be submitted for all sites and subsites. Download the template and learn more about maintenance plans.
-
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.
-
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.
Review and Approval Checkpoint
Submit your maintenance plan to the DOE Project Lead, the EERE Web Manager, and the Web Corporate Content Coordinator.




















