The Normalized Image Styles module provides 20 sets of aspect ratio based image styles with normalized dimensions. These sets of image styles can be used by the core Responsive Image module as part of your site performance strategy.

Each set contains 17 normalized base widths (in pixels):

  1. 3840
  2. 3328
  3. 2944
  4. 2560
  5. 2176
  6. 1920
  7. 1664
  8. 1408
  9. 1152
  10. 1024
  11. 896
  12. 768
  13. 640
  14. 512
  15. 384
  16. 256
  17. 128

The height for each image style is a function of the aspect ratio (width / aspect ratio, rounded down).

Normalized Image Styles uses the Image Style Generate module to generate the image styles for each aspect ratio. After enabling the base module and any desired aspect ratios, you need to run the migration import process.

Once imported, Normalized Image Styles and all of its sub-modules can safely be uninstalled on the module Uninstall page. The generated image style configuration will persist and can be managed on the configuration Synchronize page or via Drush commands.

Similar projects

Easy Responsive Images
Has the added benefit of generating media image view modes and responsive image styles for each aspect ratio you define. Currently employs a javascript based mechanism using data- attributes for swapping images rather than using native browser behavior.

Project link

Normalized Image Styles

Comments

UpTil4Music created an issue. See original summary.

apaderno’s picture

apaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
CreditAttribution: apaderno as a volunteer commented

Thank you for applying!

Please read Review process for security advisory coverage: What to expect for more details and Security advisory coverage application checklist to understand what reviewers look for. Tips for ensuring a smooth review gives some hints for a smoother review.

The important notes are the following.

  • If you have not done it yet, you should run phpcs --standard=Drupal,>DrupalPractice on the project, which alone fixes most of what reviewers would report.
  • For the time this application is open, only your commits are allowed.
  • The purpose of this application is giving you a new drupal.org role that allows you to opt projects into security advisory coverage, either projects you already created, or projects you will create. The project status will not be changed by this application; no other user will be able to opt projects into security advisory policy.
  • We only accept an application per user. If you change your mind about the project to use for this application, or it is necessary to use a different project for the application, please update the issue summary with the link to the correct project and the issue title with the branch to review and the project name.

To the reviewers

Please read How to review security advisory coverage applications, Application workflow, What to cover in an application review, and Tools to use for reviews.

The important notes are the following.

  • It is preferable to wait for a Code Review Administrator before commenting on newly created applications, even to leave a comment similar to the following one. Code Review Administrators will do some preliminary checks that are necessary before any change on the project files is suggested.
  • It is also preferable to wait before using a CLI tool to report what needs to be changed, especially because the comment left from Code Review Administrators suggests to use PHP_CodeSniffer. Before that, manual reviews should be done.
  • Reviewers should not copy-paste the output of a CLI tool. They should use a CLI tool only once per application. When they do that, they should later verify the code has been correctly changed; this means, for example, that adding a documentation comment that is not correct just to avoid to get a warning/error is not a correct change that should be reported in a further comment.
  • It may be best to have the applicant fix things before further review.

For new reviewers, I would also suggest to first read In which way the issue queue for coverage applications is different from other project queues.

apaderno’s picture

apaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
CreditAttribution: apaderno as a volunteer commented
Status: Needs review » Needs work

Usually, after reviewing a project, we allow the developer to opt projects into security advisory coverage. This project is too small for us and it doesn't contain enough PHP code to really assess your skills as developer.

Have you created any other project on drupal.org (module, theme, distribution) we could instead review? The project needs to have most of the commits (preferable all the commits) done by you.

apaderno’s picture

apaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
CreditAttribution: apaderno as a volunteer commented
Status: Needs work » Closed (won't fix)

I am closing this application since there have not been replies to my previous comment, where I asked for a different project to use for the application, after more than five weeks.