Website Health & Happiness
Governance Review Schedule
Coming soon!
Requesting New Components & Features
- Fill out a “Component Submission” form on Wrike
- CMD will review the request and will take one of the following actions:
- Approve the request, at which point the component will go through CMD’s New Component Process
- Match the request with a component that already meets the stated needs
- Deny the request. If the component is too complex or unique (i.e. only used for one unit or need), the request will be denied.
Bug Reporting
- Defining a bug
- What is a bug? A technical error (i.e., a button doesn’t work, a page is 404ing, the layout is broken on mobile etc)
- What is NOT a bug? A type or request to change a photo, these fixes can be handled at the unit level
- Find a bug?
- Submit a ticket to SLTS
Accessibility & Inclusivity Goals
- U-M Resources on accessibility: https://accessibility.umich.edu/
- Our Tools: We use SiteImprove to monitor site health. There is a web app as well as an extension available on Chrome
- Units are responsible for fixing “Content-Level” errors (like missing Alt Text or broken heading orders)
- Accessible Files: All PDFs uploaded to the site must be run through an accessibility checker like Adobe Acrobat Pro. If a PDF can’t be made accessible, the information must be provided as a standard web page instead.
SEO Best Practices, Tips & Tricks
- Use your frontmatter (SEO Title and Meta Description)! It matters!
- Keywords vs. Clutter: Don’t “stuff” keywords. Write for the student first. If the student is looking for “Housing Contracts,” make sure that exact phrase is in your H1 or H2.
- Descriptive Links: Never use “Click Here.” Use descriptive text like “Download the 2024 Housing Contract.” (This helps Google and screen readers).
- URL Slugs: Keep them short and lowercase. studentlife.umich.edu/housing-application is better than studentlife.umich.edu/application-for-housing-2024-final-v2.