Navigation
This is archived content. Visit our new forum.

Tagged: 

  • Author
    Posts
  • #1125457
    Misho
    Participant

    Hi,

    I’d say there is an UX problem with Icon stack.

    When we click on the blog index page, we see an order of the posts (in standard style, not masonry).

    Like this: http://www.mojemalozlato.com/blog/.

    But when we click the first visible post, the layout stays exactly the same. for example:

    Kontaminacija glutenom

    This confuses the users, because when they change a page, they expect to see something different.

    This can be solved with CSS, to introduce some differences between index and single blog header, but I think this should be addressed by default.

    2.

    Masonry style often doesn’t look neat, because the position of the posts on the Index page is depending on the length of the titles. I think there should be an option in the Customizer to align the columns horizontally, no matter the title length.

    Thanks!

    #1125709
    Rupok
    Member

    Hi there,

    I understand what you are saying but isn’t it expected? If you need to make some difference; you can use different background, font-size etc. for the blog page or for the single posts. Also if you really consider UX, it’s actually more UX friendly since most of them click on the read more link to read more content and it loads the content without changing he view which is more consistent in terms of design. However we have different stack with different design and choice are subjective. So you can either change the design a bit for blog page and post or choose another stack. Same goes for the masonry layout as it’s also pretty expected. If you are trying to show something different; there is always scope of adding custom CSS or modifying the templates with Child Theme.

    Hope this makes sense.

    Cheers!

    #1125755
    Misho
    Participant

    Thank you for your answer, Rupok.

    I agree that this can be solved with CSS. I don’t have a problem with that. But I was more talking in the name of the average site owner who wouldn’t even notice this, while the users would.

    The “Read more” button doesn’t exist on Icon stack blog index, which makes the issue bigger.
    The reason you see it on the blog is because I have added it there.

    Finally, my observation is based on live user testings of the blog I have linked to. Eight patricipants out of ten have stuck waiting for something to happen once they clicked the top post title, not realizing that they are on the new page and they can start scrolling down to read the article.
    Some of them have been waiting for a few seconds, and some of them have even started to click the title/image again, thinking that nothing happened.

    That is by definition a UX problem. 🙂

    #1126025
    Rupok
    Member

    Thanks for your feedback. If users face trouble then certainly it could be improved. I think a bit different size would make the difference. I’ll forward this to our developer so that they can assess this and improve in future. Again thanks for your feedback.

    Have a nice day!

  • <script> jQuery(function($){ $("#no-reply-1125457 .bbp-template-notice, .bbp-no-topic .bbp-template-notice").removeClass('bbp-template-notice'); }); </script>