4 ms·

I accept that some people don't know how, or don't want to dedicate the time to making a responsive site. I get that, I have sites that don't make sense in mob

by keedot 11y ago

I accept that some people don't know how, or don't want to dedicate the time to making a responsive site. I get that, I have sites that don't make sense in mobile, so we don't bother with a mobile design. But don't take away the ability to zoom on mobile if you don't. You lose a good portion of your audience.

xigency 11y ago
Try refreshing the page. The site is hosted on GitHub pages and I used a template. I found this tag in the HTML <meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no"> And changed it to <meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=yes">
- sunilkumarc 11y ago
  The page is not responsive. Hosting on Github pages doesn't mean the web page will be responsive. It depends on the template you have used which is not responsive apparently.
  - xigency 11y ago
    Yeah, I'm not a UX guy, I'm a programmer. It's plaintext rendered with HTML. The <meta> tag above prevented scaling on WebKit phones. I don't really believe in using templates or overlays because I'm afraid of them interfering with usability, disabling the ability of a viewer to read the text, or being distracting. If you are interested in the content I've posted, you would be best off printing it out and reading it. It's probably easier on the eyes.
    - acqq 11y ago
      You still have widths expressed in pixels which still limits the chance of your text being readable on some smaller devices. At least I can report that your page is fully readable using Safari on iPhones in the "reader mode" (which avoids all the original formatting of the page).
  - girvo 11y ago
    xigency didn't say it was responsive, merely that the template they were using is disabling user scrolling by default, which they have said is now fixed.
  - posnet 11y ago
    He was responding to the fact that user zooming was disabled and that he changed it so it works now.
- keedot 11y ago
  Much better, thank you!

by keedot 11y ago

xigency 11y ago

Try refreshing the page. The site is hosted on GitHub pages and I used a template. I found this tag in the HTML <meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no"> And changed it to <meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=yes">

sunilkumarc 11y ago
The page is not responsive. Hosting on Github pages doesn't mean the web page will be responsive. It depends on the template you have used which is not responsive apparently.
- xigency 11y ago
  Yeah, I'm not a UX guy, I'm a programmer. It's plaintext rendered with HTML. The <meta> tag above prevented scaling on WebKit phones. I don't really believe in using templates or overlays because I'm afraid of them interfering with usability, disabling the ability of a viewer to read the text, or being distracting. If you are interested in the content I've posted, you would be best off printing it out and reading it. It's probably easier on the eyes.
  - acqq 11y ago
    You still have widths expressed in pixels which still limits the chance of your text being readable on some smaller devices. At least I can report that your page is fully readable using Safari on iPhones in the "reader mode" (which avoids all the original formatting of the page).
- girvo 11y ago
  xigency didn't say it was responsive, merely that the template they were using is disabling user scrolling by default, which they have said is now fixed.
- posnet 11y ago
  He was responding to the fact that user zooming was disabled and that he changed it so it works now.
keedot 11y ago
Much better, thank you!