NGA teams needed branded, accessible SharePoint sites across many programs, on two separate classified networks. Building each site by hand was slow and left the markup, styling, and accessibility inconsistent from one site to the next.
The fix was a shared system: reusable component libraries that any site could pull from, plus a repeatable delivery process that worked within the constraints of both the high-side Classic and low-side environments.
One component system, every site.
Reusable component libraries
Built HTML and CSS component libraries implementing the USWDS and UXDS specifications, cutting per-site build time and standardizing markup across the environment.
End-to-end site delivery
Delivered 25+ sites from requirements through acceptance: configuring structures, placing web parts, applying the component styling, and handing off finished sites.
Two-network delivery
Themed the high-side Classic sites with master pages and CSS, and used JSLink for custom web-part and list rendering on the low-side SharePoint 2016 network.
I also handled day-to-day SharePoint administration across the sites: permissions governance, list and library configuration, and need-to-know access enforcement.
Standards-based, and built to reuse.
USWDS + UXDS component libraries
Reusable HTML and CSS built to the U.S. Web Design System and agency UXDS specifications, so every site inherits the same accessible, on-brand components.
Master-page & CSS theming
On the high-side Classic sites, branding and layout were driven through master pages and CSS, the tools available in that environment.
JSLink rendering (low-side)
On the low-side SharePoint 2016 network, JSLink JavaScript and CSS controlled how web parts and list views rendered.
Bootstrap layout, agency branding
Bootstrap handled responsive layout, with the USWDS and UXDS branding layered on top rather than a ground-up grid.
Consistent sites, shipped faster.
The component system standardized branding, layout, and accessibility across 25+ classified sites and cut the time it took to stand up a new one. Instead of every team reinventing the same pieces, they pulled from a shared, accessible library.
It gave NGA a repeatable way to deliver SharePoint sites that looked consistent and met accessibility standards on both classified networks.