Introduction to New Web Templates: Workshop Summary
This session introduced Stony Brook University web editors to the new Modern Campus CMS department templates and outlined how sites will transition to meet the April 24, 2026 Title II WCAG 2.2 AA accessibility requirements. The goal of this project is not only compliance, but a more modern, consistent, accessible, and easier-to-maintain web experience for both visitors and editors.
View Workshop Slides Download Redirect Spreadsheet (Second Tab)
Why this is happening
The current website architecture is over a decade old and no longer supports modern accessibility, security, or usability standards. New templates rebuild the underlying code, improve mobile responsiveness, remove legacy technical debt, and introduce more flexible, accessible components while aligning with updated university branding and design patterns.
Who this applies to
This rollout applies to websites managed in Modern Campus CMS on stonybrook.edu and supported by MARCOM Web Services. Sites on stonybrookmedicine.edu or you.stonybrook.edu follow separate processes with their respective teams.
Launch timeline and expectations
Department templates begin rolling out February 11, 2026, using a phased, request-based intake process. Not all sites move at once, but each site must move all pages together—partial migrations are not supported. Sites will not go dark if they are not moved by April 24, but departments are expected to make a continuous, good-faith effort to migrate as close to the deadline as possible.
How the migration process works
Editors submit a new site request form to initiate setup. MARCOM Web Services creates a new site shell using the provided sitemap, including navigation and folder structure. Editors then rebuild content using new components and snippets, migrate selected images, and complete a redirect spreadsheet mapping old URLs to new ones. Once ready, a cutover request is submitted, redirects are implemented, the old site is sunset, and the new site goes live. Editors should plan for at least three business days for setup and cutover.
What editors should do now
Editors should review and simplify their site structure, draft or refine their sitemap, and reduce unnecessary pages. This is a strong opportunity to clean up content and remove pages that are no longer used. Images intended for reuse must be copied into an /images-to-migrate/ folder inside the existing images directory so they can be moved automatically. Editors should also identify PDFs that need to be removed, archived, remediated, or rebuilt as web pages.
When getting started building
- This is still Modern Campus–you already know how to use the platform
- If you have multiple sites, choose a small site first to get experience with the new components
- Build out other pages before the homepage - keep homepages simple
- Look at the component/snippet demos on our support site for ideas on how you want to present different content
- Work within the components and snippets presented - they are flexible, but to a point. Adapt your content to fit into the provided designs
- Filenames: use lowercase-hyphens-no-spaces.jpg (avoid caps, underscores, special characters)
- Images: we will have some image libraries available for certain components and backgrounds
- If you are using your own images, pay attention to dimensions, file size and file type. Resize hi-res photos
- See our images article (link coming Wednesday)
- Pages don’t have to be pretty to start. You can always add graphics, etc. later
- Make sure to move everything you want to use on the new site - anything getting called from the old site will break during cutover
- During the build: do not copy source code from old site as most things will break and may also bring over legacy code
- Clear all formatting from the old site, Google Docs, Word, etc. in Notepad, Modern Campus, or other editor
Important guidance on PDFs and accessibility
PDFs are difficult to remediate and should be avoided whenever possible. Content should be converted into HTML pages unless a PDF is truly required for download or printing. Archived PDFs may be stored in clearly labeled archive locations or external drives and must not be updated. Any PDFs created after April 24, 2026 must be fully accessible.
URL and file structure changes
Legacy directories such as /commcms/ and /sbroot/ will be removed from URLs, with server-level redirects handling the transition. New folder structures enforce proper file placement, restricting images, documents, and media to designated folders to prevent disorganized uploads.
New templates and quality-of-life improvements
Editors will work with a single flexible template supporting multiple layouts, accessible three-level navigation, improved side navigation behavior, streamlined footers, and more consistent components. Components now include previews, accessibility fields such as ARIA labels, and multiple design options within a single component. Dependency tags are strongly encouraged to prevent broken links during renaming and cutover.
Support and training
A new Web Support site will launch alongside the templates, featuring demos, help articles, and glossaries. Weekly open office hours begin February 25, along with additional migration trainings for student workers and freelancers. Editors are encouraged to use support request forms rather than direct outreach to help triage issues efficiently.
This workshop recording and slides are intended as a reference throughout the migration process. Editors are encouraged to start with smaller or less frequently updated sites, work within the provided components, and prioritize accessibility and simplicity during rebuilds.