Further Reading & Resources
Sources we reference throughout these docs, plus useful background on the tools and technology behind the site
This page collects the sources cited throughout the docs along with background reading on the technology powering the site. Some of these are the basis for specific recommendations; others are just good context if you want to dig deeper.
Writing & content
| Resource | What it covers |
|---|---|
| Nielsen Norman Group: How People Read Online | Eye-tracking research on scanning behavior — the foundation for most of our formatting advice |
| NNG: F-Shaped Pattern of Reading | The original eye-tracking study on how users scan web pages |
| NNG: Inverted Pyramid | Why the most important information should come first |
| NNG: "Learn More" Links | Why generic link text hurts usability and what to do instead |
| NNG: Minimize Cognitive Load | The design principle behind "calm and approachable" |
| plainlanguage.gov | Federal plain language guidelines — excellent reference for clear writing |
| Hemingway Editor | Free readability checker (paid Plus tier available for AI features) |
SEO
| Resource | What it covers |
|---|---|
| Google: Creating Helpful Content | Google's own guidelines on what makes content rank well — "people-first content" |
| Google: Title Links | How Google generates and displays page titles in search results |
| Google: Structured Data Overview | What JSON-LD structured data is and how Google uses it |
| Google: Organization Schema | Structured data for nonprofit/organization info |
| Google: Local Business Schema | Structured data for locations like dining centers |
| Google: Job Posting Schema | Structured data for career listings |
| Search Engine Journal: Meta Descriptions | Practical guide on meta description length and best practices |
A note on FAQ schema
Google used to display FAQ answers directly in search results using FAQ structured data. They restricted this in August 2023 and fully deprecated it in May 2026. If you hear someone recommend FAQ schema for SEO purposes, it no longer has any effect in Google Search.
Accessibility
| Resource | What it covers |
|---|---|
| WCAG 2.2 | The current Web Content Accessibility Guidelines (W3C Recommendation, October 2023) |
| WCAG: Contrast Minimum (AA) | 4.5:1 for normal text, 3:1 for large text |
| WCAG: Target Size Minimum (AA) | 24x24px minimum for interactive elements |
| WCAG: Target Size Enhanced (AAA) | 44x44px — what we target as best practice |
| W3C WAI: Image Alt Text Tips | How to write meaningful alt text |
| W3C WAI: Heading Structure | Best practices for heading hierarchy |
| MDN: prefers-reduced-motion | The CSS media query for respecting motion preferences |
| axe by Deque | Automated accessibility testing tool |
| Google Lighthouse | Performance, accessibility, and SEO auditing |
Language & tone
| Resource | What it covers |
|---|---|
| APA: Bias-Free Language (Age) | American Psychological Association guidance on age-related terms |
| National Institute on Aging | Uses "older adults" throughout — a reference for respectful language in aging services |
| Springer: Face Photos and Truthfulness | Research showing claims paired with face photos are perceived as more truthful |
| BrightLocal: Consumer Review Survey | Annual survey on how photos and attribution affect review credibility |
On 'older adults' vs. 'seniors'
There's no universal consensus here. The APA and NIA prefer "older adults." AARP uses both "older adults" and "seniors" across their site. In practice, "seniors" is what most people search for and what many organizations use in everyday communication. Our recommendation: use "neighbors" as the default on the MOWP site, and don't overthink the rest — use whatever feels natural to how the team already talks about its community.
Technology
These are the core tools powering the new site. You don't need to understand them to use the CMS, but they're here for reference.
| Tool | What it does | Learn more |
|---|---|---|
| Payload CMS | The content management system where you'll edit pages and manage content | Docs |
Infrastructure & hosting
You don't interact with any of this directly, but it's worth knowing what's in place to keep the site safe, fast, and recoverable.
| Tool | What it does for you |
|---|---|
| GitHub | Every change to the site is tracked in version control using Git. Nothing gets lost — if something breaks, we can roll back to any previous version. All code changes go through a review process before they go live. |
| Cloudflare | Sits between visitors and the server. It provides DDoS protection, a global CDN (so the site loads fast regardless of where someone is), SSL certificates, and caching. Think of it as a security and speed layer that runs automatically. |
| Automated backups | The site and its content are backed up regularly. If something goes wrong — whether it's an accidental deletion or a server issue — we can restore from a recent backup. |
| Continuous deployment | When we push a change to the code, it automatically builds and deploys. No manual file uploads, no FTP, no "it works on my computer" issues. Every deployment is consistent and repeatable. |
What this means in practice
If the site goes down, we can restore it. If a change causes a problem, we can undo it. If traffic spikes (a viral social post, a matching gift campaign), Cloudflare handles the load. The infrastructure is designed so you never have to think about it.
Design references
See the full list of reference sites and design inspiration.