vidyesh 2 days ago

That blog needs some inline padding for mobile view.

Reply View 5 replies
  • dongcarl 2 days ago

    (Carl from Obscura here)

    You’re absolutely right, we fixed it and forgot to push to prod XP

    Reply View 1 reply
    • vidyesh 2 days ago

      Hey Carl, good to know is already fixed! While you are at it, please setup wildcard redirects too. Instinctively, I went to /blog assuming it would be a blog page but it isn't.

      Reply View 0 replies
  • gchamonlive 2 days ago

    And it's not even that hard if the page is built in a sane way, which for the simplicity of the blog should be a no brainer to go for simplicity.

    I have my blog hosted at omg.lol and while I had to support mobile by myself, it was really really simple.

    Here is my blog: https://xd1.dev

    Here is the code for the blog's responsive layout: https://github.com/gchamon/xd1.dev/blob/main/css/responsive-...

    No injection, no build, just plain inline linking https://github.com/gchamon/xd1.dev/blob/10b98ddb37a9786ca8fe...

    Reply View 0 replies
  • 0xEF 2 days ago

    It's insane to me that this even has to be pointed out with such a relatively simple page, and then I looked at the source; it screams "I'm gonna just bang something out in [popular framework] without knowing basic HTML/CSS and let the world suffer from my <div> rot."

    I hate modern web development.

    Reply View 1 reply
    • vidyesh 2 days ago

      I agree. Its not that difficult to just have a max-width of 90% for the content or just add some padding to the inner container.

      I also think people skipping over learning some basic CSS fundamentals also end up skipping over basic UI/UX needed for accessible websites, something every web developer should have some awareness about.

      Complete reliance on CSS frameworks does not magically make the websites accessible,it gets you 90% there.

      Also /blog leads of 403!? Wildcard redirects are not that difficult to setup either.

      Reply View 0 replies