Add Atlas Cropper documentation

[justkahdri]

Summary

Added comprehensive documentation for the Atlas Cropper tool, a browser-based visual utility for defining, arranging, and extracting crop regions from atlas images.

Changes

• Created new documentation file (content/logs/13-atlas-cropper.mdx) with complete feature overview and usage guide
• Documented the four-tab workflow: Crop Definition, Layout Arrangement, Output, and UV Crop
• Included keyboard shortcuts and quality-of-life features reference table
• Provided JSON output format example
• Explained the tool's purpose and differentiation from general-purpose design tools

Key Sections

• Problem statement — addresses the pain point of manual atlas cropping workflows
• Workflow documentation — detailed breakdown of each of the four sequential tabs with feature lists
• Keyboard shortcuts — comprehensive reference table for power users
• Output format — example JSON structure for crop configurations
• Rationale — explains why this tool is better suited than Photoshop/Figma for atlas workflows
• Links — reference to GitHub repository

The documentation is structured to serve both as an introduction for new users and a reference guide for existing ones.

https://claude.ai/code/session_018ausLaQNYXDo46Tb2mzC5Q

Greptile Summary

Adds a new log entry documenting the Atlas Cropper browser tool, covering its four-tab workflow, keyboard shortcuts, JSON output format, and rationale. The content is well-written and consistent with the existing log format — no meta.json is needed for this section as the logs directory uses auto-discovery (no content/logs/meta.json exists for any of the 12 prior entries).

Confidence Score: 5/5

Safe to merge — only a static documentation file with no logic or security surface.

Single MDX file addition with no functional code changes. The one P2 finding (commented-out TODO) is cosmetic and doesn't affect rendering or functionality.

No files require special attention.

Vulnerabilities

No security concerns identified. This PR adds only static MDX documentation content with no code execution paths.

Important Files Changed

Filename	Overview
content/logs/13-atlas-cropper.mdx	New documentation page for Atlas Cropper tool; content is well-structured and complete, with only a commented-out TODO section remaining as a minor concern.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: content/logs/13-atlas-cropper.mdx
Line: 102-106

Comment:
**Uncommitted TODO left in published content**

The commented-out `## Our use case` section contains an explicit TODO marker and is still included in the file. Even though it's wrapped in an MDX comment block and won't render to users, it signals unfinished work checked into the main branch. Consider either removing the block entirely until the content is ready, or tracking it as a separate issue/task so it doesn't silently persist.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "add atlas-cropper log entry draft" | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
joyco-hub	Ready	Preview, Comment	Apr 13, 2026 8:53pm

[greptile-apps]

Uncommitted TODO left in published content

The commented-out ## Our use case section contains an explicit TODO marker and is still included in the file. Even though it's wrapped in an MDX comment block and won't render to users, it signals unfinished work checked into the main branch. Consider either removing the block entirely until the content is ready, or tracking it as a separate issue/task so it doesn't silently persist.

Prompt To Fix With AI

This is a comment left during a code review.
Path: content/logs/13-atlas-cropper.mdx
Line: 102-106

Comment:
**Uncommitted TODO left in published content**

The commented-out `## Our use case` section contains an explicit TODO marker and is still included in the file. Even though it's wrapped in an MDX comment block and won't render to users, it signals unfinished work checked into the main branch. Consider either removing the block entirely until the content is ready, or tracking it as a separate issue/task so it doesn't silently persist.

How can I resolve this? If you propose a fix, please make it concise.