Description of the need
In the discussion of https://github.com/backdrop/backdrop-issues/issues/4903 it has been suggested that our default view of the new card content type would work much better if CORE provided a default image style that is cropped to specific dimensions to provide a more consistent display in views. Originally, we had added a new "cropped" image style to that PR to specifically to address this problem. BUT, this generated a debate over several different approaches, see below.
NOTE: The current thinking is that this issue is NOT a blocker for #4903 and can be addressed at a later date (either in this coming release or in future releases).
Additional information
This issue is largely a duplicate of #5590 - except that this issue is focused on a solution to the very specific problem raised by issue #4903 - while issue #5590 is intended to address a broader set of issues beyond those in issue #4903.
Proposed solution
Let's use this issue to decide which direction folks would like us to go:
1) Update all our default image styles to address this issue as well as other problems with the default image styles (https://github.com/backdrop/backdrop-issues/issues/5590) - close this issue and work on that PR. 2) Create a single new image style that is cropped and works for our view of Cards on front page - leaving the larger issues in #5590 for future. 3) Update ONLY the large image style (add cropping) specifically to address this issue. 4) Do nothing - and just let site architects create their own image styles.
Are we missing any other alternatives?
Recent comments
Graham Leach: Has anyone got any experience with the assets in this area of Backdrop CMS? filetransfer.inc ftp.inc local.inc ssh.inc If you do, I'd love to chat with you... Graham...
Jan 16th 2025 Weekly Meetings
I've been building Backdrop sites since 2021 with the first being my own: https://www.systemhorizons.co.uk/ Two over time for one client: https://www....
Happy Birthday Backdrop CMS - Share your projects!
Hi Tim. Yes I think at the moment it needs custom code. Depending where you want the class it could be either: /** * Implements hook_preprocess_page(). */ function theme_name_preprocess_page...
How to make clear to editor if they are on a revision?