Urgent.News

What's breaking now, across hundreds of outlets.

Tech

Change a screenshot to the required aspect ratio in the tab before you commit the hero

The docs call for a 16:9 hero, or the OG template is 1200×630. The file in the PR is a 4:3 laptop screenshot. The layout letterboxes it, or a later object-fit: cover chops off the toolbar you meant to show. Nobody looked at the ratio before the file landed in git. I’ve started treating the required aspect ratio as a first check , not as something the CSS can paper over. Resize and compression are…

The documentation specifies that a hero image should be in a 16:9 aspect ratio, with the original template dimensions being 1200×630 pixels. However, a recent pull request (PR) contains a 4:3 laptop screenshot that was uploaded into the wrong aspect ratio. The layout team letterboxed the image, or used object-fit: cover, which chopped off the toolbar that was intended to be displayed.

Nobody checked the aspect ratio before the file was committed to the git repository. The reporter has started treating the required aspect ratio as an initial check, rather than relying on CSS to compensate for the wrong ratio. The resizing and compression steps should come after ensuring the correct aspect ratio.

If the frame is incorrect, the resulting crop will be flawed. Resizing a 4:3 screenshot to a 16:9 ratio will not solve the issue, as the captured image will still be in a 4:3 format. The layout team requested a 16:9 ratio for README heroes, OG images, changelog screenshots, and store listing frames with published dimensions. When an in-tab ratio adjustment is sufficient, the captured image should match the target ratio.

If the captured image is almost correct but requires cropping or containing within a canvas, it is necessary to visualize the cover vs. contain options before committing the file. Poor fits include product photos with a real art-direction crop in Figma, screenshots that need to show specific controls that would be cut off by cover cropping, or images already produced by the design team’s export preset.

If the content cannot fit the ratio without losing crucial information, the layout requirement should be modified, or a tight crop combined with a wider shot should be attached. The solution should avoid stretching the pixels. The reporter emphasizes the importance of knowing the target ratio before capturing the image, whether it be for the documentation template, OG size, or component preview.

Prefer capturing an image that already matches the required ratio, followed by cropping or containing it within a canvas. Do not stretch a 4:3 screenshot to fit a 16:9 ratio. After setting the correct ratio in the tab, attach the file for review.

A helpful local tool can set the desired aspect ratio (16:9, 1:1, 4:3, or a custom size) and choose between cover, contain, or stretch options while downloading the result. This avoids uploading potentially sensitive customer data to a server. If the screenshot is already on disk, use an in-tab ratio tool to adjust the image without sending it to a server.

Uwarp's aspect ratio changer is a browser-based tool that offers cover, contain, or stretch options for common ratios, allowing you to judge the crop before sharing the file.

If the team already has a Figma export or an export pipeline with a fixed frame for product releases, use that source for images that will be shipped in the product. When stretching a screenshot to match the required ratio is the only solution, ensure that the text and UI elements do not become distorted or circular avatars lose their intended appearance.

To maintain the evidence of a layout bug, crop the screenshot so the bug remains in view, even if that means using a different aspect ratio and noting the change in the pull request.

When rejecting a screenshot, do not send it back with only a cover-fit fix. Stretching the capture to match the numbers or uploading a screenshot that may contain production data without proper protection is not acceptable. Accept a hero or OG image that already matches the required ratio, or a contain-on-canvas still that maintains the whole frame's visibility. Similarly, accept a design-export file that came directly from the intended template, rather than a hurriedly resized version.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at dev.to →

Report a problem with this story

More in Tech

A Japanese NLI checker for the space between generation and trust (sealed 0.961, zero-shot baselines 0.79–0.81)

TL;DR — We released ja-nli-v1, a small Japanese natural language inference model: given a premise and a hypothesis, it returns probabilities for entailment / neutral / contradiction.

  • ja-nli-v1 Japanese NLI model achieves 0.9612 accuracy on sealed test
  • Outperforms zero-shot baselines with 0.79–0.81 accuracy
  • Model trained on synthetic data from public-domain government documents

Why Small Teams Need CI/CD (and How to Set Up Your First Pipeline)

It is a common myth among small engineering teams that CI/CD pipelines are an enterprise luxury. When you only have two or three developers, setting up automated infrastructure can feel like…

  • CI/CD automates testing and deployment, reducing manual errors
  • Small teams can set up CI/CD with simple steps, not complex systems
  • Automated pipelines catch bugs early, freeing developers for feature work

Same Character, 25 Clips: How ULTRA Was Made

Originally published on the Character Lock blog . ULTRA is a 3-minute AI brand film (3:13) with one bear dad holding across more than 25 clips.

  • ULTRA is a 3-minute AI brand film with 25 clips of a bear dad.
  • Character Lock method ensures consistent character appearance across 25 clips.
  • Film achieved LUFS master of minus 14, demonstrating Character Lock method effectiveness.

How I Automated 10M+ Network KPI Records a Day with Python and Apache Airflow

Originally published on pmpdilshan.github.io . Every hour, a mobile network generates performance counters for every cell: traffic, drops, handovers, throughput, congestion.

  • Mobitel generates over 10 million network KPI records daily
  • Automated pipeline using Python and Apache Airflow reduces effort by 40%
  • Automation frees up time for optimization work and KPI centralization

More from Saturday 21 November →