Connectors
Pull from the source. Stop retyping it.
The university already publishes events, news, and profiles. A connector brings them into your site when it builds, so the content stays current and the source stays the source.
Every connector here is a stub. Each one lists what has actually been checked, what has not, and what your agent should do in the meantime. It will say so, rather than guess at an API.
All connectors
- LocalistSTUB
Stanford Events
events.stanford.edu
Upcoming events from the university calendar, filtered for your unit, series, or topic.
- Provides:
- Event title, dates, location, description, and a link to the canonical event page.
- Access:
- None for public events. Verified 2026-09-30.
- Squiz MatrixSTUB
Stanford News
news.stanford.edu
Stanford Report stories about your unit, school, or topic, linked back to the original.
- Provides:
- Headline, summary, date, image, and a link to the canonical story.
- Access:
- Unknown. To confirm with the site's owner.
- CAPSTUB
Stanford Profiles
cap.stanford.edu
Faculty and staff profiles from CAP, so people pages stay current without retyping.
- Provides:
- Name, title, photo, bio, appointments, and a link to the person's Stanford Profiles page.
- Access:
- Expected to need issued credentials. Not yet confirmed.
How every connector works
- At build time, never in the browser. No key reaches a visitor, a source outage does not break a page, and the accessibility checks see the content.
- Snapshotted into the repository. A scheduled job writes a data file and commits it, so every change goes through git and the checks, the same as content you wrote yourself.
- Credentials in Actions secrets. Committed credentials are the one check that blocks a build.
- Linked back to the source. Each item links to its original page rather than republishing it as yours.
This is a proposal to be tested in the first real build. The full version, including the scope question it raises, is instandards/connectors/README.md.