|
|
{blogger_name}{blogger_profile} {blogger_facts} {blogger_sports} {blogger_movie} {blogger_tv} {blogger_website} {blogger_quote} |
All entries by {blogger_name}
APR12
A billion for Instagram should not surprise
Facebook bought Instagram for $1 billion this week! Surprised? I was not...
I reveal my reasons on my personal blog - click here to read.
I reveal my reasons on my personal blog - click here to read.
JAN10
Our New Year's resolution
The New Year period is always a time for reflection and planning. It is when everybody starts dieting. When smokers quit smoking. When people get organized.
It is no different for businesses, and it is definitely no different here at KAYWEB.
Our New Year's resolution is to take our much-lauded customer service to the highest level ever in 2012.
When I survey clients to find out what they like about KAYWEB, they always respond that our customer service is very good compared to other experiences they've had in the web industry. We've accepted these compliments for over seven years, recognizing that customer service is one of our key points of difference.
This year, we want to take this point of difference to another level ... because we feel you need us to.
When starting a business 10 years ago, giving your business a web presence was not even on the priority list. Five years ago, it probably arrived somewhere towards the bottom of the top 10 things your business needs to get started. Today, it is number one or number two on that same priority list.
Every business needs a website, and a well strategized web presence. We will look to work with our clients to ensure their web presence is updated and holistic, with search engine optimization and social media marketing options taken into consideration.
We also feel that a mobile presence is becoming as important as a web presence for businesses. With nearly half of the world's visits to websites being made with mobile phones, it is our responsibility to check that our clients' websites are optimized for mobile browsing.
Our Support team has been expanded over the last year and is better equipped than ever to continue handling all our clients' technical issues.
KAYWEB will take customer service to a new level in 2012. Unlike many diets that began on January 1, our New Year's resolution will deliver results.
It is no different for businesses, and it is definitely no different here at KAYWEB.
Our New Year's resolution is to take our much-lauded customer service to the highest level ever in 2012.
When I survey clients to find out what they like about KAYWEB, they always respond that our customer service is very good compared to other experiences they've had in the web industry. We've accepted these compliments for over seven years, recognizing that customer service is one of our key points of difference.
This year, we want to take this point of difference to another level ... because we feel you need us to.
When starting a business 10 years ago, giving your business a web presence was not even on the priority list. Five years ago, it probably arrived somewhere towards the bottom of the top 10 things your business needs to get started. Today, it is number one or number two on that same priority list.
Every business needs a website, and a well strategized web presence. We will look to work with our clients to ensure their web presence is updated and holistic, with search engine optimization and social media marketing options taken into consideration.
We also feel that a mobile presence is becoming as important as a web presence for businesses. With nearly half of the world's visits to websites being made with mobile phones, it is our responsibility to check that our clients' websites are optimized for mobile browsing.
Our Support team has been expanded over the last year and is better equipped than ever to continue handling all our clients' technical issues.
KAYWEB will take customer service to a new level in 2012. Unlike many diets that began on January 1, our New Year's resolution will deliver results.
DEC08
Is your website mobile friendly?
It is no longer a secret that mobile is starting to take over as the preferred method of internet browsing for most consumers.
As a result, we at KAYWEB are constantly trying to get clients to start thinking about a mobile-friendly version of their website.
Google has come up with a neat tool to check how your website looks on mobile devices - it is part of an initiative called GoMo. Check it out by clicking here.
If you want to go mobile with your web presence, contact our Business Development staff in Sydney on 1300-793-646 or email info@kayweb.com!
As a result, we at KAYWEB are constantly trying to get clients to start thinking about a mobile-friendly version of their website.
Google has come up with a neat tool to check how your website looks on mobile devices - it is part of an initiative called GoMo. Check it out by clicking here.
If you want to go mobile with your web presence, contact our Business Development staff in Sydney on 1300-793-646 or email info@kayweb.com!
DEC08
Hey, I registered kayweb.xxx
.xxx is a domain extension designed to house pornographic websites, which currently appear on the same domain extensions used by businesses and organizations (e.g. .com and .com.au).
Contrary to what some may have thought when reading this blog headline, I am not thinking of branching KAYWEB out into porn (I can feel the sighs).
All I am doing is protecting our brand 'KAYWEB'. Better I register it and do nothing with it, rather than someone else register it and do everything with it.
I encourage you to do the same.
KAYWEB does not currently sell .xxx domain names as our supplier has not yet made it available, but they are available at Go Daddy.
I just thought I'd let our readers know that I have registered the domain name, kayweb.xxx.
.xxx is a domain extension designed to house pornographic websites, which currently appear on the same domain extensions used by businesses and organizations (e.g. .com and .com.au).
Contrary to what some may have thought when reading this blog headline, I am not thinking of branching KAYWEB out into porn (I can feel the sighs).
All I am doing is protecting our brand 'KAYWEB'. Better I register it and do nothing with it, rather than someone else register it and do everything with it.
I encourage you to do the same.
KAYWEB does not currently sell .xxx domain names as our supplier has not yet made it available, but they are available at Go Daddy.
SEP26
Beautiful fonts for the web
All modern browsers now support web fonts, in some form. Microsoft Internet Explorer has supported @font-face since 1997 in version 4, Apple Safari implemented support in 2008 in version 3.1, Mozilla Firefox added support in 2009 in version 3.5, and Google Chrome added support in 2010 in version 6.
When using @font-face you need to be aware of supported font formats and browser specific syntax. There is currently no universally supported web font format. Failing to provide proper font formats and browser supported CSS will result in your page rendering inconsistently across browsers. If done incorrectly, visitors will see the browser’s default font instead of the specified font.
There are some great font services that take care of cross browser support by dynamically generating the appropriate CSS for each browser.
Typekit, Webtype, WebINK, and Fonts.com are some of the services available, and all of them generally take care of hosting and licensing. Using one of these services allows the quickest path to implementation without having to know too much about the underlying technology.
Typekit provides many fonts created by Adobe, and we are working together to offer more Adobe fonts in the future.
Then there's Google fonts. The fonts will be generated by Google by accessing their servers, it will just take a couple of niffy jiffy on the doctype to use it, and its all for free.
If you find yourself needing to roll your own web fonts, there are a few basics that are required to ensure your intended fonts show up on all browsers:
Know your font formats. There are a few different versions of web fonts in use today.
Embedded OpenType (.eot) – Supported by Internet Explorer only.TrueType/OpenType (.ttf/.otf) – Supported by the widest range of browsers, but, not supported in Internet Explorer. (this may change in IE9)Web Open Font Format (.woff) – Supported in recent versions of Chrome, Firefox and Internet Explorer, but not yet supported in Safari.In addition to needing to worry about licenses and multiple font formats, browsers interpret CSS code differently, so writing a rule to include your fonts is less than straightforward. “Bulletproof” syntax for @font-face has evolved over the years to work around browser inconsistencies. Much of the syntax seems repetitive and counter intuitive. For a good history of @font-face and a clear explanation of the CSS syntax read the ”The New Bulletproof @Font-Face Syntax” blog post at Fontspring. Learning how the syntax has evolved gives a clearer picture of how each browser handles @font-face.
FontSquirrel is a web service that will convert fonts for you and generate CSS code. After uploading your fonts, FontSquirrel will convert your fonts for cross browser usage and generate CSS for you. The CSS code generated by FontSquirrel also happens to work just about everywhere, including mobile devices. If you use FontSquirrel to generate web fonts, make sure you have the proper license to do so.
Now, websites will be magazine-likes, having the best and nicest fonts out there and having the liberty to use all existing fonts for the web is truly outstanding and great news for designers as well.
Before wide browser support for the CSS @font-face rule, web pages were limited to “browser safe fonts”. This meant the designer was constrained to using fonts that were available on every visitor’s machine. @font-face allows a web designer to make typeface decisions based on aesthetics rather than availability.
All modern browsers now support web fonts, in some form. Microsoft Internet Explorer has supported @font-face since 1997 in version 4, Apple Safari implemented support in 2008 in version 3.1, Mozilla Firefox added support in 2009 in version 3.5, and Google Chrome added support in 2010 in version 6.
When using @font-face you need to be aware of supported font formats and browser specific syntax. There is currently no universally supported web font format. Failing to provide proper font formats and browser supported CSS will result in your page rendering inconsistently across browsers. If done incorrectly, visitors will see the browser’s default font instead of the specified font.
There are some great font services that take care of cross browser support by dynamically generating the appropriate CSS for each browser.
Typekit, Webtype, WebINK, and Fonts.com are some of the services available, and all of them generally take care of hosting and licensing. Using one of these services allows the quickest path to implementation without having to know too much about the underlying technology.
Typekit provides many fonts created by Adobe, and we are working together to offer more Adobe fonts in the future.
Then there's Google fonts. The fonts will be generated by Google by accessing their servers, it will just take a couple of niffy jiffy on the doctype to use it, and its all for free.
If you find yourself needing to roll your own web fonts, there are a few basics that are required to ensure your intended fonts show up on all browsers:
Know your font formats. There are a few different versions of web fonts in use today.
Embedded OpenType (.eot) – Supported by Internet Explorer only.TrueType/OpenType (.ttf/.otf) – Supported by the widest range of browsers, but, not supported in Internet Explorer. (this may change in IE9)Web Open Font Format (.woff) – Supported in recent versions of Chrome, Firefox and Internet Explorer, but not yet supported in Safari.In addition to needing to worry about licenses and multiple font formats, browsers interpret CSS code differently, so writing a rule to include your fonts is less than straightforward. “Bulletproof” syntax for @font-face has evolved over the years to work around browser inconsistencies. Much of the syntax seems repetitive and counter intuitive. For a good history of @font-face and a clear explanation of the CSS syntax read the ”The New Bulletproof @Font-Face Syntax” blog post at Fontspring. Learning how the syntax has evolved gives a clearer picture of how each browser handles @font-face.
FontSquirrel is a web service that will convert fonts for you and generate CSS code. After uploading your fonts, FontSquirrel will convert your fonts for cross browser usage and generate CSS for you. The CSS code generated by FontSquirrel also happens to work just about everywhere, including mobile devices. If you use FontSquirrel to generate web fonts, make sure you have the proper license to do so.
Now, websites will be magazine-likes, having the best and nicest fonts out there and having the liberty to use all existing fonts for the web is truly outstanding and great news for designers as well.





