Colophon

How this site is written, hosted, published, and kept accurate — and which parts a machine drafted.

Written with AI, and saying so

This site asks faculty to be transparent with students about their own use of AI — on slides, on feedback, in grading. It would be odd to make that argument anonymously.

Most of these pages were drafted in Claude Code and then edited, cut, and corrected by hand. The model works from a standing instruction file in the repository that sets voice and house rules, not from a blank prompt each time. Claims about people, policies, and sources need checking against the sources themselves: these tools can produce confident, plausible, wrong citations, which is exactly the failure this site warns instructors about.

What that looks like in practice

Colleagues have asked to see the actual prompts rather than a description of them. Here is a real one.

Prompt

what does the ai resources portal have about teaching with AI → that content belongs on the pedagogy portal, but it is important to cross link

That produced an audit across both sites, which found five teaching skills described in full on each — the same tools, two sets of prose, and names that had drifted apart. The duplicates on the other portal were replaced with a single pointer here. The prompt is unremarkable: it names a goal and a constraint and leaves the method open. That is most of the craft.

Accuracy passes

I use structured fact-checking for substantive additions: review agents identify factual claims, check them against sources, and report what they could not confirm. The first MIT version received a source check before publication; a later full Eddie pass found further corrections, which were then published. The repository history records that sequence. A review is not a guarantee that every claim has been verified.

This is not optional politeness. A teaching-guidance site that misquotes a report or misstates a policy does real damage to whoever relies on it.

Hosting

Served byGitHub Pages, built from the main branch at the repository root. HTTPS enforced.
Domainpedagogy.pennlawteaching.org, set by a CNAME file in the repository.
Shortlinkpennlaw.link/pedagogy, handled by an exact-match Cloudflare redirect. Other paths without an override proxy through to Rebrandly. This is the address worth sharing: it survives a move, and the site has moved once already.
Former addressThe earlier polkwagner.github.io address still redirects here.
SourceThe repository is private, so there is no public link to it. Designated internal working notes, archived correspondence, and internal source files are excluded from the public site; public resource PDFs are intentionally served from docs/.
External dependenciesOne: Google Fonts. No analytics, no trackers, no CDN scripts.

Publication pipeline

There is no local application build step and no framework. The site is hand-written HTML with its CSS and JavaScript inline. Serve the files over a simple local HTTP server to preview the Pages output.

What stays human

The judgment. Which recommendations are worth making to colleagues, how far a finding from another institution travels to a law school, what is too uncertain to assert, and everything written in the first person. Errors here are mine.

Typography and colour

The main portal and its companion pages use EB Garamond for headings and DM Sans for body text, both served from Google Fonts — the same pairing as the AI Resources portal, so the two read as siblings. The digital-signage page uses Cormorant Garamond and Source Sans 3.

Licence

Original site content is CC BY 4.0 and the code is Apache 2.0. Third-party material and institutional marks are excluded from the site's license grants — see the licence page.

← Back to Faculty Pedagogy Resources