Curious about the design behind seths.blog?
SiteFontCheck scanned their live CSS architecture and identified 4 unique font families.
The website relies heavily on pt serif, serif for its main text elements, paired with source sans pro, sans-serif and franklingothic, helvetica, sans-serif as fallback options, and 1 additional.
Below is the precise map of font sizes, weights, and text elements used across their site.
Detected Fonts
4 foundsource sans pro, sans-serif
You have unread updates
pt serif, serif
0
monospace, monospace
Maintain a handoff doc for this work. Its reader is a smart stranger who has to take over tomorrow with no access to me or to our chats. At the end of any session where something changed, update the doc before you finish, without being asked. If nothing changed, say so in one line. The doc has these sections, always in this order: 1. WHAT THIS IS — two or three sentences: the project, who it's for, what "done" looks like. 2. CURRENT STATE — what works, what's half-built, what's broken. Dated. 3. WHERE THINGS LIVE — every file, folder, account, URL, and tool, with the exact name and location. No "the spreadsheet." Name it. 4. DECISIONS — each choice we made, the alternatives we rejected, and why. Never delete a decision; if we reverse one, mark it superseded and note the date and reason. 5. ASSUMPTIONS — things we're treating as true but haven't verified. Flag which ones would hurt most if wrong. 6. OPEN QUESTIONS & DILEMMAS — unresolved tensions, stated plainly, with the leading options. 7. PEOPLE — who's involved, their role, how to reach them, what they're waiting on. 8. NEXT STEPS — the first three things a newcomer should do. 9. HOW TO UNWIND — what it would take to stop, hand off, or move this to another platform. Rules: - Distinguish what I told you from what you inferred. Mark inferences. - Record the reasoning, not just the outcome. The "why" is the valuable part. - Be specific enough that someone could act without asking a question. - If something I say contradicts the doc, point it out instead of silently changing it. - Keep it tight. Cut stale detail into a dated one-line summary rather than letting the doc bloat. - If you're unsure whether something belongs, include it under Open Questions.
franklingothic, helvetica, sans-serif
Share This
Loading preview...