So I had to show a progress indicator for an online questionaire and I also wanted it to look really nice.
There is a downside of course and it is that the technique uses the CSS3 rotate transform which is only supported on newer browsers. So if you have to allow for those with old IE versions to use the site you should probably look elsewhere.
I have based the code on an older pie graph timer example which is in turn based on an even older pie graph tutorial. In my case I wanted the progress indicator to not be a pie but actually a ring and also I wanted that ring to have a background-color that I could set. Having the background-color settable was not part of the examples I found so I have modified it to allow for that. Also I have modified it to work nicely with Twitter Bootstrap 3 – there was some problems due to the border box box-sizing applied everywhere by default in Bootstrap 3. In the spirit of sharing I am providing the code for you to download and improve upon.
In case you are wondering what it looks like you can have a look at the Signs Of Dyslexia Test that originated this work (just start answering the questions to see the progress indicator in action) or here is a screenshot:
By default the twentythirteen theme that comes bundled with WordPress is a great looking theme. It uses modern fonts and large orange coloured graphical accents.
Another benefit of using this standard theme is that you can be sure that a lot of work has been put into it – the WordPress brand depends on it!
Still I believe it has a few drawbacks for most : the comments feed is broken and it does not honour the setting to show summaries of posts on the frontpage instead of full posts. In this article I will fix both, it is really quite easy.
First of all the comments feed will actually return xml but it will do so with a 404 not found http response code which will cause the Google crawler to report it as a broken link on each and every page. This is not good for SEO. Fixing it involves hooking the feed_link action and return false if it is the comments-link :
Are you running several name-based virtual hosts on the same Apache server? If so you need to be aware that it can cause problems if there is ever a DNS record pointing to the server that is not also configured as a virtual host.
The reason for this is that by default Apache will send unmatched requests to the first site found in the configuration. This sounds like a good fallback until you realize that in practice the first site in configuration files is a rather arbitrary choice and also that the result is duplicate content!
Duplicate content is bad for SEO so you should really try to avoid it. As an example if you have example1.com setup as a site in your Apache configuration and also example2.com is setup in the DNS records – Apache will serve the exact same content (from site example1.com) to both example1.com and example2.com visitors!
Not only that but at least in Google Analytics it can distort your statistics as when this happens it will sometimes show as if example2.com is a referrer for visitors to example1.com when in fact is was simply because Apache served example1.com content to example2.com visitors.
Fortunately it is really easy to avoid when you know to look for it. What you do is simply to add this code in your httpd.conf file :
Save time and money when you shop online with Honey, a free Google Chrome based extension. Honey automatically finds the best coupon codes while browsing the vendor’s website. All you have to do is to click the find a coupon button which is automatically inserted in the page’s source code.
Currently supported websites/stores (more added daily):
Here are a few key updates:
Nothing has changed about your photos’ ownership or who can see them.
The updated terms of service help protect you, and prevent spam and abuse as Instagram grows.
And remember, these updates don’t change the fact that you own your photos that you post on Instagram, and the privacy controls work just as they did before.