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
Currently the homepage renders in a way that is not expected on mobile devices.
I do not 100% know whether the project aims to support mobile devices, so not sure whether you consider it an issue. In general, it is a recommended practice to ensure websites work with mobile devices these days, given that many people end up using it this way.
Wanted to flag this in case you are not yet aware of this.
The text was updated successfully, but these errors were encountered:
Yes, I noticed this last night ... I'm not sure if it's the column div rendering or what?
I know the rest of the site is somewhat awkward on mobile, so I think our (longer) term plan was to create a separate mobile version for smaller screens that was significantly paired down. Do you see what's causing the issue on this page though? I will also investigate (and can probably leave a note on the page about future plans so people are aware).
It's the combination of the flex and justify-content at the moment. Generally, the CSS may need a good solid pass to ensure things display as expected (if there are articulated expectations).
Honestly, I get that you say you want to create a separate mobile version and I bet this will lead to a frustrating UX for folk. It is not an unreasonable expectation that things work this way and you cannot prevent it. Maybe not for end of October, but for the first complete version 👍
Currently the homepage renders in a way that is not expected on mobile devices.
I do not 100% know whether the project aims to support mobile devices, so not sure whether you consider it an issue. In general, it is a recommended practice to ensure websites work with mobile devices these days, given that many people end up using it this way.
Wanted to flag this in case you are not yet aware of this.
The text was updated successfully, but these errors were encountered: