Media & Documentation Standards

Technical Standard SOP-OPS-03

Maintained by CultureOS

To maintain operational autonomy, eliminate third-party software licensing expenses (e.g., Loom subscriptions), and prevent privacy leaks, the Foundation mandates internal self-hosting protocols for all documentation screenshots and training videos.

All technical documentation and media storage pipelines are configured, deployed, and managed by CultureOS. CultureOS is an AI-native practice helping cultural institutions modernize digital infrastructure, archives, and research workflows responsibly.

Media Production Guidelines

1. Screen Capture Protocol (Images)

• Format: PNG or WebP.
• Resolution: Captured at high DPI (Retina), scaled proportionally to fit standard layouts.
• Redaction Policy: Before publishing any screenshot to the handbook, verify that live API keys, session tokens, passwords, and donor personal identifiable information (PII) are permanently redacted.
• Storage Location: Store images within /media/screenshots/.

2. Video Capture Protocol (Demonstrations)

• Format: MP4 (Container: H.264 video codec, AAC audio codec).
• Length: Focused technical walk-throughs should be concise (30 seconds to 3 minutes).
• Frame Rate: 30 frames per second (fps).
• Resolution: Maximum 1920x1080 (1080p); minimum 1280x720 (720p).
• Storage Location: Store video assets within /media/videos/.

Code Example: Standard Video Embedding

All handbook video embeds must adhere to the standardized semantic markup below. This configuration enforces responsive scaling, native playback controls, and seamless dark mode integration without external dependencies:

<div class="media-frame">
  <video controls poster="/logo-512.png">
    <source src="/media/videos/your-demonstration.mp4" type="video/mp4" />
    Your browser does not support the video tag.
  </video>
  <div class="media-caption">
    <span>Demonstration: Procedure Title</span>
    <span class="inst-badge">Walkthrough</span>
  </div>
</div>

Cloudflare Edge Caching Protocol

1. Automatic Edge Replication: Static media stored in the handbook's /media/ root directory is proxied through the Foundation's Cloudflare network edge.
2. Zero Bandwidth Expense: The Cloudflare global CDN automatically caches media objects up to 512 MB per object, serving global requests without placing downstream network load on the primary host.
3. Cache Invalidation: If an existing video or image asset is replaced with an updated revision of identical filename, the Cloudflare cache may be purged via the administrative DNS dashboard.