Wednesday, 16 January 2013

Important Stacks Update - Google updated hosted version of the jQuery Javascript library

Stacks update 1/16/13?

Brian Corbett's Avatar

Brian Corbett

January 17, 2013 @ 05:12 AM
I just received an email via doobox regarding a stacks update today. Wondering where that is available and how I can obtain it. I am in the midst of preparing my site update for the first quarter and want to make sure I don't have any JQuery issues.
  1. 2 Posted by Areg Jera on January 17, 2013 @ 07:41 AM
    Areg Jera's Avatar
    Yes I have the same issue. Doobox had informed me that I need to download a stacks plugin update in order my my sites to function properly because of the change in Google's jQuery.
  2. Support Staff 3 Posted by Isaiah on January 17, 2013 @ 07:42 AM
    Isaiah's Avatar
    You will likely see the update the next time you start up RapidWeaver and open a Stacks page. If not you can always download it from our site: http://yourhead.com/stacks
  3. Isaiah closed this discussion on January 17, 2013 @ 07:42 AM.
Comments are currently closed for this discussion. You can start a new one.
------------------------------------------------------------------------------------------------

Important Stacks Update

As an owner of our Stack Products we want to inform you about an
important update of the Stacks Plugin.

Google updated their CDN hosted version of the jQuery Javascript library,
that is used by the Stacks Plugin and so by our Stack Products.

This new major version of jQuery might be causing some of our Stack Products
to show unexpected behavior when you are using the Stacks Plugin v2.1.

This affects the following Stack Products:
- Fancy Intro
- ImageMapper
- ShakeIt
- ScrollTo and Bounce


Yourhead Software released a new version of the Stacks Plugin v2.1.8,
that is using an older version of jQuery and so restores the behavior of the Stack Products.

We strongly recommend updating your version of the Stacks Plugin when you are
using one of the mentioned products.

You can update to this version using:
* The direct download link from the YourHead website
* Re-start RapidWeaver with your project file and select an Stacks Page for an automatic update.

After updating the Stacks Plugin it is time to republish your site(s).
We recommend using File -> Republish All Files to make sure that all required page assets are uploaded.


Our apologies for the inconvenience, we are working on updates to prevent this from happening.

In case an issue related to this jQuery update is not solved by the mentioned actions you can
of course contact us via support@tsooj.net


Kind regards,

Joost

©2013 Tsooj Media | Amersfoort | The Netherlands | www.tsooj.net

---------------------------------------
Begin forwarded message:

From: "Elixir Graphics"
Subject: Important update for the Bricks stack
Date: 17 January 2013 2:11:48 AM AEDT
To:
Reply-To: "no-reply@cartloom.com" <no-reply@cartloom.com>


Important Update!

Today Google made an update to their hosted version of jQuery, the javascript file the Stacks plugin uses. This javascript file is what powers much of what the Bricks stack does.

In it being updated this has caused a problem with another javascript library used within the Bricks stack, called Masonry.

I have just pushed out an update to the Bricks stack that will fix the problem for now until the Masonry library is updated, at which time we will likely send out a supplemental update.

Do note that this update to the jQuery library has broken a lot of stacks out there, not just the Bricks stack, so be patient with the Stacks developers as we all sort through these problems.


How to get the update:

The update has been pushed out to all Bricks users via Stacks built-in updater. To make sure you get this latest version and it is applied to your sites, please follow the instructions below:

- If you currently have RapidWeaver open, quit RapidWeaver. Once it has quit, relaunch it.

- Go to a page in your project file that is a Stacks page. This triggers Stacks to look for updates.

- Wait several minutes for Stacks to poll all of your stacks' plugins updates. This time varies depending on the number of stacks you have installed.

- Once it has finished you should see a red exclamation mark on the Bricks stack icon in the Stack Elements library drop down.

- To apply the update, highlight Bricks in the Stack Elements library by single-clicking on it.

- At the bottom of the Stack Elements drop down you will see a small gear, or cog, icon. Click this and choose 'Install Update.'

- Once it has finished, just to be sure all is well, quit and then restart Rapidweaver.

- From the File Menu in RapidWeaver choose the Mark All Pages as Changed. Then go back to the File Menu and choose Republish All Files.

We're terribly sorry for this inconvenience. It is a shame that an update to a javascript library that is remotely hosted, and automatically applied by Stacks, would cause such a hassle for all involved.

Sincerely,
Adam

Why to use Google hosted jQuery CDN | jQuery By Example

Why to use Google hosted jQuery CDN | jQuery By Example

Thursday, January 5, 2012


Why to use Google hosted jQuery CDN

Google is sea of free services. Do you know that Google is also hosting jQuery libraries on its CDN(Content delivery network) and allows any website to use it for free. But why to use Google hosted jQuery CDN?

Advantage:


  • Caching: The most important benefit is caching. If any previously visited site by user is using jQuery from Google CDN then the cached version will be used. It will not be downloaded again.
  • Reduce Load: It reduces the load on your web server as it downloads from Google server's.
  • Serves fast : You will be also benefitted from speed point of view. As Google has dozen's of different servers around the web and it will download the jQuery from whichever server is closer to the user. Google's CDN has a very low latency, it can serve a resource faster than your webserver can.
  • Parellel Downloading: As the js file is on a separate domain, modern browsers will download the script in parallel with scripts on your domain.

How to use it?


There are 2 ways to load from Google CDN.

Method 1:
1<script  type="text/javascript"
3</script>

Method 2
1<script src="http://www.google.com/jsapi" type="text/javascript"></script>
2<script type="text/javascript"><!--
3google.load("jquery", "1.7.1");
4google.setOnLoadCallback(function() {
5// Place init code here instead of $(document).ready()
6});
7// -->
8</script>

What if Google CDN is down?


It is a good idea to use CDN but what if the CDN is down (rare possibility though) but you never know in this world as anything can happen. So if you have loaded your jQuery from any CDN and it went down then your jQuery code will stop working and your client will start shouting.

Hang on, there is a solution for this as well. Below given jQuery code checks whether jQuery is loaded from Google CDN or not, if not then it references the jQuery.js file from your folder.
1<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js"></script>
2<script type="text/javascript">
3if (typeof jQuery == 'undefined')
4{
5  document.write(unescape("%3Cscript src='Scripts/jquery.1.7.1.min.js' type='text/javascript'%3E%3C/script%3E"));
6}
7</script>
It first loads the jQuery from Google CDN and then check the jQuery object. If jQuery is not loaded successfully then it will references the jQuery.js file from hard drive location. In this example, the jQuery.js is loaded from Scripts folder.

Few quick tips


If you want jQuery 1.7.1 you can use a url like this:
1http://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js
Suppose you want to use latest version of 1.7 release,
1http://ajax.googleapis.com/ajax/libs/jquery/1.7/jquery.min.js
If you always want to refer the latest version of jQuery,
1http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js

Feel free to contact me for any help related to jQuery, I will gladly help you.


Monday, 31 December 2012

The Top 5 Website UX Trends of 2012 | UX Magazine

The Top 5 Website UX Trends of 2012 | UX Magazine


User interface techniques continued to evolve in 2012, often blurring the lines between design, usability, and technology in positive ways to create an overall experience that has been both useful and pleasurable.

Infinite scrolling, for example, is a technological achievement that also helps the user by enabling a more seamless experience. Similarly, advances in Web typography have an aesthetic dimension but also represent a movement toward greater clarity of communication.

1. Single-Page Sites



Single-page websites are everywhere. Big background images, rich illustrations, and animation techniques are being used to tell stories, entertain, and get a message across loud and clear. Free of the limitations of traditional website architecture, creative and beautiful one-pagers are flourishing. Two of our favorite single-page sites are Jess and Russ and Ben the Bodyguard. (Several other nice examples can be found here.) As with any trend, people want to emulate it, even if it's not the appropriate solution. This can easily lead to homogenization of style and, in some cases, poor execution. When done correctly, however, the single page website works very well.

2. Infinite Scrolling



Infinite scrolling is familiar to everyone, even if they don't realize it. It works best for unstructured information; live feed style, sorted by time. Sites with lots of images—like Google images or Pinterest—make excellent use of this technique, but thoughtful implementation is important to prevent user frustration. Lookbook is another good example. By pairing infinite scroll with a floating right column and a "back to top" button, the site allows users to consume endlessly and still get to other parts of the site easily. Infinite scroll is not a "one size fits all" solution—there are plenty of complex factors to consider, and pagination may still be the best technique for search results, large lists, and e-commerce.

3. Persistent Top Navigation or “Sticky Nav”



Persistent menus are ideal for complex sites, long scrolling pages, or applications with toolbar functionality. Persistent menus can be distracting, so it's best to keep them slim and unobtrusive. A great example is New Zealand's tourism website, which features a navigation that collapses down to just the main sections, leaving plenty of real estate for the rest of the page. The Gmail Web interface also does it right by giving users a persistent toolbar with the most used actions.

4. The Death of Web 2.0 Aesthetics



We've noticed a return to basics in visual design trends. A flat, clean, minimalist aesthetic with a focus on typography and information hierarchy has replaced the big, bright, juicy days of Web 2.0. A lot of websites and apps are even ditching graphical background images for pure CSS styles in order ensure a compelling experience across devices and resolutions. Our favorite recent visual designs include Basecamp, Dropbox, and the Smashing Magazine redesign.

5. Typography Returns


Thanks to maturing font technologies and improved font rendering on most browsers and devices, designers have more typefaces to choose from and more control of their type. There is an increased awareness of the importance of content, and with it, using typography to effectively communicate a message. With mobile, responsive design, and more retina displays, typography will continue to be an important focus on the Web in the next few years. One of our favorite examples is The New Yorker, which uses a standard Web font (Times New Roman) for body copy, beautifully paired with display fonts for headings and navigation (Irvin, Neutra).
In 2013, we’ll be looking for more examples of sites that improve user experience by judiciously balancing beauty, utility, and technology.

Monday, 19 November 2012

Top Ten Internal Website Goofs

Top Ten Internal Website Goofs

by Frank Roche on September 6, 2006

Corporate internal websites can be useful, but are often headache inducing. Employees are required to use them, but are often unable to find what they need. It’s often the little things that break down. And we’ve seen them all. With that in mind, we assembed our list of the top ten internal website goofs:

10. Poorly scaled. Otherwise useful tools are not scaled up for use with thousands or tens of thousands of users. If the only way to find your meeting in your meeting organization software is to click ‘Next’ four or five times through the list of every meeting your company is having today, then the software simply isn’t scaled for the demand.
9. Inability to navigate without a mouse. Don’t get me wrong, computer mice are handy tools. But so is the keyboard. In fact, there are users who simply can’t or shouldn’t use the mouse (e.g., blind people and carpal tunnel sufferers, respectively). And, quite simply, there are employees who prefer to use their keyboard. Browser technology is sufficiently advanced that there’s no excuse for making a website unnavigable without a mouse.
8. Not cross-browser compliant. Internet Explorer may be your corporate standard, but that doesn’t mean there aren’t other browsers users might want to use. Some browsers have disability-friendly tools (e.g., Firefox and Opera) that make it possible for users with disabilities to get around the internet. Don’t make it harder for them by making your site unusable by their tools of choice. Cross-browser compatibility can be difficult to achieve, and you’re always going to have to make some choices about which browsers you support, but more is better.
7. Inconsistent look and feel. You click a link on your corporate site, and you’re suddenly transported…somewhere. The logo’s the same, but the menu’s changed. Or the page title says it’s an internal department, but there’s nothing remotely similar in the look of the site to make you think it’s related to your company at all, let alone a part of the company. Not good. Users need to feel like they know where they are. When the look and feel of the site changes unexpectedly, it confuses your users.
6. Multiple navigation schemes. You’re looking for a link to today’s cafeteria menu. But is it in one of the many dizzying menus? One of those tab thingies? The quicklinks? Those sidepanels with extra info? Who knows? The more ways there are to organize info, the less likely you’ll be able to guess where your particular info is hiding.
5. Too much information on the front page. Too much info. Too many links. Tiny fonts. Too, too…busy. Company portals need to be scannable. No one has the time to or interest in reading everything available. Everyone’s just looking for the first link that catches their eye that could possibly be the thing their looking for. Sure, there’s a lot to your company, lots of information, and a lot of people to please. But the point of a portal isn’t to provide everything you possibly can squeeze in there. The point is to make a clear, easy starting point where employees will be able to navigate themselves to everything.
4. Poor role awareness. You see a link. It looks vaguely like what you’re looking for. You click it. You go to a page that says: “I’m sorry. You don’t have access to this feature.” Or maybe you get a popup with an error message. This is just not ok. Do not waste your user’s time. The user should never have access to a link to something he or she is not allowed to use. If they don’t have access, don’t give them something to click.
3. Missing information. This is especially problematic when combined with #5. A user can spend over a half an hour trying to hunt down info that should be there, but just isn’t. If your company offers a shuttle service, employees should be able to find the schedule. If you have a cafeteria, the hours it’s open should be easily available. If you provide an emergency weather phone number, it should be on your site.
2. No clear way to tell where I am. A complex portal website must have a clear and easy way to identify the user’s location in the portal. The portal should have breadcrumbs at the top of the page. The company logo should always be in the upper left corner, and should be a link to the home page for the portal. Links in the menu should not use different labels than the title of the page it will take you to. Every time you confuse your user, you slow him down. You slow your user down, they have less time for actual business concerns.
1. No clear way to find what I want. The biggest culprit of all is lame, poorly implemented, useless search. Your users need to be able to search or browse for what they want quickly and easily. So, you’re not Google. Fine. Hire them. Or spend some serious effort on making clear, clean browsing trees for your users to poke around in. When you go to a mall, and you don’t know where a store is, you check the mall map. When you go to a portal, and don’t know where your info is, you need a similarly straightforward way to navigate to that info.
Fundamentally, a portal should speed your users up. It should move them quickly to the info they want. It should be friendly to people with disabilities. It should be flexible to the myriad ways people do things. It shouldn’t get in their way, slow them down, or confuse them. After a half hour of battling with an uncooperative portal, your user is going to be tired, cranky, and uninterested in whatever it was they were originally doing. And that’s not good for business.
Want to learn more about good design? Consider the following resources:

10 Harsh Truths About Corporate Websites | Smashing Magazine

10 Harsh Truths About Corporate Websites | Smashing Magazine


Advertisement
Create free stunning flash websites!
We all make mistakes running our websites. However, the nature of those mistakes varies depending on the size of your company. As your organization grows, the mistakes change. This post addresses common mistakes among large organizations.
Most of the clients I work with are large organizations: universities, large charities, public sector institutions and large companies. Over the last 7 years, I have noticed certain recurring misconceptions among these organizations. This post aims to dispel these illusions and encourage people to face the harsh reality.
The problem is that if you are reading this post, you are probably already aware of these things. But hopefully this article will be helpful to you as you convince others within your organization. In any case, here are our 10 harsh truths about websites of large organizations.
(Smashing's note: We're working on the brand new Smashing Mobile Book on best practices, techniques and design strategies for mobile. Interested? Pre-order now and save 20%!)

1. You Need A Separate Web Division

In many organizations, the website is managed by either the marketing or IT department. However, this inevitably leads to a turf war, with the website becoming the victim of internal politics.
In reality, pursuing a Web strategy is not particularly suited to either group. IT may be excellent at rolling out complex systems, but it is not suited to developing a friendly user experience or establishing an online brand.
Screenshot of Zeldman's website
Zeldman urges organisations to create a separate web division.
Marketing, on the other hand, is little better. As Jeffrey Zeldman puts it in his article Let there be Web divisions:
The Web is a conversation. Marketing, by contrast, is a monologue… And then there’s all that messy business with semantic markup, CSS, unobtrusive scripting, card-sorting exercises, HTML run-throughs, involving users in accessibility, and the rest of the skills and experience that don’t fall under Marketing’s purview.
Instead, the website should be managed by a single unified team. Again, Zeldman sums it up when he writes:
Put them in a division that recognizes that your website is not a bastard of your brochures, nor a natural outgrowth of your group calendar. Let there be Web divisions.

2. Managing Your Website Is A Full-Time Job

Not only is the website often split between marketing and IT, it is also usually under-resourced. Instead of there being a dedicated Web team, those responsible for the website are often expected to run it alongside their “day job.” When a Web team is in place, it is often over-stretched. The vast majority of its time is spent on day-to-day maintenance rather than longer-term strategic thinking.
This situation is further aggravated by the fact that the people hired to “maintain” the website are junior members of the staff. They do not have the experience or authority to push the website forward. It is time for organizations to seriously invest in their websites by hiring full-time senior Web managers to move their Web strategies forward.

3. Periodic Redesign Is Not Enough

Because corporate websites are under-resourced, they are often neglected for long periods of time. They slowly become out of date with their content, design and technology.
Eventually, the website becomes such an embarrassment that management steps in and demands that it be sorted. This inevitably leads to a complete redesign at considerable expense. As I point out in the Website Owners Manual, this a flawed approach. It is a waste of money because when the old website is replaced, the investment put into it is lost, too. It is also tough on finances, with a large expenditure having to be made every few years.
Screenshot of Cameron Molls Article
Cameron Moll encourages web designers to realign their website rather than redesign.
A better way is continual investment in your website, allowing it to evolve over time. Not only is this less wasteful, it is also better for users, as pointed out by Cameron Moll in his post Good Designers Redesign, Great Designers Realign.

4. Your Website Cannot Appeal To Everyone

One of the first questions I ask a client is, “Who is your target audience?” I am regularly shocked at the length of the reply. Too often, it includes a long and detailed list of diverse people. Inevitably, my next question is, “Which of those many demographic groups are most important?” Depressingly, the answer is usually that they are all equally important.
The harsh truth is that if you build a website for everyone, it will appeal to no one. It is important to be extremely focused about your audience and cater your design and content to it. Does this mean you should ignore your other users? Not at all. Your website should be accessible by all and not offend or exclude anybody. However, the website does need to be primarily aimed at a clearly defined audience.

5. You Are Wasting Money On Social Networking

I find it encouraging that website managers increasingly recognize that a Web strategy is more than running a website. They are beginning to use tools such as Twitter, Facebook and YouTube to increase their reach and engage with new audiences. However, although they are using these tools, too often they do so ineffectively. Tweeting on a corporate account or posting sales demonstrations on YouTube misses the essence of social networking.
Screenshot of Microsoft's Channel 9 website
Microsoft dramatically improved its image amoung the development community by allowing Microsoft staff to speak out via the Channel 9 website.
Social networking is about people engaging with people. Individuals do not want to build relationships with brands and corporations. They want to talk to other people. Too many organizations throw millions into Facebook apps and viral videos when they could spend that money on engaging with people in a transparent and open away.
Instead of creating a corporate Twitter account or indeed even a corporate blog, encourage your employees to start Tweeting and blogging themselves. Provide guidelines on acceptable behavior and what tools they need to start engaging directly with the community connected to your products and services. This demonstrates not only your commitment to the community but also the human side of your business.

6. Your Website Is Not All About You

Where some website managers want their website to appeal to everybody, others want it to appeal to themselves and their colleagues. A surprising number of organizations ignore their users entirely and base their websites entirely on an organizational perspective. This typically manifests itself in inappropriate design that caters to the managing director’s personal preferences and contains content full of jargon.
A website should not pander to the preferences of staff but should rather meet the needs of its users. Too many designs are rejected because the boss “doesn’t like green.” Likewise, too much website copy contains acronyms and terms used only within the organization.

7. You’re Not Getting Value From Your Web Team

Whether they have an in-house Web team or use an external agency, many organizations fail to get the most from their Web designers. Web designers are much more than pixel pushers. They have a wealth of knowledge about the Web and how users interact with it. They also understand design techniques, including grid systems, white space, color theory and much more.
Post from Twitter complaining about being a pixel pusher
Treating designers as pixel pushers wastes their design experience: post from Twitter complaining about being a pixel pusher
It is therefore wasteful to micro-manage by asking them to “make the logo bigger” or to “move that 3 pixels to the left.” By doing so, you are reducing their role to that of a software operator and wasting the wealth of experience they bring.
If you want to get the maximum return on your Web team, present it with problems, not solutions. For example, if you’re targeting your website at teenage girls, and the designer goes for corporate blue, suggest that your audience might not respond well to that color. Do not tell him or her to change it to pink. This way, the designer has the freedom to find a solution that may even be better than your choice. You allow your designer to solve the problem you have presented.

8. Design By Committee Brings Death

The ultimate symbol of a large organization’s approach to website management is the committee. A committee is often formed to tackle the website because internal politics demand that everybody has a say and all considerations be taken into account. To say that all committees are a bad idea is naive, and to suggest that a large corporate website could be developed without consultation is fanciful. However, when it comes to design, committees are often the kiss of death.
Illustration showing why design by committee fails
Design by committee leads to design on the fly.
Design is subjective. The way we respond to a design can be influenced by culture, gender, age, childhood experience and even physical conditions (such as color blindness). What one person considers great design could be hated by another. This is why it is so important that design decisions be informed by user testing rather than personal experience. Unfortunately, this approach is rarely taken when a committee is involved in design decisions.
Instead, designing by committee becomes about compromise. Because committee members have different opinions about the design, they look for ways to find common ground. One person hates the blue color scheme, while another loves it. This leads to designing on the fly, with the committee instructing the designer to “try a different blue” in the hopes of finding middle ground. Unfortunately, this leads only to bland design that neither appeals to nor excites anyone.

9. A CMS Is Not A Silver Bullet

Many of the clients I work with have amazingly unrealistic expectations of CMS (content management systems). Those without one think it will solve all of their content woes, while those who have one moan about it because it hasn’t!
It is certainly true that a CMS can bring a lot of benefits. These include:
  • reducing the technical barriers of adding content,
  • allowing more people to add and edit content,
  • facilitating faster updates,
  • and allowing greater control.
However, many CMS are less flexible than their owners would like. They fail to meet the changing demands of the websites they manage. Website managers also complain that their CMS is hard to use. However, in many cases, this is because those using it have not been adequately trained or are not using it regularly enough.
Finally, a CMS may allow content to be easily updated, but it does not ensure that content will be updated or even that the quality of content will be acceptable. Many CMS-based websites still have out-of-date content or poorly written copy. This is because internal processes have not been put in place to support the content contributors.
If you look to a CMS to solve your website maintenance issues, you will be disappointed.

10. You Have Too Much Content

Part of the problem with content maintenance on large corporate websites is that there is too much content in the first place. Most of these websites have “evolved” over years, with more and more content having been added. At no stage has anybody reviewed the content and asked what could be taken away.
Many website managers fill their website with copy that nobody will read. This happens because of:
  • A fear of missing something: by putting everything online, they believe users will be able to find whatever they want. Unfortunately, with so much information available, it is hard to find anything.
  • A fear users will not understand: whether from a lack of confidence in their website or in their audience, they feel the need to provide endless instruction to users. Unfortunately, users never read this copy.
  • A desperate desire to convince: they are desperate to sell their product or communicate their message, and so they bloat the text with sales copy that actually conveys little valuable information.
Steve Krug, in his book Don’t Make Me Think, encourages website managers to “Get rid of half the words on each page, then get rid of half of what’s left.” This will reduce the noise level on each page and make the useful content more prominent.

Conclusions

Large organizations do a lot right in running their websites. However, they also face some unique challenges that can lead to painful mistakes. Resolving these problems means accepting that mistakes have been made, overcoming internal politics and changing the way you control your brand. Doing so will give you a significant competitive advantage and allow your Web strategy to become more effective over the long term.
(al)

Saturday, 10 November 2012

blogger label categories (code for) ~ The Blog Doctor.

Everything About Labels in Blogger. ~ The Blog Doctor.

CLASSIFY LABELS


Perhaps you would like to group your labels? To do this login to Dashboard and click on layout. Then click on Add Page element link in sidebar and in popup window choose Html/Javascript option. Paste the following code in it :



CATEGORY A






  • LABEL 1





  • LABEL 2





  • LABEL 3





  • CATEGORY B






    • LABEL 4





    • LABEL 5





    • LABEL 6





    • CATEGORY C






      • LABEL 7





      • LABEL 8





      • LABEL 9





      • Replace 'CATEGORY A' etc. with relevant category of the labels grouped under it. Save Page Element