Skip to content

[JUM-896][Feature] Current product screenshots and a "See it running" tour - #542

Merged
web2solutions merged 5 commits into
devfrom
claude/feature/JUM-896-product-screenshots
Sep 27, 2026
Merged

web2solutions merged 5 commits into
devfrom
claude/feature/JUM-896-product-screenshots

Conversation

@web2solutions

@web2solutions web2solutions commented Sep 26, 2026 •

Copy link
Copy Markdown
Owner

Summary

The website now shows six current product screenshots instead of one image from 2026-07-26: Domain Designer, Architecture Designer, OpenAPI/Swagger, Code Workspace, the frontend dashboard, and the X-CRUD Users grid. The Product page opens with a "See it running" tour of all six; the homepage keeps the Domain Designer shot with an accurate caption. Every image is produced by one script (bun run --filter @jumentix/website screenshots:capture) with fixed framing (WebKit, 1440x900 CSS px @2x, dark scheme), so a refresh is a command, not a manual session.

Problem Statement

apps/jumentix-website/public/product/ held one file, domain-designer.png (last touched 2026-07-26 per git log -1 --format=%cs -- apps/jumentix-website/public/product/domain-designer.png), captioned "The real Jumentix Domain Designer interface". It predates the architecture designer, the Swagger tab, and the X-CRUD frontend, so the site showed a product that no longer exists.

Project Tracking (Required)

Branch Promotion Path (Required)

  • Source branch: claude/feature/JUM-896-product-screenshots
  • Target branch: dev
  • Required PR title format: [JUM-XXXX][Nature] <concise outcome>
  • The leading JUM-XXXX matches the single Linear Issue declared above.
  • This task PR targets dev.
  • If this PR targets main, it is a release promotion sourced from dev, references the task PRs/issues already merged into dev, and introduces no unreviewed changes.
  • This PR is not a direct task/topic branch promotion to main.

Bidirectional Traceability (Required)

  • Every linked issue already contains this PR URL.
  • Every linked issue already contains commit hash/range evidence.
  • PR description includes mapping of task -> commit(s).
  • Task -> commit(s) mapping:

Scope of Change

Domain / Business Rules

  • None.

Application / Use Cases

  • None.

Adapters / Infrastructure

  • apps/jumentix-website/public/product/{domain-designer,architecture-designer,openapi-swagger,code-workspace,frontend-dashboard,frontend-xcrud-users}.png (2880x1800).
  • apps/jumentix-website/components/commercial/CommercialPages.tsx: productTour + ProductTourBand (EN/PT captions and alt text); homepage caption corrected.
  • apps/jumentix-website/scripts/capture-product-screenshots.mjs + screenshots:capture script.
  • documentation/md/COMMERCIAL-EXPERIENCE.md (+ pt-BR): Product Proof section documents the capture command and prerequisites.

API / Contracts (OpenAPI, DTOs, handlers, controllers)

  • None.

Detailed Technical Changes

Captured 2026-09-26 against the running apps with the JUM-905 (architecture canvas), JUM-906 (breadcrumb) and JUM-907 (Swagger UI 5 for OAS 3.1) fixes applied, because capturing exposed those three defects; each has its own PR. The multitask shell is not visually distinct from the dashboard at this viewport, so it has no dedicated shot. The starter-template PNG was already retired by #536. Known gap outside this Issue: the dashboard shows organization UUIDs where names belong (recorded on JUM-906).

Architecture and Design Alignment

  • Domain logic remains inside domain/application layers.
  • Controllers/handlers do not instantiate repositories/services directly.
  • Ports/adapters boundaries are respected.
  • No new circular dependencies introduced.
  • Event publishing/listening flow remains consistent.

Security Impact

  • Security impact: No security impact.
  • Secrets handling reviewed: [ ] Yes [ ] No [x] N/A
  • Input/output sanitization reviewed: [ ] Yes [ ] No [x] N/A
  • AuthN/AuthZ impact: [ ] Yes [x] No
  • Data exposure risk (password/salt/token/PII): [ ] Yes [x] No
  • Sonar security findings addressed or unaffected: [x] Yes [ ] No

Data and Migration Impact

  • Data model impact: none.
  • Migration required: [ ] Yes [x] No
  • Rollback strategy: revert the PR.

Breaking Changes

None.

Acceptance Criteria

  • Feature/bug behavior matches expected functional outcome.
  • Error paths and edge cases are covered.
  • API contract changes (if any) are documented and validated.
  • Architecture boundaries remain enforced.
  • No regression in existing workflows.

Test Plan (Evidence)

  • bun run --filter @jumentix/website test:unit — Tests: 288 passed, 288 total (pre-commit gate)
  • bun run test:unit — Tests: 1159 passed, 1159 total (pre-commit gate)
  • node apps/jumentix-website/scripts/capture-product-screenshots.mjs — six images written

Extra evidence:

ls apps/jumentix-website/public/product
architecture-designer.png code-workspace.png domain-designer.png frontend-dashboard.png frontend-xcrud-users.png openapi-swagger.png

Feedback Resolution (Required)

  • Every GitHub review thread is resolved natively.
  • Every general comment has a visible resolution response by the PR author or a repository maintainer.
  • Each resolution response uses exactly one marker and, for resolved, a SHA from this PR.

Coverage

  • Project coverage >= 95%: [x] Yes [ ] No
  • Patch coverage >= 95%: [x] Yes [ ] No
  • Codecov status passing: [ ] Yes [ ] No (pending CI)

SonarQube Cloud

  • Quality Gate passing: [ ] Yes [ ] No (pending CI)
  • New vulnerabilities introduced: [ ] Yes [x] No
  • New security hotspots reviewed: [ ] Yes [ ] No [x] N/A

Performance / Reliability Impact

No measurable impact.

Observability

  • Logs updated: [ ] Yes [x] No
  • Metrics/Tracing updated: [ ] Yes [ ] No [x] N/A

Deployment and Rollout

  • Deployment notes: none.
  • Feature flag needed: [ ] Yes [x] No
  • Rollout strategy: merge to dev, promote with the next release.
  • Rollback steps: revert the PR.

Risks and Mitigations

  1. Risk: none material.\n Mitigation: n/a.

Documentation Updates

  • README updated (if needed)
  • Additional docs updated (if needed)
  • Changelog untouched; GitHub Actions synchronizes it only after the validated main merge

Reviewer Checklist

  • Changes are clear and scoped.
  • Acceptance criteria are testable and satisfied.
  • Tests are sufficient for risk level.
  • Security and data impacts are addressed.
  • CI checks pass fully.

🤖 Generated with Claude Code


Note

Low Risk
Changes are limited to marketing UI, static assets, and a local-only capture script; no API, auth, or runtime behavior changes in production.

Overview
The Product page now opens with a bilingual "See it running" tour: six lazy-loaded captures (architecture, domain modeling, OpenAPI, code workspace, admin CRUD, dashboard) in a responsive two-column grid, with copy stating they are real app screenshots—not mockups. The homepage Domain Designer caption is updated to match.

A new screenshots:capture script drives capture-product-screenshots.mjs, which uses Playwright WebKit (1440×900 @2×, dark scheme) against running Service Management and frontend dev servers to refresh everything under public/product/ in one repeatable command. COMMERCIAL-EXPERIENCE docs (EN/pt-BR) describe prerequisites and env vars (FRONTEND_USERNAME / FRONTEND_PASSWORD).

Reviewed by Cursor Bugbot for commit 69dd69e. Bugbot is set up for automated code reviews on this repo. Configure here.

JUM-896. Replace the July Domain Designer capture and add five more from the
running apps: architecture designer, OpenAPI tab, code workspace, and the
frontend's admin list and dashboard. The product page opens with a tour of the
six; the homepage caption no longer claims "the real interface" of a screen
that had changed. scripts/capture-product-screenshots.mjs (bun run --filter
@jumentix/website screenshots:capture) regenerates all of them with fixed
framing; COMMERCIAL-EXPERIENCE (EN + pt-BR) documents it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@cursor

cursor Bot commented Sep 26, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_36129962-e5ae-4cb0-a709-07fe4b58956a)

@cursor

cursor Bot commented Sep 26, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_3ac79ee0-7f25-47f8-8723-9312cbc5c312)

@cursor

cursor Bot commented Sep 27, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_4bb36a61-52e8-4c9e-8a25-e813c39b17ec)

@cursor

cursor Bot commented Sep 27, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_0ce4371d-8fc8-4291-a3f2-607a4e6a7274)

@cursor

cursor Bot commented Sep 27, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_aad2c4c0-d528-42e8-8cb9-0189ad3160b1)

@web2solutions
web2solutions merged commit d63ebe2 into dev Sep 27, 2026
36 of 37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant