You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've observed that the comparison tables on the packages page are quite wide and can be challenging to navigate, particularly on devices with smaller screens. I believe that transposing the tables—switching rows for columns and vice versa—could significantly enhance the user experience by allowing for a better overview and comparison between packages without the need for horizontal scrolling.
I believe that by transposing the tables, not only will readability be improved, but it will also likely increase the visibility of individual packages. This enhanced visibility could potentially lead to greater growth and engagement metrics for packages that might otherwise be overlooked due to the current table format.
Thank you for considering this improvement. I am willing to assist in any way I can to implement this suggestion.
The text was updated successfully, but these errors were encountered:
@aperezlillo thank you for the feedback. Can you take a look at #646 and let us know if this request is different than that? This seems to be the same issue, but wanted to verify.
Hi Django Packages team,
I've observed that the comparison tables on the packages page are quite wide and can be challenging to navigate, particularly on devices with smaller screens. I believe that transposing the tables—switching rows for columns and vice versa—could significantly enhance the user experience by allowing for a better overview and comparison between packages without the need for horizontal scrolling.
I believe that by transposing the tables, not only will readability be improved, but it will also likely increase the visibility of individual packages. This enhanced visibility could potentially lead to greater growth and engagement metrics for packages that might otherwise be overlooked due to the current table format.
Thank you for considering this improvement. I am willing to assist in any way I can to implement this suggestion.
The text was updated successfully, but these errors were encountered: