<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rssdatehelper="urn:rssdatehelper"><channel><title>webhdt business blog</title><link>http://www.webhdt.ca</link><pubDate>2013-03-27T14:28:07</pubDate><generator>umbraco</generator><description>A repository of awareness and knowledge for SMB's on how they could more effectively create and implement their web strategies, webhdt inc. is proud to share its many years of knowledge and experience in our company business blog.</description><language>en</language><item><title>Mistakes when selecting a CMS</title><link>http://www.webhdt.ca/blog/2013/3/26/mistakes-when-selecting-a-cms/</link><pubDate>Tue, 26 Mar 2013 00:00:00 GMT</pubDate><guid>http://www.webhdt.ca/blog/2013/3/26/mistakes-when-selecting-a-cms/</guid><description><![CDATA[ <h2>Introduction</h2>
<p>Businesses often overlook the importance of choosing the right CMS for their website project. This can impact not just the process of selecting the right CMS but the whole website project. Having worked on many different types of CMS projects over many years, the same issues appear over and over again. And most often these issues arise because of how the requirements are documented, or lack of documentation, or lack of project scope, or from limited understanding of content management systems issues. Below is a list of commonly seen mistakes when selecting a CMS, to help you make a better decision for your next website development project. Most of these mistakes are simple to resolve by taking a common-sense approach in the selection process to the final deployment of the CMS that works for everyone; authors, translators, administrators and IT.</p>
<div class="box alert-box">
<h4>Mistakes to avoid</h4>
<ul class="short arrow">
<li><a href="/blog/2013/3/26/not-understanding-what-problems-your-website-needs/" target="_blank" title="Not understanding what problems your website needs" class="button">Not understanding what problems your website needs to solve</a></li>
<li><a href="/blog/2013/3/26/not-knowing-content-management-issues/" target="_blank" title="Not knowing content management issues" class="button">Not knowing Content management issues</a></li>
<li><a href="/blog/2013/3/26/assuming-you-do-not-have-much-options/" target="_blank" title="Assuming you do not have much options" class="button">Assuming you do not have much options</a></li>
<li><a href="/blog/2013/3/26/not-keeping-it-simple/" target="_blank" title="Not Keeping it simple" class="button">Not Keeping it Simple</a></li>
<li><a href="/blog/2013/3/26/not-setting-clear-requirements/" target="_blank" title="Not setting clear requirements" class="button">Not setting clear requirements</a></li>
<li><a href="/blog/2013/3/26/concentrating-on-the-what-instead-of-the-how/" target="_blank" title="Concentrating on the 'What,' instead of the 'How'" class="button">Concentrating on the 'What,' instead of the 'How'</a></li>
<li><a href="/blog/2013/3/26/assuming-anyone-can-deliver-both/" title="Assuming Anyone Can Deliver Both" class="button">Assuming anyone can deliver both new design and a new CMS </a></li>
</ul>
</div>
<h3>Summary</h3>
<p>Most of these mistakes are overcome by taking a common-sense approach in the selection process to the final deployment of the CMS that works for everyone; authors, translators, administrators and IT. Start by understanding the content management issues, weigh your options and most of all set clear business goals as soon as you can. These will help you identify the requirements for your CMS solution. Success depends on those who will use the software on a daily basis, be realistic with your organizations capacity. And, however you organize to make the selection process for your business the following tips will help you.</p>
<ul class="short check">
<li>Do not skip the content strategy: Once you know what your business goals are and how you will achieve them with your website content, you will have a much better task of choosing the right CMS. But never choose your CMS without knowing what and how you need to accomplish.</li>
<li>Focus on business goals and desired outcomes over processes: Unless if the CMS offers a better process, focus on what you want to accomplish instead of trying to adjust your current working methods to fit the CMS system.</li>
<li>Test, test, test: Plan and create a testing environment right from the start to test future development works or upgrades. Do not take any major changes to your live version of the CMS unless you have tested it on your testing environment.</li>
</ul>
<p><a href="/blog/2013/3/26/not-understanding-what-problems-your-website-needs/" title="Not understanding what problems your website needs" class="green button"> Go to First Mistake</a></p>]]></description></item><item><title>Not understanding what problems your website needs</title><link>http://www.webhdt.ca/blog/2013/3/26/not-understanding-what-problems-your-website-needs/</link><pubDate>Tue, 26 Mar 2013 00:00:00 GMT</pubDate><guid>http://www.webhdt.ca/blog/2013/3/26/not-understanding-what-problems-your-website-needs/</guid><description><![CDATA[ <p>There is no basis with which to select a CMS if you have not yet identified or understood what your website will need to do. When businesses usually rush in choosing a CMS it is mainly due to a piece of technology that sounds it will solve the problem. Instead, you should think of analyzing the needs and focus on the business problems the website will need to solve. Therefore you should start by understanding your website needs before understanding the CMS requirements. The major mistake businesses make is choosing the CMS even before:</p>
<ul class="short check">
<li>Establishing the business needs and goals</li>
<li>Identifying the website design or management requirements</li>
<li>Creating an overall web strategy</li>
<li>Identifying the website functionality</li>
</ul>
<p><a href="/blog/2013/3/26/not-knowing-content-management-issues/" title="Not knowing content management issues" class=" green button"> Go to Next Mistake</a></p>]]></description></item><item><title>Not knowing content management issues</title><link>http://www.webhdt.ca/blog/2013/3/26/not-knowing-content-management-issues/</link><pubDate>Tue, 26 Mar 2013 00:00:00 GMT</pubDate><guid>http://www.webhdt.ca/blog/2013/3/26/not-knowing-content-management-issues/</guid><description><![CDATA[ <p>For those businesses who have never had prior experience using a CMS knowing all the content management issues will be hard. Even those who have worked with only one application and considering changing their content management systems might not have necessarily experienced all. The biggest challenge is actually identifying what will be required from the CMS system. The responsibility of choosing the right solution lies with the organization purchasing the system, after all they will be the one using it day in day out. For an informed decision you would need to be able to answer the following questions for each CMS you intent on selecting in your short list:</p>
<ul class="short check">
<li>What will be the important challenges that the implementation project will face?</li>
<li>What are the main features that differentiate from others?</li>
<li>What are the main design issues which might cause problems in the near future?</li>
<li>What was the developer's main intent originally?</li>
<li>What are the proposed "Best Practice" approaches to content management?</li>
<li>What kind of problems does the CMS solve the best?</li>
</ul>
<div class="box notice-box">
<p>The earlier you know the answers to these questions the better you will understand the issues pertaining to content management systems which will help you make an informed decision at the end. You should give time to build a certain knowledge before choosing your CMS and usually this will involve reading and researching existing material, or the quicker approach is to discuss it with other organizations who have already implemented a CMS similar to the one you would need.</p>
</div>
<p><a href="/blog/2013/3/26/assuming-you-do-not-have-much-options/" title="Assuming you do not have much options" class="green button">Go to Next Mistake</a></p>]]></description></item><item><title>Assuming you do not have much options</title><link>http://www.webhdt.ca/blog/2013/3/26/assuming-you-do-not-have-much-options/</link><pubDate>Tue, 26 Mar 2013 00:00:00 GMT</pubDate><guid>http://www.webhdt.ca/blog/2013/3/26/assuming-you-do-not-have-much-options/</guid><description><![CDATA[ <p>There exists thousands of Content management systems World-wide, from the free open source to the licensed enterprise versions. The challenge is to find the right one which will satisfy your business needs without taking you to the bank. Most often businesses, who do not take the time to research, have a partial perception of what is a CMS. Thus allowing for the opportunity to miss the appropriate CMS.</p>
<p>At first most CMSs will look similar with their functionalities but further investigation will reveal their differences and how they are hugely different from the other.</p>
<p><a href="/blog/2013/3/26/not-keeping-it-simple/" title="Not Keeping it simple" class="green button">Go to Next Mistake</a></p>]]></description></item><item><title>Not Keeping it simple</title><link>http://www.webhdt.ca/blog/2013/3/26/not-keeping-it-simple/</link><pubDate>Tue, 26 Mar 2013 00:00:00 GMT</pubDate><guid>http://www.webhdt.ca/blog/2013/3/26/not-keeping-it-simple/</guid><description><![CDATA[ <ul class="short star">
<li>Is a <span class="highlight">bigger</span> content management system <span class="highlight"> better</span>?</li>
<li class="highlight">Is there a <span class="highlight">correlation</span> between <span class="highlight">cost</span> and <span class="highlight">performance</span> of a CMS?</li>
<li class="highlight">Is <span class="highlight">open source</span> CMS <span class="highlight">cheaper</span> than the <span class="highlight">licensed</span> ones?</li>
</ul>
<p>These are questions that arise in almost every selection process and most often bigger is not better. Paying more for a CMS does not automatically make your choice a better one for you.</p>
<p>It is also a major mistake to associate the number of features, plug-ins or add-ons a CMS has with the never-ending possibilities it can offer to you. I have yet to work on a serious CMS project that did not require modifications to plugins or add-ons anyway. Nevertheless, the idea is to keep the CMS simple and small enough to accomplish your business goals.</p>
<p><a href="/blog/2013/3/26/not-setting-clear-requirements/" title="Not setting clear requirements" class=" green button">Go to Next Mistake</a></p>]]></description></item><item><title>Not setting clear requirements</title><link>http://www.webhdt.ca/blog/2013/3/26/not-setting-clear-requirements/</link><pubDate>Tue, 26 Mar 2013 00:00:00 GMT</pubDate><guid>http://www.webhdt.ca/blog/2013/3/26/not-setting-clear-requirements/</guid><description><![CDATA[ <p>A requirement is that need that the CMS must be able to perform for you to accomplish your goals. Defining requirements will help you eliminate those CMS solutions which are not a good fit for you thus setting your needs clearly from the start will allow you to make that best choice.</p>
<p>Some businesses end up by identifying some requirements which are available in all of the CMS solutions. For example, requesting for a WYSIWYG editor with CMS is an ineffective requirement since all of them already offer it.</p>
<p>Other examples of unclear requirements would be not to provide enough detail or context which will make it hard to evaluate during the evaluation process. For example, requesting that the CMS integrate with social media is an ineffective requirements since it is very hard to evaluate if the level of integration will accomplish the business goals.</p>
<p>Having too many requirements is also ineffective. If for some reason you notice that the number of requirements is growing than it would be best to categorize them as "must-have" or "nice-to-haves". These categorization of requirements will help you when it comes to evaluate the CMS solutions.</p>
<p><a href="/blog/2013/3/26/concentrating-on-the-what-instead-of-the-how/" title="Concentrating on the 'What,' instead of the 'How'" class="green button">Go to Next Mistake</a></p>]]></description></item><item><title>Concentrating on the 'What' instead of the 'How'</title><link>http://www.webhdt.ca/blog/2013/3/26/concentrating-on-the-what-instead-of-the-how/</link><pubDate>Tue, 26 Mar 2013 00:00:00 GMT</pubDate><guid>http://www.webhdt.ca/blog/2013/3/26/concentrating-on-the-what-instead-of-the-how/</guid><description><![CDATA[ <p>The success of any CMS project depends on the day to day usage of its users and how the CMS actually works, in detail. For example, one of your requirements would be to have flexible workflow capabilities, a very advantageous feature. But how does this flexible workflow feature actually work? In reality, there are many different implementations, starting from a single drop down status changes all the way to developing workflow foundation frameworks. At the end the answers are in the details. Asking "how" questions with the aim of building the CMS strengths and weaknesses will help you make the best choice.</p>
<p>One approach would be to ask about how each CMS can meet your "must-have" requirements or needs. And evaluating your choices based on "how" the CMS meets your need.</p>
<p><a href="/blog/2013/3/26/assuming-anyone-can-deliver-both/" title="Assuming Anyone Can Deliver Both" class="green button">Go to Next Mistake</a></p>]]></description></item><item><title>Assuming Anyone Can Deliver Both</title><link>http://www.webhdt.ca/blog/2013/3/26/assuming-anyone-can-deliver-both/</link><pubDate>Tue, 26 Mar 2013 00:00:00 GMT</pubDate><guid>http://www.webhdt.ca/blog/2013/3/26/assuming-anyone-can-deliver-both/</guid><description><![CDATA[ <p>Most often, if a business is in the process of selecting a CMS it is mainly due to the current site not meeting the business goals anymore. For whatever reason that may be generally a new CMS comes with redesign of the site and in most cases companies tend to think that any web designer can also help them in making their CMS choice. This is a very dangerous assumption that is driven by convenience instead of strategy.</p>
<p>It is better to separate the task of designing from developing the CMS. Otherwise, your new design will be guided by the developer's functionality limitations instead of the designer's usability guidelines.</p>
<p><a href="/blog/2013/3/26/mistakes-when-selecting-a-cms/" title="Mistakes when selecting a CMS" class="green button">Go to Introduction</a></p>]]></description></item><item><title>Developing effective content for your website project</title><link>http://www.webhdt.ca/blog/2013/1/14/developing-effective-content-for-your-website-project/</link><pubDate>Mon, 14 Jan 2013 00:00:00 GMT</pubDate><guid>http://www.webhdt.ca/blog/2013/1/14/developing-effective-content-for-your-website-project/</guid><description><![CDATA[ <p> </p>
<p>In a previous blog <a href="/blog/2011/11/14/creating-a-website-alone-will-not-get-you-the-results-you-want!/" title="Creating a website alone will not get you the results you want!">Creating a website alone will not get you the results you want</a> we stress the importance that having an effective website will drive you traffic, leads and sales. <strong>Content is king! </strong></p>
<p>And for content to be king, you need to go through a certain process and develop a content plan for your website. 10 questions to ask yourself which will get you started developing your website content.</p>
<h2>10 questions for developing effective content for your website</h2>
<ol style="margin-left: 30px; font-size: 1.25em;">
<li>What are the popular services or products your clients/prospects most want and need?</li>
<li>What are your organization strengths and weaknesses?</li>
<li>What are the customer needs that your products or services satisfy?</li>
<li>Describe your typical customer (needs, desires, preferences, fears, pain, etc.). What can you say about your best customers?</li>
<li>Who is your competition?  (list them)</li>
<li>What makes your organization different than your competitors? Why should someone choose you over the other?</li>
<li>Do you have an existing tagline, slogan or brand statement?</li>
<li>How do you attract new customers now?</li>
<li>What are the keywords that new customers might use to find you online?</li>
<li>What is your target geographical location (international/national/regional/state/local)?</li>
</ol>
<p> </p>
<p>You might not have all the answers to these questions at first but with time and an effort it will be clear to you and your organization.</p>
<p>The answers to these question will then help you in writing the website copy page per page.</p>
<h2>How to plan writing content for each page?</h2>
<p>For each page in your proposed website architecture, the objective should be to keep it simple and stupid for your customers. After the page title (main header) of the page the second most important content will be the first paragraph. This paragraph should summarize the page and link to the main call-to-action. The ideal would be to have this paragraph so convincing to the user that they will follow through your call-to-action. For those who are not convinced at first, you can develop further each argument you made in the original paragraph and back them up with supportive points. Do this until you have completely developed your main arguments and provided supportive follow up points. At the end of the page, make sure you provide a clear direction to the user as to where they should go next.</p>
<p>While writing your copy for each web page you must consider that you are writing for your reader (the human behind the screen), it is important to focus on what the page is all about. Here are some questions that will help you stay focused.</p>
<ul>
<li>What is the desired outcome of this page?</li>
<li>Who is the target of this page?</li>
<li>What are the 3 primary benefits you want to communicate?</li>
<li>What keywords should you include for SEO?</li>
</ul>
<h2>Website content writing review questions</h2>
<p>Once you have written your copy for your primary reader (the human), review your content to make sure you stayed focus and that the content will help you drive traffic from search engines (SEO) as well. Preparing a review checklist is a good practice, the following are some important questions to consider for your review questions:</p>
<ul>
<li>Is the page content greater than 300 words?</li>
<li>Is the main page title clear and catchy?</li>
<li>Is your content relevant to the targeted audience? Does the content incite the reader to take an action (desired outcome)?</li>
<li>Is your first paragraph summarizing benefits and provoking a call-to-action?</li>
<li>Is your content divided in sub-headers and paragraphs?</li>
<li>Are you addressing the reader?</li>
<li>Is there no spelling or grammatical errors?</li>
<li>After reading the page will the reader know what to do next?</li>
</ul>]]></description></item><item><title>Why Responsive Web Design</title><link>http://www.webhdt.ca/blog/2012/12/10/why-responsive-web-design/</link><pubDate>Mon, 10 Dec 2012 00:00:00 GMT</pubDate><guid>http://www.webhdt.ca/blog/2012/12/10/why-responsive-web-design/</guid><description><![CDATA[ <p><img src="/media/17504/responsive-web-design-webhdt_500x245.jpg"  width="500"  height="245" alt="Responsive Web Design - access" src="/media/17504/responsive-web-design-webhdt.jpg"/></p>
<p>2012 was the year of the mobile smartphones &amp; some predict 2013 will be the year for tablets.</p>
<p>To anyone who manages a website, it is apparent that mobile &amp; tablet use is increasing and for most it is becoming the device choice to browse or shop on the internet.</p>
<p>This change causes a major challenge to a web designer. Not only does a website designer need to accommodate the different browsers and their versions they must absolutely tailor to the different devices and their size.</p>
<p>Traditionally, web designers would create web pages for the latest browsers that would also work on older versions of browsers. The traditional web design strategy was then replaced with the principle of creating a simple document with the lowest common denominator compatible for all browsers and by adding extra behavior or functionality using cascading style sheet or javascript.</p>
<p>The increase in popularity of the mobile &amp; tablet made this latest strategy hard or expensive to manage for those business websites who had to cater to their mobile users. Some implemented multiple versions of the website using server side device detection techniques to accommodate the different browsers, devices, and screens.</p>
<p>Responsive web design addresses this ever changing landscape of devices, browsers, screen sizes and orientation. This strategy basically is to create fluid layouts and adapt the website content to almost any viewer.</p>
<h2>What does responsive web design mean for business websites?</h2>
<p>If implemented properly, responsive websites:</p>
<p>1)      Reduces the need to manage multiple website content: Develop content once and have the CMS adapt to the viewing screen.</p>
<p>2)      Allows the possibility to offer a better user experience by catering to the most desired functionality by user type.</p>
<p>3)      Can increase website stickiness and return visits because your website is user friendly on multiple devices now.</p>
<p>The responsive web design strategy is still in its early stages but evolving rapidly. It definitely looks like it is here to stay.</p>
<h2>Is it worth to redesign your website?</h2>
<p>Switching over to a responsive web design will be a challenge for your content, design &amp; development teams, but with the way the industry is moving, it’ll prepare you for the future, and put you a step ahead of your competitors.</p>]]></description></item></channel></rss>
