As a result of extending functionality so that posts can be written by users, we have less control over the image size/dimensions of uploaded images.
Cloudinary CAN help resolve this, but the current situation is that on index.html, either the:
Articles Align at the bottom but the pictures are distorted, OR Articles don't Align at the bottom but the pictures are scaled correctly.
Cloudinary functionality needs to be investigated to facilitate: Articles Align at the bottom AND the pictures are scaled correctly.
I've opted for the more obvious UX impact by ensuring the pictures are scaled correctly.
I tested this with css code which is deliberately commented out in case you would like to see the impact
I need to seek UX advice from Users and Dev Experts to move forward on how to fix this. The complexity is greater because we're using pagination. CSS decisions would be impacted IF pagination in blog.views.py changed:
OR
DTL was changed - {% if forloop.counter|divisibleby:3 %} in blog.index.html
As a result of extending functionality so that posts can be written by users, we have less control over the image size/dimensions of uploaded images. Cloudinary CAN help resolve this, but the current situation is that on index.html, either the: Articles Align at the bottom but the pictures are distorted, OR Articles don't Align at the bottom but the pictures are scaled correctly.
Cloudinary functionality needs to be investigated to facilitate: Articles Align at the bottom AND the pictures are scaled correctly.
I've opted for the more obvious UX impact by ensuring the pictures are scaled correctly. I tested this with css code which is deliberately commented out in case you would like to see the impact
I need to seek UX advice from Users and Dev Experts to move forward on how to fix this. The complexity is greater because we're using pagination. CSS decisions would be impacted IF pagination in blog.views.py changed:
OR
DTL was changed - {% if forloop.counter|divisibleby:3 %} in blog.index.html
