<?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:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:georss="http://www.georss.org/georss" xmlns:gml="http://www.opengis.net/gml"
>

<channel>
	<title>Apex Logic &#187; Web</title>
	<atom:link href="http://www.apexalaska.com/category/blog/web/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.apexalaska.com</link>
	<description>Providing The Right Solution!</description>
	<lastBuildDate>Fri, 03 Sep 2010 15:24:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Consistent e-mail = consistent business!</title>
		<link>http://www.apexalaska.com/blog/web/consistent-e-mail-consistent-business/</link>
		<comments>http://www.apexalaska.com/blog/web/consistent-e-mail-consistent-business/#comments</comments>
		<pubDate>Mon, 07 Apr 2008 08:38:20 +0000</pubDate>
		<dc:creator>karl</dc:creator>
				<category><![CDATA[Trends]]></category>
		<category><![CDATA[Web]]></category>

		<guid isPermaLink="false">http://www.apexalaska.com/?p=116</guid>
		<description><![CDATA[I was talking to a very nice couple. They own their own business and even have a website for it. As they were presenting their business card they prefaced it with, &#8220;our e-mail will be changing soon to email@newispdomain.dom, so ignore the one on the card.&#8221; Has this happened to you?  A business card with an [...]]]></description>
			<content:encoded><![CDATA[<p>I was talking to a very nice couple. They own their own business and even have a website for it. As they were presenting their business card they prefaced it with, &#8220;our e-mail will be changing soon to <a href="mailto:email@newispdomain.dom">email@newispdomain.dom</a>, so ignore the one on the card.&#8221;</p>
<p>Has this happened to you?  A business card with an e-mail scratched out or a label stuck on it over the old e-mail/website?</p>
<p>As we tell our clients, your e-mail and domain shoud be as consistent as as your business.</p>
<p>As I was speaking to that nice couple I asked how much this was going to cost them. After they told me the price of new business cards I asked how much to change newspaper ads, yellow page ads as well as notify their existing customers &amp; vendors that send them e-mail as well. Their eyes grew big as it became obvious that they did not consider the cost of these factors in changing ISPs.</p>
<p>I also reminded them that the reason I was there was to do a presentation on SPAM prevention and one of my points in my presentation/handouts was if the e-mail was different from the promoted website to consider the sender a possible spammer.</p>
<p>So I ask the question&#8230;how many of you have a website and use a hotmail, gmail, AOL, or yahoo e-mail on our business card? If it&#8217;s a matter of not wanting to change mail service (and frankly, thanks to today&#8217;s technology you should not have to), then how about setting up a forwarding e-mail account from your web domain?</p>
<p>A forwarding account is very simple to setup and is not a real e-mail account that you need to manage/check. It would be a special e-mail address that simply forwards to another e-mail account.</p>
<p>This would create a consistent e-mail address (<a href="mailto:you@yourbusinesswebsite.dom">you@yourbusinesswebsite.dom</a>) that no matter what you change in regards to your services (mail, hosting, ISP, etc.) your customers/vendors could always gain access to you regardless of the change.</p>
<p>It would also save reprinting of business cards, updating your website, changing yellowpage (and other printed) ads, and validating online directories for inconsistent data.</p>
<p>Oh&#8230;did I mention that you&#8217;re probably going to be mislabeled on major search engines like Google, Yahoo!, and MSN for months afterward?</p>
<p>Lastly, why would you want a single &#8220;catchall&#8221; e-mail for personal and business mail? Do you have USPS mail from your business come to your home? Keeping track of what&#8217;s business vs. personal as well as managing spam would be a nightmare!</p>
<p>So here are some tips for e-mail consistency:</p>
<ol>
<li>If you can keep the old e-mail address forwarding for at least a year. It will take about a year for people to remove old phone books alone, not to mention outdate vendors or customes you have infrequent dealings with.</li>
<li>Keep your old domain(s). Even if you change businesses keep you old domains if you have not sold them as they can be good leads for further and future business. Have them forward to your current/new website.</li>
<li>Have a consitent prefix (the part before the @) for e-mails. If you maintain the same prefix (jobob@) for every domain you have, then no matter where you end up e-mail wise&#8230;people shold still be able to reach you.</li>
<li>Keep your business and personal e-mail seperate. Most mail clients allow you to have mail from different accounts delivered to different mail storage points keeping the business mail records seperate.</li>
</ol>
<p>A consitent e-mail address just makes sense. If you are moving across town you try to keep the same phone number so people can continue to reach you&#8230;why should e-mail be different?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.apexalaska.com/blog/web/consistent-e-mail-consistent-business/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Blogging&#8230;not just for geeks and college students!</title>
		<link>http://www.apexalaska.com/blog/web/design/bloggingnot-just-for-geeks-and-college-students/</link>
		<comments>http://www.apexalaska.com/blog/web/design/bloggingnot-just-for-geeks-and-college-students/#comments</comments>
		<pubDate>Fri, 19 Oct 2007 18:11:29 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Application]]></category>
		<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://www.apexalaska.com/blog/services/bloggingnot-just-for-geeks-and-college-students/</guid>
		<description><![CDATA[It&#8217;s the latest craze for business on the internet. Sharing your thoughts and wisdom on a particular subject or subjects. What is a blog and more importantly&#8230;what can it do for my business? First let&#8217;s define a blog. A blog is short for web log &#8211; a frequently updated journal or diary that is instantly [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s the latest craze for business on the internet. Sharing your thoughts and wisdom on a particular subject or subjects.</p>
<p><strong>What is a blog and more importantly&#8230;<em>what can it do for my business</em>?</strong></p>
<p>First let&#8217;s define a blog. A blog is short for <em>web log</em> &#8211; a frequently updated journal or diary that is instantly published on the internet. Lately blogs have come into mainstream fashion in the news and political arenas, but there are blogs for practically anything, so much so that even Google has now built a specialty blog site (<a href="http://blogsearch.google.com/">http://blogsearch.google.com/</a>).</p>
<p>Compared to a regular website, a blog has several advantages, most notably:</p>
<ul>
<li><em>Easy to maintain</em> &#8211; no special tools like Dreamweaver or FrontPage, nor do you need to FTP anything. All the necessary tools to publish content are built in.</li>
<li><em>Easy to create &amp; setup</em> &#8211; most blogging tolls are very easy to setup on your existing website and there are a wealth of free blogging services such as blogspot (<a href="https://www.blogger.com/start">https://www.blogger.com/start</a>).</li>
<li><em>SEARCH ENGINE FRIENDLY</em> &#8211; That&#8217;s correct&#8230;blogs have lots of SEO features built in (i.e. each post is typically it&#8217;s own URL, categories and/or tags, and updated content make them more likely to be indexed if the search engines find lots of fresh content each time).</li>
<li><em>Interactivity with customers</em> &#8211; It&#8217;s a great way to interact with your existing and potential customers. If you make widget cast molds and blog about the various methods of &#8220;care and cleaning of widget molds&#8221; then you have now added value for existing customers as well as a forum for feedback (via blog comments).</li>
</ul>
<p>Best of all, blogs aren&#8217;t tied to a location! If you&#8217;re at a conference, you can blog from your hotel about the great things you&#8217;ve learned that will enhance your product/service. If it&#8217;s a matter of typing, you can even blog by phone (<a href="http://www.phoneblogz.com/">http://www.phoneblogz.com/</a>)!!!</p>
<p>Blogging for business allows you to do more than just plug your product or service, it personalizes your business with the customer allowing you to share your points of view and create a lasting relationship&#8230;not just with the people who walk in your door (assuming you have a brick and mortar shop), but the customers a half a world away.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.apexalaska.com/blog/web/design/bloggingnot-just-for-geeks-and-college-students/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Perils and Plunders &#8211; Moving to WordPress 2.3</title>
		<link>http://www.apexalaska.com/blog/web/hosting/perils-and-plunders-moving-to-wordpress-23/</link>
		<comments>http://www.apexalaska.com/blog/web/hosting/perils-and-plunders-moving-to-wordpress-23/#comments</comments>
		<pubDate>Fri, 19 Oct 2007 00:37:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Application]]></category>
		<category><![CDATA[Design]]></category>
		<category><![CDATA[Hosting]]></category>

		<guid isPermaLink="false">http://www.apexalaska.com/blog/hosting/perils-and-plunders-moving-to-wordpress-23/</guid>
		<description><![CDATA[First things first…. Right now there is no real reason to upgrade.  There aren’t security fixes, or the like in 2.3.  The changes between 2.2 and 2.3 are the following: Canonical URLs.  Our number one reason for you to move to 2.3. If your WP is in a subdirectory (www.myawesomesite.com/wp) then you’re OK search engine wise…however if your [...]]]></description>
			<content:encoded><![CDATA[<p>First things first….</p>
<p>Right now there is no real reason to upgrade.  There aren’t security fixes, or the like in 2.3.  The changes between 2.2 and 2.3 are the following:</p>
<ul>
<li>Canonical URLs.  Our <strong>number one reason</strong> for you to move to 2.3. If your WP is in a subdirectory (www.myawesomesite.com/wp) then you’re OK search engine wise…however if your blog is the root (www.myawesomesite.com) or a subdomain (subdomain.myawesomesite.com), you will be penalized by search engines for having duplicate content!!!!  Basically…in earlier versions of wordpress, <strong>http://www</strong> and <strong>http://</strong> are not canonical so that in the eyes of the search engines, you have TWO websites with duplicate content which will have you removed (right now you need to load a plugin, or set your .htacces to correct it)!</li>
<li>Links and posts are finally separated (if you use the blogroll it was considered a post and searchable as such).</li>
<li>Pending review for content, allowing the site owner to have contributing authors but maintain editorial control.</li>
<li>Housekeeping was another big one. Code formatting and style were also cleaned up.</li>
<li>Several bundled libraries were updated to their latest versions at time of release (i.e. TinyMCE – the core visual input tool now has spell check).</li>
<li>Post and page management was also improved. Managing your draft and private posts and pages is now much easier.</li>
<li>Plugin maintenance. If the plugin is registered, the plugin admin screen will alert you to updates.</li>
<li>Native tagging support which has been significantly lacking and required one to three plugins to incorporate.</li>
</ul>
<p>In making some of these changes, the developers had to restructure the database and this is where the problems come in.  If your theme or plugin isn’t 2.3 compatible it could cause you MAJOR headaches.</p>
<p>Luckily WP is listing the compatible (and incompatible) plugins for 2.3: <a href="http://codex.wordpress.org/Plugins/Plugin_Compatibility/2.3">http://codex.wordpress.org/Plugins/Plugin_Compatibility/2.3</a>. For the most part, your theme should not cause problems, but here is a list of compatibles: <a href="http://codex.wordpress.org/Themes/Theme_Compatibility/2.3">http://codex.wordpress.org/Themes/Theme_Compatibility/2.3</a>, especially if you want to implement tags.</p>
<p>However the lists above are as people alert the codex, so to still be sure we recommend you load and run this amazing plugin: <a href="http://smithsrus.com/downloads/wordpress-upgrade-preflight-check/">http://smithsrus.com/downloads/wordpress-upgrade-preflight-check/</a>.  We can tell you, if we had found this first…it’d have saved us several hours of headaches.</p>
<p>So…here is what we recommend now after all our experiences with upgrading:</p>
<p>Backup your database (you <strong><em>are</em></strong> backing up your database regularly right?!?)!  If not or you can&#8217;t with your hosting service, there are two plugins that do this VERY well from within WP: <a href="http://www.ilfilosofo.com/blog/wp-db-backup/">http://www.ilfilosofo.com/blog/wp-db-backup/</a> and if you want more control (as well as some db maintenance abilities): <a href="http://lesterchan.net/portfolio/programming.php">http://lesterchan.net/portfolio/programming.php</a> (WP-DBmanager).</p>
<p>With a little preplanning the migration should be fairly smooth.  Just remember to have a good backup of your WP files and database in case you need to revert.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.apexalaska.com/blog/web/hosting/perils-and-plunders-moving-to-wordpress-23/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
