pouët.net

I agree with raer and psonice

gargaj: not at all, it just was a pretty rough time for me andI had to reduce my exposure to other projects etc.. to concentrate on what was at hand

knos: yeah i thought so - hope it's better now either way :)

yes indeed things are good now, but it took a whole year and a half

I just discovered that Pouet has a mobile version! http://m.pouet.net/

This is brilliant.

However I have a problem :( I discovered this by random as Pouet doesn't behave responsively based on the device. I'm using an iPhone and by default I get served with the desktop version.

If a simple solution for Pouet to check the device resolution? If device resolution < X then display mobile content otherwise display desktop sized content ?

or just type in m.pouet.net? or is that too difficult for iphone?

Thanks for the smart ass comment but your missing the point,on purpose perhaps.

Serving content based on device resolution is the established best practice in responsive design. Its also a damn nice user experience.

Pouet is almost there.

a javascript check to forward to m.pouet.net if device is mobile could easily be added, but then i'm sure someone on a mobile device with a decent connection and large enough scren at some point would rather have the standard site and not the mobile version and complain about the auto forward. a popup confirming the forward and saving in cookie session could work.

but i really think people just use m.pouet.net by default when they want the mobile version. it's standard on most sites that the mobile version is prefixed with the m.

You seem to know a bit about web design. Go ahead and submit a pull request to pouet's source code, adding a <meta name="viewport"content="width=device-width,initial-scale=1"/> and fixing switching the #content and .column selectors to use flexbox or to floats with a min-width if you prefer some oldschool deprecated technique.

p01, I'm not an expert but I don't believe a pull request will solve this as the mobile content isn't displayed unless you explicitly know about this m. parallel subdomain.

My 2 cents would be to do a server side redirect 302 based on the user agent/device resolution.

The alternative as psenough pointed out is to do the redirect in JS.

Whatever way it's done, the objective here is to better the Pouet user experience.

My 2 cents are that this is not a JS or redirect issue.

Forcing the left and right columns to 22% without a media query, as it is done on the www. layout, is wishful thinking. Not throwing a brick at anyone there; the web landscape has changed significantly in recent years.

IMO, there should be ONE layout, and the m. one seems like a better start. It needs a bit of media queries or simply flexbox with max-width on the columns to work well on small and bigger screens.