docs: refresh workspace-management screenshots with current UI - #28356
Conversation
There was a problem hiding this comment.
💡 Codex Review
In the refreshed UI shown here, the dropdown is labeled Bulk actions, but docs/user-guides/workspace-management.md:111 still directs readers to the top-right Actions dropdown. This creates an internal mismatch for anyone following the documented UI steps, so update the prose to use the current label alongside this screenshot.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Fair enough... @matifali I am not one for writing good human understanding words can you validate this please 🙂 |
…atic-updates screenshots
Documentation CheckUpdates Needed
Automated review via Coder Agents |
I would leave this to @nickvigilante |
nickvigilante
left a comment
There was a problem hiding this comment.
Screenshots LGTM. I think I want to establish some mechanism, either with Pixel or something else, to collect screenshots automatically and standardize the sizing and whatnot. I'll have to ponder this and get back to you, but these are ready to merge now 
🚀
Refreshes the six stale screenshots on the Workspaces page (
docs/user-guides/workspace-management.md) with the current Coder UI, recreating equivalent dummy data (matching template and workspace names) so the images stay recognizable.Linear: DOCS-55
Updated images
creating-workspace-ui.pngworkspace-update.pngworkspace-automatic-updates.pnguser-guides/workspace-bulk-actions.pngschedule.pngtemplates/template-variables.pngProse is unchanged; this is a screenshot-only refresh.
Notes / limitations
The originals came from production-like deployments with AWS/Azure/Kubernetes templates, multiple users, and aged data. These were reproduced on a local
scripts/develop.sh(Docker) instance, so:use_kubeconfig=True/namespace=default, and the auto-update =Alwayssetting all match.0 developers, build times showUnknown, the connection-latency pill has no value, and the workspace name field is disabled by the template.How these were produced (decision log)
Followed the
dogfoodskill:./scripts/develop.sh(v2.36.0-devel, matching the docs version).data-warehouse,analytics,api-services,frontend-web,pod-share-jupyter,aws-linux-ephemeral,azure-aks-pod, pluskubernetes2("Develop in Kubernetes"). The JetBrains module was dropped from the Docker template to avoid a plan-time error;kubernetes2uses a Coder-only variant declaring the realnamespaceanduse_kubeconfigvariables so it imports withuse_kubeconfig=true.admin/my-frontend(outdated → update available, with a schedule),admin/dev(auto-update = Always), andkirby/{data-science, aws-large, azure-space, ephem-demo (Failed), kirbs (Stopped)}.::beforehazard stripe, and the-develversion chip) and cropping settings pages to the form. Images are 2x for crispness.