What kind of site do you need?

Tailored sites make the best impressions.

Here we will explain We try to break them down into their simplest forms to explain exactly what it is that makes them tick so that we are all on the same page when we talk about site progression and the limitations of the web.

First things first, let's divide sites on the web into two main categories:

1. Static: site content is hard coded into a file, usually in HTML format. Content manipulation typically requires strong grasp of html coding practices along with a helper program, and a file transfer client through which a FTP connection can be established.
2. Dynamic: site content is managed and stored by a web application, many times utilizing a database to keep track of data. Typically these programs, of which there are hundreds, are equipped with a user interface that makes the process of changing content within the site as easy as using your favorite word processor (Word, OpenOffice, iWork, etc...) These interfaces are usually accessible with any web browser and an internet connection. The way in which the data is stored and the way that the interface works is determined by the coder and the language that is used, click here to get a brief breakdown of what that means.

There are also a couple of things that these two site types have in common, some of which are obvious but overlooked many times.

1. Both types of site are just different ways of getting to the same end product. Internet browsers of all kinds (for the purposes of this discussion) can only understand one language, HTML. Versions non-withstanding, all the dynamic and static sites eventually end up as HTML, usually with "extras" attached. The "extras" are where we get into images, video, Javascript, Flash, Quicktime, Silverlight, etc...the list goes on, as does the complication.
2. Also we must remember when looking at sites of any kind is that because the end game is the same, they both have many of the same feature limitations. That is to say the same site can be visually achieved using either method, the cost and complication change dramatically based on the intended purpose, picking the right solution is crucial.

This, of course, leads us to the question, "Which type is right for me?" Well that's why we're here! It can be a fairly difficult call to make, what you need now may not be compatible with what you need in the near future, and you don't want to buy a complicated site that you don't need. There are however some general guide lines that we can give you to help hone you in:

1. Find the purpose of your site. Figuring out what you want the site to do for you in a tangible way is going to make your life a lot easier, all questions can be answered and focused, "Will _______ feature, help me get ________ accomplished better?"
2. Determine your skill level, people that understand (and dare we say enjoy...) code typically gravitate toward the simpler static solutions. On the other hand if you have no desire to work in the strangely punctuated world of code but want to be able to change your site around periodically then dynamic has your name all over it.
3. Establish a budget. This one is pretty hard for most people. It takes a fair amount of research to know what fair market prices are going to run you, just know that for big sites static solutions are more expensive and for small sites dynamic solutions are more expensive. Exactly what the difference will be is a personal experience.
4. Think about the future, if you have an idea of where you want to go it might make a big difference in cost if you can plan for it today.