Web Standard: Hub Sites
Note
All EPA public and internal content pages and web applications are required to follow this standard.
ArcGIS Hub Sites are ArcGIS Online-hosted applications used to manage, curate, and share geospatial data, mapping applications, and other forms of geographic information.
Content Requirements
- Hub Sites must:
- Adhere to processes outlined in the StoryMap Guidance and Publication Requirements, including:
- required review for public-facing content at two stages: before work begins (concept review) and when the product is near final (final review);
- Public Affairs Director or Communications Director review and approval for Hub Sites shared at the organization level on EPA intranet sites;
- Adhere to processes outlined in the StoryMap Guidance and Publication Requirements, including:
- Include ArcGIS Online-hosted content with a substantive geographic component that enhances, or compliments content provided in traditional web environments (e.g., content on epa.gov);
- Substantive geographic component include interactive web maps that are about EPA content and data that allow users to explore the geographical data.
- (Substantive geographic component includes more than a single point on a map to a well known location, e.g. Washington DC or information that could be easily included with an image.)
- All Hub sites and geographical content must be related.
- Contain data that are stored, cataloged, or referenced as required by the National Geospatial Data Procedure;
- Implement Agency guidance on map design and cartography to maximize digital accessibility (e.g., accessible color palettes, flexible sorting, alternative text, etc.).
- Include the Agency’s Web analytics code to ensure that it is compliant with the Digital Analytics Program (DAP).To the extent possible, adhere to the EPA Look and Feel Template (including required footer links), EPA Web Standards (including the Writing for the Web Standard) and EPA Style Guide Pattern Lab.
About this Standard
Original effective date: 08/09/2023
Last approved on: 08/09/2023
Web Council review by: 08/09/2026 (or earlier if deemed necessary by the Web Council)