{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihlu7gqbq35ghoat76osy6hb7a76mtwwy6wo6j727oo5v5ihfiqvq",
    "uri": "at://did:plc:t4aigbwuwix7x3q42qzjc6mn/app.bsky.feed.post/3mowpn5ytvx72"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreihcrses3isijqnjldcxvnigqkrjidfu2tks7jknknty72gjbpms5a"
    },
    "mimeType": "image/jpeg",
    "size": 90716
  },
  "path": "/link/535/17365293/automating-application-screenshots",
  "publishedAt": "2026-06-22T12:05:00.000Z",
  "site": "https://brett.trpstra.net",
  "tags": [
    "Marked",
    "Subscribe Now",
    "on Mastodon",
    "Bluesky",
    "Twitter",
    "Click here if you'd like to help out.",
    "Mastodon",
    "GitHub",
    "everywhere else",
    "@2x"
  ],
  "textContent": "Keeping help documentation screenshots up to date is tedious. Every time the UI changes, you end up manually opening windows, hiding distractions, capturing images, cropping them, generating @2x versions, and dropping files into the right folders. I got tired of that workflow for Marked, so I built an AppleScript that does most of it for me.\n\nA lot of it this script is very Marked-specific — settings pane names, keyboard shortcuts, sample documents — but the bones are reusable. If you maintain docs for a Mac app, you can treat it as a starting point and swap in your own app logic.\n\nI’m paywalling this for my supporters. If you want to see the script, please pitch in a few bucks a month for full access!\n\n🔒\n\n### Premium Content\n\nThis content is for subscribers only.\n\nSubscribe Now I'm a Subscriber\n\nLike or share this post on Mastodon, Bluesky, or Twitter.\n\n* * *\n\nBrettTerpstra.com is supported by readers like you. Click here if you'd like to help out.\n\nFind Brett on Mastodon, Bluesky, GitHub, and everywhere else.",
  "title": "Automating Application Screenshots",
  "updatedAt": "2026-06-22T12:05:00.000Z"
}