![]() Var s = document.getElementsByTagName('script') s.parentNode.insertBefore(ga, s) Var ga = document.createElement('script') ga.type = 'text/javascript' ga.async = true Just make sure it points to the right file, and the file exists in that location. You might have to hard-code it or use a different WP function. Or whatever the path to your theme directory is. It would instead be something like this: /js/"> If it’s a WordPress theme, then you have to make sure the script is inside the correct folder, and you reference it correctly.īut that’s not correct for a WP theme. That would be less clicking and maybe more intuitive if done right. A better plan might be to let hover select the slide when you hover over a title and clicking the title on the left goes directly to the article. first you click on the tab to get the slide photo and page link, then you have to look for the mouse, move the mouse to the correct link for the page featured in the slide, then click on the page link. One related problem that always bothers me with this sort of slideshow is that you have to click twice to get to a news article. in my opinion simply mousing over the text with a hover intent delay should be enough to switch slides since it indicates the user is focused on a particular slide earlier and easier then clicking. If you satisfied with users having to stop looking at the content to track the movement of the mouse to the correct slide then you don’t need the next and previous buttons.Īlso there’s a slight confusion over when do we switch slides. A fixed position next and previous button allows the user to position their mouse over the next button and then focus visually on the photo or headline while clicking quickly. quickly or at a speed of their choosing this should be doable without having to look at the mouse pointer and focus on moving the pointer to the next location. I would possibly recommend adding a next and previous button because sometimes users want to use case: click, see picture, click, see picture, click see picture. if you are satisfied with readers spending the time they’ve planned for your site to be spent looking at numbers and counting slide rotations, then a traditional jquery slider should be just fine. If you want your readers looking at your content what you have is good. in your version the person viewing is absorbing and remembering in short term memory the headline for the new article instead of keeping their short term memory fixed on an arbitrary slide number 4 they need to click. when changing the slider from one feature to the next the eye moves along a shorter path than in most sliders where the eye must move outside the picture and down to a little number for the slide. The other big advantage comes from being more persuasive. You are right about this being better usability than most “mystery” sliders. You can view it on GitHub or use the links below to download and view a demo. I’m sure this has a few weaknesses (like accessibility the clickable news headlines are not using anchors - is that bad?), so I’m glad to look at suggestions for improvements. Those two options are very easy to change in the code by reading the code comments.Īlso, if you want different colors, the styles in the CSS file can be changed easily to accommodate any context. This is because, other than speed and auto-rotating, I couldn’t find many significant “options” to include. It’s not a jQuery plugin, it’s just a plug-and-play script with simple editable markup. In this way it’s a little more like a tab switcher, which has visible and clear options, rather than mystery items sliding in by surprise. That is, it’s not necessary to the readability and/or scannability of the module’s content, so I think it’s much more usable than other content sliders and switchers. The content that shows in the preview (the image and description) is really incidental. What I find is more practical about this one (compared to the usual carousels and whatnot) is the fact that there’s no mystery as to what’s coming next all the news items are clearly on display. This module, like the original in the magazine, is responsive and uses CSS3 for animation. I’ve been meaning to revisit, tweak, and release the code for that here and so I finally got around to it. I think the problems with these types of modules have been well documented.Ībout a year ago, however, I wrote a step-by-step tutorial for Issue #203 of Web Designer Mag that involved creating a “news content switcher”. The last thing developers need today is another jQuery and/or CSS3 based content slider or carousel.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |