Checklist the per-video bar — engine/sim
74.0/100
quantitative quality · weights learn from your reviews (
engine.sim.memory review thread-field-notes-W47-Sat good|bad)⚠ 7 flag(s) — not yet ship-ready: copy_genericlow_vo_coveragedead_airgeneric_scene · see docs/strategy/VIDEO-CHECKLIST.md
Composition comp · template family · expected output
9:16 Reelrendered1:1 Squarepending16:9 Widepending9:16 4Kpending1:1 4Kpending16:9 4KpendingGIF (SMS)pending
expected output: 1/7 rendered — same matrix the /media preview surfaces for this asset.
Composition layer × scene 5 scenes · 26.4s · comp_id + rendered still + tier + the script
| # | Layer (comp_id · still · tier) | Beat | Timecode | Motion | Logo | Audio | VO / on-screen / caption |
|---|---|---|---|---|---|---|---|
| 1 |  first render · fix pending shared field signature-3ddead_air | hook | 0–5.0s | kinetic-build | icon·color | ♪ node_lock | Field note. Your content site feels slow, and most of the time the slow part is the CMS itself. on-screen: Your CMS is the slow part |
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · mark · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual markshape knotground whitetreatment colormotion kinetic-buildpower laser-lockinstrument laser-trace→Your CMS is the slow part | |||||||
| 2 |  matches intent NumberedList template | teach | 5.0–11.4s | kinetic-build | icon·color | ♪ node_lock | Old way: the CMS queries a database and assembles the page live, every single hit. on-screen: Pre-build, serve plain files |
expected on screen: white ground · a NumberedList panel over a dimmed Signal Field · Magister leads · node-graph · kinetic-build · icon·color logo · caption bottom-left spec (the prompt): comp_id NumberedListvisual node-graphshape knotground whitetreatment colormotion kinetic-buildpower morphinstrument morph+laser→Pre-build, serve plain filescurate items, nodes | |||||||
| 3 |  matches intent TerminalRun template | diff | 11.4–16.4s | crossfade-8f | icon·color | ♪ node_lock | Take your most-visited section and pre-build it to static files, then serve those files straight from the cache. on-screen: Pre-render one section |
expected on screen: white ground · a TerminalRun panel over a dimmed Signal Field · Magister leads · code · crossfade-8f · icon·color logo · caption bottom-left spec (the prompt): comp_id TerminalRunvisual codeshape knotground whitetreatment colormotion crossfade-8fpower morphinstrument morph→Pre-render one sectioncurate codeLines | |||||||
| 4 |  first render · fix pending LegacyCard templatedead_airgeneric_scene | proof | 16.4–21.4s | receipts-count | icon·color | ♪ node_lock | Field Notes |
expected on screen: white ground · a LegacyCard panel over a dimmed Signal Field · Magister leads · receipts · receipts-count · icon·color logo · caption bottom-left spec (the prompt): comp_id LegacyCardvisual receiptsshape knotground whitetreatment colormotion receipts-countpower receiptsinstrument spotlight→Field Notescurate statsLabels | |||||||
| 5 |  first render · fix pending shared field signature-3ddead_airgeneric_scene | resolve | 21.4–26.4s | coalescence | icon·ember-fill | ♪ bed_out | Field Notes |
expected on screen: white ground · knot hero in the shared Signal Field · Magister leads · coalescence · coalescence · icon·ember-fill logo · caption bottom-left spec (the prompt): comp_id shared Signal Fieldvisual coalescenceshape knotground whitetreatment ember-fillmotion coalescencepower coalescenceinstrument coalescence→Field Notes | |||||||
Format stack 3 aspects · same scenes[], re-cropped
9:16
1080×1920
Stories · TikTok · YouTube Shorts · Reels
1:1
1080×1080
LinkedIn · Facebook · Instagram
16:9
1920×1080
X/Twitter · YouTube · LinkedIn video
Channels 9 destinations
LinkedInX/TwitterYouTubeInstagramFacebookThreadsTikTokPinterestBluesky
Social captions supplemental published copy · per channel (comp_id level)
tiktokField note: your content site feels slow, and usually the slow part is the CMS. It queries a database and builds the page live on every hit. Fix: take your most-visited section, pre-build it to static files, and serve those from the cache. (AI-assisted)
instagramField note.
Site feels slow?
Usually it's the CMS.
It queries a DB and builds the page live, every hit.
Fix: pre-build your top section to static files.
Serve from cache.
#webdev #performance #CMS #staticsite #speed
linkedinField note: when a content site feels slow, the slow part is usually the CMS itself.
The old way: the CMS queries a database and assembles the page live on every single hit. That work repeats for every visitor, even when the content has not changed.
The fix: take your most-visited section, pre-build it to static files, and serve those straight from the cache. Same content, none of the per-hit work. Start with one section and measure.
xField note: your site feels slow because the CMS builds the page live on every hit.
Fix: pre-build your most-visited section to static files and serve from cache. Same content, none of the work. temerarii.xyz
facebookField note for anyone with a slow content site: the slow part is usually the CMS, which queries a database and builds the page live on every visit. The fix is simple. Take your most-visited section, pre-build it to static files, and serve those from the cache. Start small and measure. temerarii.xyz.
threadsField note.
Your content site feels slow, and most of the time the slow part is the CMS. It queries a database and assembles the page live on every single hit.
Fix: take your most-visited section and pre-build it to static files, then serve those straight from the cache. Same content, none of the repeated work.
pinterestHow to speed up a slow content website: the CMS is usually the bottleneck because it queries a database and builds each page live on every hit. The fix is to pre-build your most-visited section to static files and serve them from the cache. Web performance and static site optimization tips.
blueskyField note: your content site feels slow because the CMS builds the page live on every hit. Fix: pre-build your most-visited section to static files and serve from cache.
youtubeTitle: Field Note: Pre-Build Your CMS Pages to Static Files
When a content site feels slow, the slow part is usually the CMS, which queries a database and assembles the page live on every hit. We show the fix: take your most-visited section, pre-build it to static files, and serve those straight from the cache. Web performance, static rendering, CMS optimization. temerarii.xyz.