---
title: "Jack (@seedancejack) | Hashnode"
description: "Jack (@seedancejack) writes on Hashnode. Read their latest articles and follow their work."
url: "https://hashnode.com/@seedancejack"
---

@seedancejack

# Jack

@seedancejack · Joined November 2026

### [Keep a Docs Mascot Consistent: Character Locks and Multi-Image Combines](https://seedancejack.hashnode.dev/keep-a-docs-mascot-consistent-character-locks-and-multi-image-combines?utm_source=hashnode&utm_medium=feed)

A documentation site can survive a slightly ugly screenshot. It cannot survive a mascot that changes species between chapters. We learned this the slow way. We had a small illustrated character — a ro

6 min read · [seedancejack.hashnode.dev](https://seedancejack.hashnode.dev/keep-a-docs-mascot-consistent-character-locks-and-multi-image-combines?utm_source=hashnode&utm_medium=feed)

[1d ago](https://hashnode.com/posts/keep-a-docs-mascot-consistent-character-locks-and-multi-image-combines/6af81dd438318f95450fc00f)

### [Treat AI Video Like a Build Artifact: References, Variants, and Platform Exports](https://seedancejack.hashnode.dev/treat-ai-video-like-a-build-artifact-references-variants-and-platform-exports?utm_source=hashnode&utm_medium=feed)

Teams that publish a lot of product content already know how to treat copy and screenshots as source. The markdown is in git. The screenshots have names. Video is the usual exception: a final file on

5 min read · [seedancejack.hashnode.dev](https://seedancejack.hashnode.dev/treat-ai-video-like-a-build-artifact-references-variants-and-platform-exports?utm_source=hashnode&utm_medium=feed)

[2d ago](https://hashnode.com/posts/treat-ai-video-like-a-build-artifact-references-variants-and-platform-exports/6af6d413e314ef0e3d098a2e)
