Hello

I am a person who decided 3 years ago that I wanted to create or build my own websites.

The company I use to assist me not only has ALL the tools and All the advice and ALL the assistance and can prove ALL that it says and is SO cheap to purchase, just today it surprised me AGAIN.

It appears that they had a little setback with one of the tools they provide. This tool is a major tool for all of us who are building websites.

Did they deny the problem? No.
Did they try to pass the blame onto someone else? No.
Did they try to hide from a lot of angry customers? Again, no.

Here is what they did.
They sent an email out to everyone, yes that's right everyone telling us that there was a problem AND APOLOGIZING PROFUSELY!

In addition they compensated us for the inconvenience by adding credits to the tool that was affected.

They kept in contact with us all through a forum which was very easy to locate and use.

They received many, many words of encouragement from a lot of website builders basically saying - thanks for the extra credits and no problem with the glitch.

Then the company advised after many testings that the problems were all fixed and we were good to go.

NOW IS THIS THE TYPE OF SERVICE YOUR COMPANY PROVIDES?

I'm reasonably confident that a lot of people are paying a lot of money for a product which does NOT do all that this particular company does. Question is why do so many people stay with that type of website building company?

Not long ago, a friend of mine sent me an email asking for my opinion on whether a site he was developing should be done using Wordpress, LAMP, or ASP.NET. I've used all of those, but have always been so focused on the details and learning them that I never really thought about the great question of "What technology should be used for a given site?". That is such a good question that I decided to put my thoughts on paper and help provide some education to others.

Some people don't have the skills and ability to actually be able to choose the most appropriate technology. They know one thing and that is going to have to be made to work in all cases. That's not necessarily bad, but it's nice to be able to switch between technologies based on the type of site. The important thing to realize in web site development is that one technology does not fit all.

Wordpress

I have several web sites currently running Wordpress. I originally thought of Wordpress as just a blogging platform. While that is certainly its main use and what it is optimized for, you can definitely use it to create a more "traditional" looking web site. It is very configurable and there are tons of custom plug-ins available that can allow you to add RSS feeds, SEO tags, voting, etc. Since Wordpress is developed using PHP and MySQL, it is also possible to create your own plugins and customize your site template. Oh, and that's the other incredibly awesome thing about Wordpress -- the templates! There are literally thousands of free Wordpress templates available for download. If you can't find one that fits the theme of your site than you aren't looking hard enough.

Another nice thing about Wordpress is that you can easily find web hosting providers that support Wordpress. In most cases, you can click an install link and have Wordpress properly installed on your site in a few seconds. Then you go to the Wordpress admin console and configure your site. It is all very easy. You can upload multiple templates and easily switch between them. It is also easy to make minor changes to the templates (like changing tag lines, colors, etc.).

The other benefit of Wordpress is that it is a blogging platform and the search engines love blogs. You can configure your Wordpress install to automatically ping one or more blogging services whenever you add a new post or page. That way they know your site has changed and they should come index your site again. If you want your site to be found then using Wordpress as the underlying engine is a good option.

LAMP

In case you don't know, LAMP stands for Linux-Apache-MySQL-PHP, which is a very common and powerful set of technology components used for building web sites (and did I mention completely Open Source and free!). If you want complete control over your web site, then LAMP is a good option. There are plenty of examples, free scripts, etc. available on the web site to help you get started. There are also plenty of free editors and tools to help you along. The downside of LAMP is that it is hard for you to create your own development "environment". Since most of us run some flavor of Windows as our desktop operating system, we would need to use something like VMWare or Virtual PC to create a virtual machine running Linux. The next challenge is getting all of the components properly installed. While the installers for the LAMP components have definitely improved, they still don't compare to the ease of installing a Windows-based application. The next challenge with LAMP is debugging. It would be nice if we all wrote perfect code, but the reality is you need the ability to debug. There are PHP debuggers available. A good one is going to cost you some money though.

One of the best things about LAMP is that there are TONS of web hosting providers out there for you to pick from. The reason is quite simple -- LAMP is completely open source, so it there is very little cost for the hosting company to bear. That means more margin for them!

ASP.NET

Microsoft's contribution to web site development is ASP.NET. You can use any .NET language (C#, VB.NET, Python.NET, etc.) to develop an ASP.NET based site. In my opinion, the best thing about ASP.NET is the fact you can use Microsoft Visual Studio for you development tool. Visual Studio is the best tool out there. Yes, it costs money, but you definitely get what you pay for. The other nice thing about ASP.NET is that you can easily develop on your Windows-based desktop or laptop.

It is harder to find a good ASP.NET hosting provider. Believe me, I've looked! And I've used several different ones. The ASP.NET providers lag behind the LAMP providers in terms of what they offer. You also need to be careful and really understand what the provider means by things like "host unlimited # of domains". In many cases they just mean you can have an unlimited # of domains point to your single web site. That probably isn't what you want.

I mentioned the use of Visual Studio before. That tool is awesome and makes development SOOOO much easier. I did quite a bit of development using LAMP and got some sites up and running. I used Eclipse with a PHP plug-in and it worked pretty good. I didn't have Apache running or Linux, so couldn't really debug but I still managed. When it came time to create a more advanced web site, however, I quickly decided to switch over to ASP.NET and use Visual Studio. Debugging was a snap and the coding was made much easier thanks to Intellisense and Visual Studio's ability to "import" web services and make them easier for me to call from my code.

Making the Right Choice

Each of the technology options has pros and cons. If you want to get a site up quickly and it will be displaying basic information (text, images, video) then Wordpress is a great option. If you want a more advanced web site but don't want to spend much money on development tools, then LAMP is the best choice. Finally, if you already have Visual Studio or know .NET programming, then ASP.NET is a good option. If you're really lucky and can know all three then you can use the right tool for the job no matter what.

Not every site needs a site map, they can certainly be a good idea. Site maps provide a dual purpose: They provide search engine spiders easy access to all of your site pages and they provide site visitors easy access to all of your site pages. The difference is that search engines and visitors access your site map differently and therefore there are different methods that need to be applied to creating site map(s) that are friendly for both engines and search spiders.

Small sites typically don't need a site map so long as all pages are linked in the main navigation. Once you get into main and sub-navigation menu's then site maps are helpful in allowing search engines and visitors to quickly find anything they are looking for within just a couple of clicks. A single site map can be used for both purposes or multiple site maps can be created. Here we'll address creating site maps for spiders and humans separately.

Site Map For Spiders

.xml file

An .xml document should be added to your site's root directory containing links to all site pages. This .xml file should then be referenced should be compiled and placed into a proper .xml document which should be uploaded into the root directory.

Robots.txt file

With your .xml site map file in place you must then make it accessible to search spiders. Reference the site map in your robots.txt file by adding a line for sitemap: URL (example: sitemap: http://www.polepositionmarketing.com/sitemap.xml)

Keep current

Be sure that your .xml file is updated and uploaded frequently, or at least as often as pages are added or removed from your site. Large sites should implement an automated site map update monthly or even weekly or daily.

Site Map For Visitors

Navigation links

A site map designed for human visitors is just like any other website page. Link to the site map page should be included in the primary navigation or the site's global footer. Visitors should be able to find this link without too much searching.

Additional page links

Site map should also be linked from various pages within the site such as Help pages and your custom 404-redirect page. This helps point visitors to the site map as a quick and easy means to find what they need.

Overview

It's helpful to provide a short overview paragraph at the top of your site map page. This can be a nice introduction should someone land on this page directly from a search engine or elsewhere.

Heading and layout

The layout of the site map should present a clear visual hierarchal structure or your website. Both headings and sub-headings should be used above properly grouped links.

Text links & descriptions

Site map should primarily use textual links and page should not be cluttered with images or other distractions. It is also a good idea to provide an additional short description (provided there is room) for each link that allows the visitor to better understand where each link will take them.

Keep current

Be sure that your site map is updated and uploaded frequently, or at least as often as pages are added or removed from your site.

As I said above, not every site needs a site map. But those that do should be sure that the site map(s) they create are actually benefiting them. And the best way to do that is to make sure your site maps provide maximum usability for visitors and search engine spiders.