improvement(changelog): refresh media and released product updates

apps/sim/app/(landing)/changelog/components/changelog-video/changelog-video.tsx

@@ -1,4 +1,4 @@
-import { cn } from '@sim/emcn'
+import { cn, Lightbox } from '@sim/emcn'
 import { isChangelogMediaSource } from '@/lib/changelog/media'
 import { LANDING_STAGE_RADIUS } from '@/app/(landing)/components/landing-layout'
 
@@ -8,31 +8,58 @@ interface ChangelogVideoProps {
   /** Accessible description for the player; not repeated below the video. */
   caption: string
   captionsSrc?: string
+  width?: number | `${number}`
+  height?: number | `${number}`
 }
 
-/** Product recordings load on demand and retain a readable description without playback. */
-export function ChangelogVideo({ src, poster, caption, captionsSrc }: ChangelogVideoProps) {
+/** A quiet poster opens the recording in the shared media viewer. */
+export function ChangelogVideo({
+  src,
+  poster,
+  caption,
+  captionsSrc,
+  width = 1280,
+  height = 720,
+}: ChangelogVideoProps) {
   if (!isChangelogMediaSource(src) || (captionsSrc && !isChangelogMediaSource(captionsSrc))) {
     throw new Error('Changelog recordings must use same-origin paths or the approved media CDN')
   }
   return (
     <figure className='my-6'>
-      <video
-        controls
-        muted={!captionsSrc}
-        playsInline
-        crossOrigin='anonymous'
-        preload='none'
+      <Lightbox
+        type='video'
+        src={src}
         poster={poster}
-        aria-label={caption}
-        className={cn('aspect-video w-full bg-[var(--surface-2)]', LANDING_STAGE_RADIUS)}
+        alt={caption}
+        captionsSrc={captionsSrc}
+        crossOrigin='anonymous'
       >
-        <source src={src} type='video/mp4' />
-        {captionsSrc ? (
-          <track kind='captions' src={captionsSrc} srcLang='en' label='English' default />
-        ) : null}
-        <a href={src}>Watch the demo</a>
-      </video>
+        <button
+          type='button'
+          aria-label={`Open ${caption} in media viewer`}
+          className={cn(
+            'block w-full cursor-zoom-in overflow-hidden focus-visible:outline focus-visible:outline-2 focus-visible:outline-[var(--text-primary)] focus-visible:outline-offset-4',
+            LANDING_STAGE_RADIUS
+          )}
+        >
+          <video
+            muted
+            playsInline
+            preload='none'
+            poster={poster}
+            width={width}
+            height={height}
+            aria-hidden='true'
+            tabIndex={-1}
+            className='pointer-events-none block h-auto w-full bg-[var(--surface-2)]'
+          >
+            <source src={src} type='video/mp4' />
+            {captionsSrc ? (
+              <track kind='captions' src={captionsSrc} srcLang='en' label='English' />
+            ) : null}
+          </video>
+        </button>
+      </Lightbox>
     </figure>
   )
 }

apps/sim/content/changelog/README.md

@@ -50,7 +50,7 @@ Choose a few relevant links instead of repeating every destination in a separate
 
 ## Search and answer-engine visibility
 
-Keep each summary independently useful: name Sim and the feature, explain the new capability, and state material availability limits in the article. Put setup steps and demonstration explanations in server-rendered text alongside the media. Do not leave important facts only inside a screenshot or video.
+Keep each summary independently useful: name Sim and the feature, explain the new capability, and state material availability limits in the article. Write a short announcement of what changed and why it is useful, with a contextual setup link. Keep capture notes and review evidence in the production brief, out of public prose and media descriptions. Do not leave important facts only inside a screenshot or video.
 
 The index and archive use real links, semantic lists, and CollectionPage/ItemList data matching the visible entries. Articles keep their own canonical URLs, BlogPosting data, authorship metadata, original publication dates, and substantive correction dates. Public articles appear in the sitemap and RSS; previews stay noindex and drafts stay out of public routes. Preserve these properties when changing the layout. If the archive eventually needs pagination, use server-rendered pages with real next/previous links and a self-canonical URL for each page; do not make older entries accessible only through a JavaScript button.
 
@@ -61,11 +61,11 @@ After deployment, verify a representative article and the archive with Search Co
 ## Artifact delivery
 
 - Record one complete action and its visible result with sample data in a dedicated demo workspace. Verify the feature and permissions in that environment first. Use the product's normal theme and typography. Keep the cursor and text readable; crop around the relevant controls while preserving enough context to understand the action.
-- Export an H.264 MP4 at a readable resolution, usually 1280×720 or 1920×1080. Keep it about 20–45 seconds and optimize it for web playback with `+faststart`. Prefer a focused demonstration with native playback controls over a decorative loop. Check the final crop on a 390px-wide screen.
-- Take screenshots and the poster from the reviewed product capture. Choose a frame that shows the announced result, with a legible 16:9 crop for the story card. A separate 1200×630 share image can use the same frame with enough safe area for cropping. Keep the headline and benefit in the page's HTML rather than baking them into the image. Compress local JPEG, WebP, or PNG assets and retain actual screenshot dimensions in MDX.
+- Export an H.264 MP4 at a readable resolution, usually 1280×720 or 1920×1080. Keep it about 20–45 seconds and optimize it for web playback with `+faststart`. The article shows the reviewed poster; playback starts only after opening the shared lightbox, which provides pause, seeking, and zoom controls. Spoken recordings include captions and an unmute control. Check the preview and expanded recording on a 390px-wide screen.
+- Take screenshots and the poster from the reviewed product capture. Choose a frame that shows the announced result. Preserve the capture's aspect ratio and provide its actual width and height in MDX for both screenshots and videos. A separate 1200×630 share image can use the same frame with enough safe area for cropping. Keep the headline and benefit in the page's HTML rather than baking them into the image. Compress local JPEG, WebP, or PNG assets.
 - Use immutable, versioned media filenames, such as `compare-workflow-deployments-v1.mp4`. Upload recordings and spoken captions under `changelog/` in the existing public Academy asset store: `https://nnjgp7vypgx4myuq.public.blob.vercel-storage.com`. Put the returned public URLs in the entry. The app CSP and content audit explicitly allow this origin for recordings and captions. Small optimized walkthroughs under 1 MiB can live in `public/changelog/` and deploy atomically with their entry. Use the CDN for larger recordings. The component does not upload or proxy videos.
 - Serve MP4s as `video/mp4` and spoken captions as `text/vtt`. The existing CDN supports HTTP Range requests, cross-origin playback, and caching. Use a new filename for every revision and verify those response headers on the uploaded asset. Do not overwrite an existing recording URL.
-- In the deployment preview, check playback, seeking, captions, poster loading, and mobile readability. A silent recording uses the component's muted default. Spoken recordings need a WebVTT file.
+- In the deployment preview, check opening and closing the lightbox, playback, pause, seeking, zoom, captions, poster loading, and mobile readability. Recordings start muted; spoken recordings need a WebVTT file and expose an unmute control.
 - Generate social and email drafts from the reviewed product story: capability, practical benefit, and one link to the canonical entry. Use the same claims and restrictions everywhere. Keep distribution manual until the format and review process are established.
 
 AI can prepare storyboards, copy, captions, and clearly labeled conceptual diagrams. Screenshots and feature recordings must come from the real product. Do not generate fictional controls, results, performance numbers, or before-and-after evidence. Label a walkthrough assembled from still captures as a step-by-step walkthrough; do not describe it as a continuous recording. Keep its UI frames unmodified and record the assembly method in the production brief.
@@ -101,6 +101,8 @@ release:
 <ChangelogVideo
   src="https://nnjgp7vypgx4myuq.public.blob.vercel-storage.com/changelog/demo-v1.mp4"
   poster="/changelog/your-update-poster.jpg"
+  width="1280"
+  height="720"
   caption="Describe the action and result shown in the demo."
   captionsSrc="https://nnjgp7vypgx4myuq.public.blob.vercel-storage.com/changelog/demo-v1.vtt"
 />

apps/sim/content/changelog/compare-workflow-deployments/index.mdx

@@ -3,9 +3,10 @@ slug: compare-workflow-deployments
 title: 'Compare workflow versions before you deploy'
 description: 'See prompt edits, added steps, and changed connections in Sim. Compare two deployments or check your draft against the live workflow.'
 date: '2026-10-02T06:55:11Z'
+updated: '2026-10-10T01:48:00Z'
 authors: [waleed]
 tags: [Workflows]
-ogImage: /changelog/compare-workflow-deployments-v1.jpg
+ogImage: /changelog/compare-workflow-deployments-v2.jpg
 ogAlt: 'Sim compares two workflow versions, highlighting a prompt edit and an added Slack step'
 technical: false
 draft: false
@@ -14,14 +15,13 @@ release:
   url: https://github.com/simstudioai/sim/releases/tag/v0.9.10
 ---
 
-<ChangelogVideo
-  src="/changelog/compare-workflow-deployments-v1.mp4"
-  poster="/changelog/compare-workflow-deployments-v1.jpg"
-  caption="Review a prompt edit and an added Slack step. Edited walkthrough from real Sim captures with sample data."
+<ChangelogImage
+  src="/changelog/compare-workflow-deployments-v2.jpg"
+  alt="Workflow comparison highlighting a changed agent prompt and an added Slack step"
+  width="1200"
+  height="605"
 />
 
-Open deployment history and choose **Compare** from a version's menu. Select a changed block to inspect its settings alongside the workflow. For a draft, choose **View changes** to compare it with the live version before redeploying.
+Compare any two workflow deployments, or review your draft against the live version. See prompt edits, added steps, and changed connections together so you can check exactly what will change before deploying.
 
-Use it to review a support agent's new instructions and the [Slack](/integrations/slack) step added to send its digest. The comparison is read-only and leaves your draft intact.
-
-Included in **v0.9.10**. See the [deployment guide](https://docs.sim.ai/workflows/deployment) for setup, or [compare versions through the API](https://docs.sim.ai/api-reference/workflows/compareWorkflowVersionsV2).
+Open **Compare** in deployment history or **View changes** on your draft. [Learn more about deployments](https://docs.sim.ai/workflows/deployment).

apps/sim/content/changelog/compare-workflow-deployments/production.md

@@ -1,6 +1,6 @@
 # Deployment comparison: production record
 
-Status: prepared for publication review. Only `index.mdx` is rendered publicly.
+Status: published; October 9 media refresh prepared for review. Only `index.mdx` is rendered publicly.
 
 ## Evidence
 
@@ -11,21 +11,17 @@ Status: prepared for publication review. Only `index.mdx` is rendered publicly.
 
 ## Media provenance
 
-A dedicated local workspace contains a synthetic support-ticket workflow with two deployments. The second changes the agent prompt and adds a Slack step. No model or Slack call was executed for this capture.
+Refreshed on October 9, 2026 (October 10 UTC), using the running local app at commit `36f91a76e2`, including the current embedded comparison presentation from #8862. A dedicated disposable workspace contains a synthetic support-ticket workflow with two deployment snapshots. The second changes the agent prompt and adds a Slack step. No model or Slack call was executed.
 
-The media comes from the running product, captured through the browser. The video is a silent, edited walkthrough assembled from three unmodified UI captures with reading pauses; it is not a continuous screen recording. No generated controls or results are used.
+Open deployment history, choose Compare from v2's menu, and inspect v1 against v2. The reviewed image shows the real comparison dialog, including the changed prompt, added Slack step, and connection. It is a direct browser capture cropped to the dialog, 1200 × 605 pixels; no controls or results were generated or altered.
 
-1. Open deployment history.
-2. Open the version menu and choose Compare.
-3. Inspect the changed prompt, added Slack step, and connection.
-
-Assets: `/changelog/compare-workflow-deployments-v1.mp4` and `/changelog/compare-workflow-deployments-v1.jpg`. The poster is the final comparison view. The short MP4 is served locally with the site; larger future recordings should use the approved media CDN. Keep filenames immutable.
+Current asset: `/changelog/compare-workflow-deployments-v2.jpg`. A still is more useful for inspecting this before/after state than the previous slideshow. It opens in the shared image lightbox and supplies the share image. The earlier v1 JPEG and MP4 remain available at their immutable URLs for existing links, but the article no longer embeds the video.
 
 ## Review notes
 
-The screenshot replaces the older deployment-history reference. The comparison is read-only and shows actual before/after fields. Copy covers both two-version comparison and draft-versus-live review; the media demonstrates the two-version path. The draft remains unchanged after opening and closing Compare.
+The refreshed screenshot replaces the edited video walkthrough. The comparison is read-only and shows actual before/after fields. Copy covers both two-version comparison and draft-versus-live review; the media demonstrates the two-version path. The draft remains unchanged after opening and closing Compare.
 
-The entry keeps the historical release timestamp and RSS identity. Playback, mobile layout, asset responses, and content validation belong in the publication PR's validation record. Assign the release editor and feature reviewer in that PR; verify the public URL before distributing.
+The entry keeps the historical release timestamp and RSS identity. Lightbox zoom, mobile layout, asset responses, and content validation belong in the publication PR's validation record. Assign the release editor and feature reviewer in that PR; verify the public URL before distributing.
 
 ## Announcement drafts
 

apps/sim/content/changelog/editorial-standard.md

@@ -14,11 +14,11 @@ Keep existing article URLs, original dates, and RSS identities when refining his
 
 - Headline: name the capability or action, at most 65 characters. Avoid generic headlines such as “A better experience.”
 - Summary: 15–40 words for search, sharing, and RSS, naming Sim and explaining the capability in plain language. It must make sense without the image.
-- Body: normally 60–180 words, with one concrete example or short path to the feature. Explain the action and result; do not repeat the summary or turn a small improvement into a tutorial.
-- Media: place the reviewed image or video immediately after the article header, before procedural detail. Images use the shared lightbox and can show a brief caption for a necessary demonstration limit. Videos keep native playback controls and an accessible description, without a repeated description beneath the player. Any material claim limitation belongs in the article's prose.
+- Body: lead with what changed and what teams can do with it. Aim for 2–4 short sentences, usually 30–90 words, followed by a useful documentation link. There is no minimum word count; keep the body under 120 words. Use one concrete example when it adds clarity. Save setup instructions for the linked guide; do not pad a simple update into a tutorial.
+- Media: place the reviewed image or video immediately after the article header. Both use the shared lightbox; videos show a plain poster with playback, seeking, and zoom controls inside the viewer. Use concise alt text or an accessible action label without a visible video description. Do not add captions or prose about how the capture was made, whether a query ran, sample credentials, or what a screenshot does not prove. Keep capture provenance and review evidence in production.md.
 - Supporting notes: up to three related, source-backed improvements, each one sentence. Omit empty sections. Do not invent extras to fill a template.
 - Links: one descriptive setup/documentation link, plus an integration, model, or product link when directly relevant. Use the actual catalog slug and guide. Put links in context; avoid a wall of generic “Learn more” links.
-- Availability: retain real version, plan, permission, and rollout restrictions in the article. Keep unverified rollout questions, source analysis, capture instructions, and approval checkboxes in production.md.
+- Availability: keep restrictions that affect whether someone can use the feature, such as a required plan or administrator role, in one concise sentence. Link to documentation for setup details. Keep unverified rollout questions, source analysis, capture instructions, and approval checkboxes in production.md. Never substitute a capture disclaimer for verifying a claim.
 
 Use short active sentences and familiar words. Technical identifiers, retry timings, queue keys, PR numbers, and performance claims without measurements do not belong in the article. There is no minimum number of announcements per week.
 
@@ -36,7 +36,7 @@ Every production brief records:
 
 Use the same clean demo workspace and product theme. Frame the relevant panel with enough context to locate it, and make the result legible at a 390px viewport. Hide unrelated private sidebar content before recording. Keep UI text and controls intact; never generate a different product state to improve a screenshot. Prefer recording at the intended framing over aggressive crops later.
 
-Begin with the task ready to perform, show the action, and hold on its result. Avoid decorative intros, music, title cards, and excessive cursor movement. Keep the headline and important explanation in HTML. Label videos assembled from still screenshots as edited walkthroughs.
+Begin with the task ready to perform, show the action, and hold on its result. Avoid decorative intros, music, title cards, and excessive cursor movement. Keep the headline and important explanation in HTML. Record videos assembled from still screenshots as edited walkthroughs in the production brief; do not describe them as continuous recordings in public copy.
 
 Choose the poster deliberately after reviewing the video. An opening menu, empty state, spinner, or arbitrary first second rarely explains the feature. The media workflow can provide candidate frames, but an editor selects the final timestamp. Preview candidates are not approved assets. Preserve the real aspect ratio inside the shared media frame; do not stretch product UI. Use the same reviewed result frame for the article poster and share image when it works in both contexts.
 

apps/sim/content/changelog/intune-device-inventory/index.mdx

@@ -0,0 +1,25 @@
+---
+slug: intune-device-inventory
+title: 'Bring Intune device inventory into your agents'
+description: 'Use Microsoft Intune in Sim to read managed devices, installed application inventory, and compliance status for IT reviews and agent follow-ups.'
+date: '2026-10-08T07:10:06Z'
+authors: [waleed]
+tags: [Integrations]
+ogImage: /changelog/intune-device-filter-v1.jpg
+ogAlt: 'Microsoft Intune block in Sim configured to list noncompliant devices'
+technical: false
+draft: false
+release:
+  versions: [v0.9.15]
+---
+
+<ChangelogImage
+  src="/changelog/intune-device-filter-v1.jpg"
+  alt="Microsoft Intune List Devices operation with a noncompliant-device filter in Sim"
+  width="1280"
+  height="720"
+/>
+
+Your agents can now read managed devices, installed applications, and compliance status from [Microsoft Intune](/integrations/microsoft-intune). Filter for noncompliant devices to prepare an IT review or bring device inventory into an agent's response.
+
+[Connect Microsoft Intune](https://docs.sim.ai/integrations/intune) to get started. An active Intune license, appropriate account role, and administrator consent are required.