Closed torrin47 closed 7 years ago
Do not simply copy HTML code generated by the Drupal WebCMS application. Your look and feel will break within 30 days. If you have an application, test the standalone template on your staging server. In the standalone template, you'll also note links to a variety of assets on the www.epa.gov domain, like CSS, images, and JS files; please do not remove these. In this regard, this template is no different from Templates 3 and 4, which you may have used in the past. This template is different, however, in that it is responsive, meaning the layout changes depending on the size of your screen. How that affects your application and the HTML it outputs is unknown and should be part of your testing. It's also different because the number of changes to the HTML will likely be more significant and frequent than the changes we've made to Templates 3 and 4. One additional difference: the standalone template does not have the menu dropdowns. Nor does it have the search autosuggestion functionality. We redesigned the standalone template by removing the dropdown menus because they interfered with some applications. Both of these changes make the standalone template more lightweight and prevent code conflict with your application code. Here's a high-level overview of your process. You may not need to follow steps 3-4, but step 5 is required for all.
The One EPA Web Team will determine on a case-by-case basis how much leeway applications will have regarding styling. We recognize that applications may have different needs than our "static" content. Standalone applications are not microsites and are not bound by ALL requirements that apply to microsites. Some standards will apply in all instances: Best practices must always be used, so even if there isn’t a sidebar, there always needs to be clear navigation. Content must always be written for the web. Tabs should not wrap on to a second line. Link standards are the same. Etc. etc. However, some standards that apply to microsites may not apply to standalone apps. For example, many applications may need to be the full width of the screen. Requiring a left sidebar would only narrow the space in which the information can be presented. Sometimes that extra space is necessary, and the nav is better presented in ways other than a left sidebar. The EIC for a standalone application should show the One EPA Web Team wireframes before he or she proceeds, to ensure that we don’t get to the end-stage of development, when review happens, and insist on a feature that should have been incorporated from the beginning. EPA online applications that present information via a web interface (e.g., to the screen) should:
For the footer, in the Discover column, below "Privacy and Security" add two links: System of Registries http://www.epa.gov/sor and National Geospatial Program http://www.epa.gov/geospatial we don't need to preserve the rest of the text or the other links.
Guidance for the EPA Template is here (inaccessible off the EPA LAN, basic content in comment below): https://www.epa.gov/webguide/applications-and-one-epa-web-template The HTML for the template is this page: https://www.epa.gov/sites/all/libraries/template2/standalone.html The main CSS file is here: https://www.epa.gov/sites/all/libraries/template/s.css and the main JS file is here: https://www.epa.gov/sites/all/libraries/template/js.js
We do not expect this to be a quick, easy, or seamless conversion, but getting it cleaned up and polished will mean a great deal to OEI Management and the user community.