Showing posts with label HTML. Show all posts
Showing posts with label HTML. Show all posts

Monday, March 26, 2012

RADIO BUTTON - HTML Forms

Radio buttons are used when you want to let the visitor select one - and just one - option from a set of alternatives. If more options are to be allowed at the same time you should use
check boxes instead.





SETTINGS:

Below is a listing of valid settings for radio buttons:


HTMLEXPLANATIONEXAMPLE
radio
  name=
  value=
  align=
  tabindex=
checked

Choose one - and only one - option
Name of the group.
Value that is submitted if checked.
Alignment of the field.
Tab order of the field.
Default check this field.




The name setting tells which group of radio buttons the field belongs to. When you select one button, all other buttons in the same group are unselected.
If you couldn't define which group the current button belongs to, you could only have one group of radio buttons on each page.

The value setting defines what will be submitted if checked.

The align setting defines how the field is aligned.
Valid entries are: TOP, MIDDLE, BOTTOM, RIGHT, LEFT, TEXTTOP, BASELINE, ABSMIDDLE, ABSBOTTOM.
The alignments are explained in the image section. You can learn about the different alignments here.

The tabindex setting defines in which order the different fields should be activated when the visitor clicks the tab key.




AN EXAMPLE:

Look at this HTML example:
<html>
<head>
<title>My Page</title>
</head>
<body>
<form name="myform" action="http://www.mydomain.com/myformhandler.cgi" method="POST">
<div align="center"><br>
<input type="radio" name="group1" value="Milk"> Milk<br>
<input type="radio" name="group1" value="Butter" checked> Butter<br>
<input type="radio" name="group1" value="Cheese"> Cheese
<hr>
<input type="radio" name="group2" value="Water"> Water<br>
<input type="radio" name="group2" value="Beer"> Beer<br>
<input type="radio" name="group2" value="Wine" checked> Wine
<br>
</div>
</form>
</body>
</html>


And the resulting output:


Milk
Butter
Cheese
Water
Beer
Wine

Custom error pages - beating 404 errors and keeping visitors

Create custom error pages, help keep your visitors and increase your sales!
HTTP 404 - File not found is a browser error message that we've all grown to know and hate after clicking on a link.

On reviewing my server logs many moons ago, I  noticed around 1% of all requests from my site will return this HTTP error code. One of the reasons for it was a stupid mistake. I wasn't happy with the naming of a couple of my files, so I renamed them without considering the consequences:

- The files had been on my site for short time

- During that time a couple of search engine spiders had crawled through the pages. A search engine spider  is a software program that scours web sites for content and returns the results to a search engine database. The search engine interface feeds off this to return listings to searchers when they have entered their search criteria.
Need to learn about  search engine ranking and optimization strategies or want to monitor the SEO health of your web sites (and those of your competitors)? One of the most comprehensive set of online search engine optimization tools around -  SEOMOZ.
- Since I changed the names of the files after the spider went through and had not used a 301 redirect, the pages in their original state no longer "existed".

- The search engine query results reflect the database entries, pointing to the wrong filename, visitor clicks on the result - 404.... aaaaaaaaargh!
404 errors may also be caused through a malformed browser request (user error - wrong URL typed into address bar)

You can help prevent 404 errors scaring visitors away quite easily - dependent upon your hosting service set up. Instead of a visitor being directed to those rather horrible "file not found" pages, you can create custom error pages. Here is an example:

http://www.tamingthebeast.net/aaaargh
The above link is incomplete which triggers a 404 response on my server.

By implementing custom error pages, you have a good chance of retaining the visitor, especially if you include the standard navigation buttons. It also acts as a means of apologizing to the visitor for the inconvenience. More retained visitors can equal more sales.
It isn't just 404 error messages that you can apply this to. There are a number of error code returns that you could customize, all with the goal of alleviating visitor stress and encouraging them to further explore your site. View a listing of http error codes.

Creating custom error pages:

You may want to check with your hosting service first before creating custom error pages as certain hosting configurations may not allow you to create custom error pages. For this exercise, your host needs to support .htaccess files.

1. Create your custom error page

First design and publish the error pages to your server.  You'll only really need to design a couple for the more common errors, for file not found (404) or unauthorized/forbidden (403, 401). Your custom error pages should have a brief summary of what went wrong and an encouragement for the visitor to try again or explore a different area of the site. The best custom error pages are those that match the site's other pages in navigation and layout.
Note: I also suggest adding the following line between the <head> and </head> tags:
<META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW">
You don't want search engines spidering the page - it has been known to cause problems.

2. Open/create your .htaccess file

After publishing the pages, you'll need to edit the .htaccess file in the root directory of your server based web. Use the Edit utility (set to ASCII transfer mode) in your FTP program  to view the file or a text editor such as Notepad.
The .htaccess file contains a number of settings to control who can access the contents of a specific directory and how much access they have.  It can also be used to create a "URL Redirect".
If you have a FrontPage based web, be especially careful, as the .htaccess file contains other settings as well.
If you don't find a .htaccess file, you can create your own, but once again, check with your hosting service first for guidelines. Be sure to use a plain text editor and name the file ".htaccess" (notice the "." preceding the file name).

3. Edit your .htaccess file

Add the following lines to the end of the file (examples provided as a guideline - alter path and file names to point towards your error pages)
ErrorDocument 404 http://site.com/folder/404.htm
ErrorDocument 403 http://site.com/folder/403.htm
ErrorDocument 401 http://site.com/folder/401.htm 
Upload the .htacess file back to the root of your web in ASCII mode and you should be good to go. Try it out by typing in a non existent URL on your site.
Custom error pages are simple to create, help you to increase your site's traffic by retaining wayward visitors and also encourage better visitor/customer relations.

Creating a Custom 404 Error Page - Tutorial

This tutorial will teach you how to create your own 404 error pages for your web site. Why would you want to do this? The answer is that it is a great way to retain visitors to your site. If a visitor arrives at your site from an outdated link on an external web site, they will receive a 404 error page. If you do not have a custom one configured, they will receive the browser's default error page. Internet Explorer's is shown below:




When visitors see this page, most will assume that they site no longer exists and go elsewhere. If they can see that the site is still there, but the particular page does not exist, they are likely use your navigation menus or search box to try to find what they are looking for. As an example, take a look at our 404 error page.

Creating custom 404 error pages is pretty easy. If your site is hosted on a Linux, Unix, or BSD server, you need to edit your .htaccess file and add the following line:

Code :

ErrorDocument 404 /yourerrorpage.shtml


The italicized part needs to be the name and extension of your error page. Next, create your error page. Error pages are standard HTML pages and can also utilize SSI like the rest of your site. When creating this page, make sure that it is over 512 bytes in size or Internet Explorer will continue to display its own 404 pages. Note that images and graphics do not count toward the total size in this circumstance. Once this is completed upload your .htaccess file and your error page, and you should be all set.

If you are using a Windows web server, you will need to open the IIS managment console. Expand the list of web sites in the left-hand pane and right-click on the web site you want add a custom error page to and select "Properties". Click the "Custom Errors" tab in the window. Highlight HTTP Error 404 in the list of errors and click the "Edit Properties" button. This will open the "Error Mapping Properties" window. In the "Message Type" dropdown, specify that you'll be using a URL. Enter the path to your 404 error page in the URL field as in /yourerrorpage.shtml.

You can perform this exact same process for other HTTP errors such as 401 and 403.

Saturday, March 24, 2012

How to Code HTML Email Newsletters Article

Step 4: Code for Google Mail, Lotus Notes and Outlook 2007
Google Mail, Lotus Notes, and Outlook 2007 present their own unique coding challenges. Outlook 2007, believe it or not, has significantly less support for CSS than previous versions of Outlook!
Google Mail’s lack of support is a little more forgiveable — because the application runs in a browser, it cannot control the contents of the emails it displays. Consequently, Google’s engineers have had to take steps to ensure that their application displays properly regardless of the quality of the HTML or CSS in which emails are written.
As a result, Google Mail is a new web mail service that acts like an artifact of the early 1990s, when web standards were primitive. It takes some work, but it is possible to crack open a Google Mail page and see just how convoluted the services approach to rendering HTML email actually is.
For one thing, Google Mail deletes the CSS styles contained between any style tags, no matter where they appear in the email. And fonts displayed within HTML tables — the only alternative to using styles — have the odd habit of appearing larger than intended, no matter how the HTML email is structured.
The good news, however, is that if you code to account for the oddities of these email three applications, your HTML email code is more likely to display well in most, if not all, email clients. Here are some techniques that appear to work well in Google Mail and other older email software:
  • Define the background color in a td cell with the bgcolor attribute, not the CSS style.
  • As noted above, use the background attribute in the td cell for background images instead of using CSS. One side-effect of this approach is that the background image can be made as tall as needed — if the content used in your email template is likely to vary in size, using an extra-tall background image in this way allows the height of the email shrink or expand, depending on the height of the copy, from one email to the next. Remember, though, that Outlook 2007 ignores background images completely.
  • If it works better, use the padding declaration to control margins within a td cell. The margin style does not work in these cells, but padding does.
  • If you need a border around a td cell, keep in mind that Google Mail displays a border around a td cell when it’s defined in a div, but not when it’s defined as a border style in a td tag.
  • If you need a light-colored link against a dark background color, put the font definition in the td cell (so it applies to p and a tags equally) then add a color: style to the a tag.
  • If the p and a fonts appear to be different sizes, wrap the a tag in a p tag.
  • Google Mail aggressively uses the right-hand column of the Google Mail user interface, which squeezes the HTML email into the center panel. Be sure the padding style in the content tds is set to 10 pixels all round, so that text does not hit against the left and right edges.
  • When testing an HTML email with a Google Mail account, it’s likely that you’ll find that one or more font styles are missing in the td, h1, h2, p, a, and other tags. Inspect every font carefully to make sure Google Mail displays the fonts correctly.
Besides Google Mail, there’s another, less obvious hazard a programmer faces when creating HTML email: Lotus Notes. Many large corporations continue to support and upgrade their Notes installations (as of 2004, IBM reported that 95 million people used Notes).
Unfortunately, it’s impossible to tell which companies use Notes. The best approach is to follow the guidelines described in this article — the more primitive the code, the more likely it will work well, if not perfectly, with Notes.
That said, it’s quite possible that Notes will introduce to your HTML email quirks that are almost beyond belief. For example, the software can convert images to their proprietary formats, or simply ignore flawless basic HTML in one email, but display other HTML fine in another email.
A trial version of Lotus Notes is available for download if you need to test your mail in Notes — see the resource list at the end of the article. Here are a few tips that will help you convince Notes to display your HTML email properly:
  • As we discussed previously, use a container table that contains all the internal layout tables (for example, for the header, content, and footer). This keeps the email together in one chunk of HTML, so pieces of the layout are less likely to wander when displayed in Notes.
  • Create a gutter around the container table by setting the width to a percentage and/or using a cellpadding of at least 5.
  • As I mentioned earlier, avoid using a style declaration in your email’s head tag. It might be the approach that adheres to web standards, but Notes (like Google Mail) might delete your styles. Rely, instead, on inline styles within the table, td, h1, h2, p, a, and other tags.
  • Use absolute URLs to images stored on a web server. You can’t do much about Notes converting images, but using remote images might help.
  • Intra-email links, using named anchors, rarely (if ever) work in Notes. It’s simply best to avoid links that jump down the email to a specific piece of content.
  • Avoid colspans in your HTML tables. Notes — especially its earlier versions — can deal only with basic table layouts.
  • Be sure that your td cell widths are accurate. Unlike web browsers, which automatically set all cells to the widest-defined width, Notes sizes each td cell based on its defined width.
  • Centering an email layout usually won’t work in Notes. Email layouts generally have to be left-aligned.
Using these techniques to achieve a successful render in Google Mail and Lotus Notes will ensure that your emails also display fine in Outlook 2007, which uses an older HTML rendering engine. Microsoft has published details about what their email software will and won’t display properly; more details can be found in the Resources section at the end of this article).
The Email Standards Project has additional details on CSS support in Outlook 2007, and Microsoft is one of the companies at which their lobbying efforts are targeted.
Summary
Many people who receive email prefer HTML over text for a number of reasons. For programmers, though, the task of creating an HTML email that will display consistently appears both simple and horribly complex. This article has described many of the issues and strategies for creating markup that will work across email software.
What’s the best idea to take away from this article? If there’s a choice to be made between a simple email design and a more complex solution, simplicity is always the safest bet.
Further Reading
These resources offer valuable information that will help you if you want to learn more about coding HTML email.
Email Standards Project
The Email Standards Project is probably the best starting point for understanding exactly to what degree HTML and CSS are supported by different email clients. The site also maintain an acid test that can be used to compare compliance across email software, and there are several ways in which you can participate to help improve email support of web standards.
Free HTML Email Templates from Campaign Monitor and MailChimp
Both of these email delivery services actively test their templates over time with different email clients. However, there are subtle differences in the approach that each takes — Campaign Monitor places a style declaration within the head tag, while MailChimp does not. Be sure to test your final HTML code with whatever email clients are used by recipients of your email list.
Plain Text Email Design Guidelines
This article lists a number of simple techniques for making text emails easier to scan.
Testing HTML Email
From SitePoint’s sister site DesignFestival.com , this article explores testing procedures across multiple email clients.  Other related articles on DesignFestival include creating HTML email layouts and understanding multivariate testing.
Articles about Blocked Email Images by Campaign Monitor
From 2004, the ClickZ article shows how major email software compares when images are blocked or when the content is viewed in a preview pane. The Campaign Monitor article goes into greater detail, listing actual examples and ideas how to combat default image-off rendering of your emails, as well as designing your email to look okay in preview panes.
Word 2007 HTML and CSS Rendering Capabilities in Outlook 2007
The official Microsoft description of what Outlook 2007 will and will not render for HTML and CSS. Includes a link to a validator that works in Dreamweaver, as well as Microsoft editing tools.
HTML Email Tips for Web Designers
A useful, barebones list of guidelines for creating and sending email. The free email templates also are great samples to study, because the code is heavily commented and has been tested against a broad range of email software. And, finally, the Resources page includes some great links to best practices, as well as other resources.
MailChimp Email HTML Coding/Delivery Guide
Lots of great information about all aspects of HTML email, including how spam filters work.
CSS Support in HTML Emails of Hotmail, Yahoo! Mail, and Gmail by Xavier Frenette
This is excellent research that shows style-by-style results for how these three webmail services display CSS.
A Guide to CSS Support in Email
Campaign Monitor, an email service provider, has taken Xavier Frenette’s excellent work documenting CSS performance in a few email clients and expanded it to include Gmail, Hotmail, Yahoo!, and Windows Live Mail. It also covers Outlook 2003, Outlook Express, Lotus Notes, and Thunderbird on the PC, as well as Mail, Entourage, and Eudora for the Mac.
Lotus Notes Trial Software
This page offers free downloads of the latest Lotus software, which is handy if you need to test an email with the Notes client software.
Email/Web Testing Services: BrowserCam and Litmus
These are both excellent services for testing how compatible your web pages with a variety of web browsers and operating systems. For email, Browsercam simply shows you all the warts in your HTML code, even though your email might work fine in Notes, Google Mail, and other difficult email software environments. Litmus shows how your email appears in a variety of email clients.
SpamCheck
This decent, free online service tells you about the “spamminess” of your email. You also should look for an email delivery service that provides this sort of spam check.
CSS and Email, Kissing in a Tree
This excellent CSS-only approach to HTML email was published by A List Apart. NOTE: The author has written an update to this article, posted at the Campaign Monitor blog, Optimizing CSS presentation in HTML emails.
How HTML Code Affects E-Mail Deliverability
A decent overview that describes how different email services view the HTML you include in an HTML email. You can’t address every problem directly (for example, creating a clear boundary between the HTML and text versions of your email is a problem for your email service provider, if you use one) but it helps to know what happens.

Website Structure - Website Link Structure Making - Tutorial

Like most things, building a web site will be much easier if you plan ahead. To just start off building and adding without a plan usually means redeveloping your entire site as its outgrows its lack of structure. A little extra work in the beginning will save you a lot of work in the end. Follow this 3-step plan and you'll be off to a great start.

Step 1

Think about all the things you want your site to have and seperate them into specific content related categories. For example, if your site were to have Recipes, Kitchen Hints, Family Photos and Family Personal pages; the Recipes and Kitchen Hints would fall into one category and the Family items would fall into another category. From these categories you'll build a basic structure for your site. Jot down all the categories you plan to have.

Step 2

After jotting down your categories draw a simple diagram of the layout. It will help you organize your site's navigation structure. Using the sample site mentioned above, I've drawn an example site plan:
As you can see in the chart the Index Page has links to the jumpstation level pages, which are the Food Links and Family Links category pages. Think of jumpstations as topical sub-index pages into your specific content areas. The jumpstation level pages are linked back to the Index Page, to each other and downward to the individual content pages relative to that jumpstation. As you add new pages, you only need to add a link to the new page from it's respective jumpstation category. If you add an entirely new content section, you only need to create the jumpstation and tie it to the other jumpstations, keeping the boring work to a minimum.
In addition to the links from a jumpstation to its content pages, you can optionally link between the pages of a particular category, as indicated by the red lines on the bottom of the chart. I wouldn't put a link to every page in a certain category on every page within that category or you're defeating the purpose of the jumpstation. Just have a "next page" link if you do it, and when you add a new page of content you only need to update the last page in the chain with the "next page" link.
An important point to remember is that at the bottom of your navigation structure you DO NOT want only the "next" link in a chain of pages. If someone doesn't want to continue with a particular chain of pages they need an easy way to choose content from another area of your site or they'll go elsewhere. Besides, no one likes to be led around by the nose without other options.

Step 3

To make your site easy to develop and be consistent it helps to make a basic page template before starting. With a template you can just add the content and not have to continually code whole pages. For this site my template has all the basic html commands a document needs, the basic two-column structure, and the SSI code to insert the top and bottom navigation systems and the right-hand column content that is common to every page. To make a new page I just fill in the stuff in this column and save it with a new name. When I want to change the navigation structure or right-hand column content, I only have to update one file for each to have that change reflected on my whole site.
Instructions for using SSI can be found in the members site. You may want to read about the benefits of becoming an Inner Circle member.
Your navigation structure can make or break your site. All my pages have the same structure as seen at the top or bottom of this page. Each page has the links to the Home page and all the jumpstations. You can go from one area of my site to a completely different area with one click from any page. Now that's navigating made easy! If you're welcoming contact from your visitors then include your contact link on each page.

Content Creation - Content Creation For Website Tutorial

To put it bluntly, your content can cause others to wish their site was a good as yours—or allow it to drown in a sea of mediocrity and sameness! There are four keys to successful content creation:
Creativity
Creativity in presentation and layout sets your site apart visually.
Uniqueness
Writing in your own style or voice, using your own words, is the uniqueness that sets your site apart mentally.
Quality
There is no substitute for quality. Without quality your creativity and uniqueness will be lost in the noise of information overload.
Updates
Adding new material regularly brings visitors back for more. Too often web sites sit there gathering digital dust with nothing new added for weeks or months at a time. I've been guilty of this myself when I have big projects underway, such as writing another book, and I can definitely see a slow-down in traffic when I let that happen.

So What's Popular?

To build your site around what's currently popular is to build on shifting sand. Istead, let's look at how successful sites are developed, because a successful site can be developed around nearly any subject matter. The online population is just too large for there to be many topics that can't enjoy a good measure of success. Granted, some topics will have a bigger audience, but they will also have more competition for that audience. Building a site around what you enjoy can often bring more success to you than if you deliberately set out to build a popular site about a topic you're not that keen about.
Sites that enjoy high traffic and keep 'em coming back have one or more of the following elements. The more of these elements you incorporate, the better your chances of developing a successful web presence.

Depth

Create an ever-expanding world. Even if you plan on a specialized site you can find different subjects to tie in with it in an entertaining or useful way. If you were doing a site on Stress in the Work Place, for example, you could have serious articles about ways to cope and manage stress, but you could also include humorous looks at ways not to deal with stress. Try to be creative. Try to imagine what you'd find if you were the visitor and someone else were making the site. What would David Letterman do with it, or Rush Limbaugh, or Dear Abby, or anyone you admire for their creativity, talent, intelligence, or for other qualities you can emulate.

Originality

Are you a recreational poet? Are you good at drawing? Do you write short stories or tell good jokes? Put it up—or if that's not what your site is about, think of ways to incorporate those traits into what you are building. Whatever makes you unique and sets you apart from others is a great place to start. Everyone is good at something. Think about your strengths.
Know this about yourself...
From the beginning of time to all eternity, there is and will always be only one you. Celebrate who you are, for no one can be you better than you can, and you can be no one else better than you can be yourself.
That makes you very special indeed. You are far more rare than one-in-a-million. You ARE a singularly unique and wonderful person in a cosmic ocean of eternity! Think about that. I mean really think about that.
When you really understand you are that special you never have to play follow-the-leader. The "leader" you follow may not know where he or she is going, or may not be happy on their chosen path. Even if they are, their path is not your path. Being a first-rate you is always better than being a second-rate copy of someone else. You're a beautiful person! Be that person rather than trying to be like someone else. You can never succeed at being someone else, you can only succeed at being yourself.
It can be pretty boring to cruise through a site with absolutely no personality to it because the webmaster is playing monkey-see monkey-do. If you're not being yourself, who will? People don't want to read the same old stuff they can read in a thousand other places that all sound the same. They would much rather read about your unique point of view as long as you're willing to put forth the effort it takes to present your point of view in a coherent manner, rather than just rambling on and on without a good flow of thought.

Serve a Purpose

Serving the needs of others means traffic for you. For me, it means sharing my talent for graphics, teaching, and my . . . um, let's call it my unique sense of humor. I manage to sell enough of my products along the way that I earn my living at this. Maybe in time I can sell enough to become filthy, stinking rich, who knows? I wouldn't mind being a little stinker in that way! I try to entertain as I serve a purpose. Sure, some folks think I'm nuts, but that's just a lucky guess. Think about what kind of service you could offer. Put up a help page on a topic you know about. You don't have to be an expert, there are plenty of people who know less. If you get questions you don't know the answer to, find it. Then you have new content and something fresh to offer. There are many ways to serve the internet community, find your own angle and go with it.
Sidenote: I was no expert when I first started posting HTML tutorials. I only did it because I kept getting emails asking how I did this or did that. After answering the same questions over and over I made some tutorials. One thing led to another and a publisher called me out of the blue and asked me to write a book on web site design for them. You just never know what interesting and profitable twists life will take when you serve others.

Variety

You can offer as many experiences as you can think of. I have more planned than I have time to implement. Build depth with variety. You needn't do it all at once and create a big project. Work on it one idea at a time and do it up right. Become a mini-expert on the things that interest you. If you work on your interests you're likely to do a good job of it and others will recognize your effort and reward you with return visits, email, links to your site, and purchase your products or services if that is your focus. In life, and on the Internet, when you give, you set the wheels in motion to receive.

Friendliness

Think about your favorite sites. Do they have a sterile, officious approach or do they have a bit of personality? The answer for most is the second choice. One of the nicest unsolicited comments I've ever received said..."I really love your site, it feels like you're right there with me." Makes a fella feel good. Doesn't pay the bills but it feels pretty good just the same. The point is, talk to your guests like you talk to your friends and you're on the right track, providing you're not a complete jerk in real life. If you are a jerk in real life—grow up—or you will always suffer the consequences of your attitude. Even business sites can benefit from having a little personality to them. One of the complaints I've noticed about web sites is that they are sterile. No personality, sterile antiseptic writing, and a lack of imagination and creativity all add up to BORING with a capital SNORE!

Rules of Thumb

Here are a few rules of thumb for developing a web site. These are not the only considerations, but they are the most important ones that apply to all topics.
  • Create your own content. Copying others is not only redundant and unimaginative, it could be illegal. Each page published has inherent copyright protection whether a copyright notice is posted or not. Fines can go as high as $100,000 plus damages. Original content is the best content.
  • Keep download times in mind as you build. Try to keep each page under 40k and 4 screen lengths. I call it the Rule of 4's - mainly because it's my rule so I can call it what I like. That, and it made more sense than calling it pudding.
  • Be yourself. There will be plenty of folks who will like you for who you are. This is especially true for personal sites. People visit personal home pages to learn about YOU...your originality, your creativy, your uniqueness. You know you're wonderful, let your light shine!
  • Keep developing and expanding on ideas that are working for you. If you have a page you're happy with or get compliments about, find a way to expand the theme with related material or simply go for a series of pages with the same topic. That's basically how my site has grown from the original site of about 15 pages, to over 500 pages by the end of year 2000. (Many pages have since been moved to the member site, which has even more pages than that.)
  • Find a way to serve. In many ways the net is one big sharing community. Find your niche, serve it well, and you'll be rewarded.
  • Variety is the spice of life! Expand the web world of you with all the things that interest and amuse your own self. If it's something you're interested in, so too will others be.

Navigation Structure - Website Navigation Structure Making Tutorial

Avoid My Newbie Mistake!

In the first incarnation of Boogie Jack's (way back in 1997) I used to provide a link to every page from every page. It was easy to navigate, but as my site grew larger this navigation structure quickly became a big chore just to add one new page. You can learn from my mistake and set your navigation structure up right from the beginning, rather than having to redesign out of necessity as I did. The best way to provide navigation is using server side includes (SSI). SSI can call a file into a web page. For example, I use SSI to load my navigation system into the top and bottom of each page. I can change one file on my site and have my site navigation changed on every page. You can learn more about SSI as an Inner Circle member or by grabbing a copy of my book, Web Site Design Made Easy. Not everyone has SSI available to them, so I'll show you the best practice that is available to everyone.

A Better Way

When I designed my next navigation system I created topical sub-indexes that I called jumpstations. I called them that because it sounded more intelligent than calling them Fred. I still use jumpstations. For example, the Web Design Tutorials index is the jumpstation you used to access this tutorial unless you came to this page directly from another site. When I add a new HTML tutorial, I only have to update the main Web Design Tutorials jumpstation. Jumpstations can also help with search engine positioning because the content is so tightly focused.
In some areas I've also put a "next page" link to the next page in a particular content circle. Using this page for an example, it is part two of a 4-part tutorial on site planning, so each page is linked to the next page to make it easy to go on to the next tutorial without backtracking to the jumpstation page.
All the main jumpstation indexes are listed at the top and bottom of each page so at any point you can jump to another area of my site without backtracking. After I came up with jumpstations, visitors were never more than one to three clicks away from what they're looking for even though I had over 500 pages of content! Some content has since been moved to my Inner Circle members area.
Your site visitors will appreciate the ease of navigation you provide and will be more inclined to explore more of your content—if you offer quality and original content. If you don't have quality, original content, little else will help you retain visitors or gain new visitors.

At the Very Least...

Always have a link to your home page (index) from every page of your site. You have no control over which page someone else may link to within your site, or which page turns up in search results. Many newbies won't know how to get to your main page if they arrive on a page without a home link. You think not? Every month people come here from search engines where they searched specifically for "BoogieJack.com" so most of those folks probably didn't know how to type a web address they already knew into their browser's address bar.

Another Good Idea

I also like to keep my links in the same set up. You'll notice my links set up at the bottom is the same on every page. Once you get it set up the way you want you only need to copy and paste for your other pages. Easy! And your guests quickly become familiar with the way your site is arranged so it aids in their navigation and enjoyment.

Test It

Be sure to test all of your links before going public with your site. You don't want your first email to be complaints about this link or that link not working. Speaking of email, if you want to receive letters from your guests you should also include your contact link on every page. Someone may want to write and tell you you're the coolest cat since Felix, but if there isn't a contact link on the page they are on, they may well just move on rather than hunt for it - and you may never get that ego boost!

A word about frames...

Some people advocate using frames to have a navigation system that allows you to change one file that will be reflected across your entire site, but—did you know there is a large percentage of surfers who hate frames? There are even "I Hate Frames" clubs. A quick search on Google for "hate frames" yielded 223,000 web sites that talk about their hatred of frames . . . and those are just the people that hate them enough to make web pages about them, millions more just dislike them, but not enough to make a web page about it. If you're thinking of building a framed site, that's not the only drawback. You'll also have trouble getting a framed site indexed with search engines, and even if you do, getting a good ranking is also more difficult, and that is plenty hard enough as it is.
Frames also prevent users from bookmarking their favorite pages because all they get is the frameset page. Then there is the frame recursion problem where frames get nested inside other frames, sometimes to the point where a browser crashes. I recommend thinking long and hard about the benefits and drawbacks of frames before using them.

A word about JavaScript...

Another way to read a navigation system into a page is with an external JavaScript file. With that you can update the one file and have that update reflected throughout your site. I use an external JavaScript to rotate the daily specials you see at the top of each page. I wouldn't use it for my navigation system though. The drawback is that some people have JavaScript turned off in their browsers. If JavaScript is not enabled, those visitors won't see any navigation system. I can live with someone not seeing my daily specials, but they have to be able to navigate my site.

HTML Tutorial: Create a Web Page

Are you ready to make your first web page? You need Notepad or another text editor open—a crash helmet is optional. Just kidding! HTML is not dangerous.
If you're using Notepad, first go to the Format menu and put a check mark by Word Wrap. This keeps your text from appearing as one long line that you'd have to scroll sideways to see.
As noted earlier, an HTML document starts off with:
<html> 
This tells the browser it's an HTML document. Clever, huh? Go ahead and type <html> into Notepad now. Next is the:
<head>
...tag. Now that you're a an old hand at typing HTML commands, type the <head> tag under your <html> tag.
Note: Technically, you don't actually have to type the head tag under the html tag, but it will help you to visualize the structure. I often start code on new lines because it breaks up the source code with white space, making it much easier to locate the places you want to edit later on. As your page complexity grows with your skill level, this habit can be a valuable time-saver.
There are several items that can go in between the opening head tag and closing head tag, but for a simple page like the one we're creating, we're only concerned with one, and that is the:
<title>
...tag. The title tag, as you might guess, contains the title of your web page. The title shows up in the title bar at the top of the browser window, as the text when someone bookmarks your page, and as the link text of a search engine query on many search engines. If you look at the top of your browser you should see the words, "Making Your First Web Page" in the title bar because that's the title I gave this page. You'll also use your first cancel command.
</title>
The cancel command, also called the close command, means you are canceling a previously opened HTML element (tag). In this case, it's telling the browser that the TITLE of the page is complete, or canceled. The forward slash before an HTML element tells the browser that element has been canceled. Note that an element and command are the same thing. Go ahead and add:
<title>My First Web Page</title>
...to your HTML document under the HEAD tag now. Since that is the only element we're adding to the head section, and because you've become such a whiz-bang ding-dang student at typing HTML commands, go ahead and type the </head> command under your title line to cancel the HEAD element.
Next is the:
<body>
...tag. The area between the opening and closing body tags is where you put the content you want to show up on the web page when viewed with a browser. Other HTML elements are used within this area as well, which allow you to add images, create paragraph spaces, and to code other display instructions. These other formatting tags do not show up on the web page, but merely tell the browser how to display the information you want to present. When you've completed this tutorial you can go to the individual tutorials and add whatever elements you wish to play around with to your first web page. As I said, after the BODY tag is where you put the content you want to show on a web page. Your pictures, jokes, links and all else goes here. So for now, just enter the <body> tag under the </head> tag and type a brief message for demonstration purposes. Anything will do, such as "Boogie Jack is so kind for providing these tutorials I think I'll make his next mortgage payment for him." Yeah, that works for me.
Done? Great! You can get my address from my contact page later to send the mortgage payment to me, but for now, we're almost done. The last thing to do is to cancel the BODY and HTML elements. In HTML we always cancel tags in the reverse order they were opened, so type:
</body>
</html> 
...under your pledge to make my mortgage payment. Your test page should now look like this:
<html>
<head>
<title>My First Web Page</title>
</head>
<body>
Boogie Jack is so kind for providing these tutorials I'm going to make his next mortgage payment for him. I might even name my next son Boogie Jack, or Boogie Jill if it's a girl!
</body>
</html>
Okay, so I might have ad-libbed a little in the content section, but naming your baby Boogie Jack or Boogie Jill is better than naming him or her Wubbyknuckles! I mean, come on, let's get real. The last thing to do is to save the page you just made. You can call this test page anything, but when you build a web site for real, your home page should always be called index.html. You might as well save this one under that name.
It should be noted that some people name their documents with a .htm extension instead of .html, but not all servers look for the .htm extension when it can't find .html, so it's wise to get in the habit of saving them as .html right now.
Note: When saving your document, enclose it in quotation marks to prevent your system from adding .txt (for text file) to the end. In the box where you type the name you want to save the file under, type it as:
"index.html"
...and be sure to include the quotation marks around the name and file extension.
Now that you've saved it, open it in your browser and see what you've made! To do that just hit Control and (the letter) O on your keyboard then hit the Browse (IE) or Choose File (Netscape) button to navigate your computer. Find the trial index page you just made and click it, then click OK. Then just hit the back button to return here.

HTML Tutorial: HTML Tag Attributes and Values

If you've followed this series from the beginning you've already learned what HTML tags are and the you've learned the basic HTML skeleton. Now I'll introduce a new tag, plus tag attributes and values. Tag attributes and values provide additional instructions to the browser. For example, suppose you want to put an image on your web page. An image tag is written as follows:
<img />
That's the basic image tag, but it doesn't tell the browser which image to display or where to find it. We give the browser that information by adding the source attribute and value. The source attribute is written as src, with the vowels removed from the word source. If the image you wanted to add was a picture of your new bicycle and the picture was saved as bike.jpg, and it was kept in the same folder as your HTML page, then the attribute and value you'd add to the image source tag is:
src="bike.jpg"
In that example, src is the attribute and bike.jpg is the value of the attribute. IN HTML, an attribute usually either indentifies a source or defines an element. In this case, the attribute identifies the image source. An example of an attribute defining an element would be adding the width and height attributes and values to the image.
So then, an attribute defines or identifies an element, and the attribute has a value attached to it by the equal sign (=), with the actual value enclosed in quotation marks. The entire code then, would be written as:
<img src="bike.jpg" />
Note: Most HTML elements have a corresponding closing tag, but there isn't a closing tag for the image element. To make HTML tags that don't have a corresponding closing tag up to date, which means compliant with XHTML, a space and forward slash is added to the end of the tag, thereby making it a self-closed tag. This is optional, however, and coding an image without the trailing space/slash is perfectly valid at this time.

HTML Tutorial: Basic HTML Tutorial - Basic HTML Tags

Below are the tags every HTML document must have. In the past you could type the HTML tags in either lower case or capital letters, but there are a few that cause problems in certain browsers when entered in upper case.
Nowadays, because other languages such as XHTML require that tags be in lower case, and because many people are calling for the same requirement for HTML, I strongly urge you to code in lower case at all times. It may seem fussy, but cross-platform display consistency is the goal, and that can only be accomplished by having standards everyone follows.
These tags are the bare necessities:
<html>
<head>
<title> Title Text Goes Here </title>
</head>
<body>
Content Area
</body>
</html>
That is the basic HTML skeleton, but it's not really as confusing as it looks. I've shown the HTML tags in red, but the tags themselves do not show up on a web page unless an error is made. They are in the "source code," which is simply the underlying text file that contains the HTML code and content you want displayed for people see. The browser interprets the HTML tags in the source code and displays your content according to those tags. It may help you to understand the concept by thinking of HTML tags as little instruction sets that inform the browser how to display the actual content.
If the above code were a real web page, the words "Content Area" would be the only thing that would show up in a browser window.
Here's a brief explanation of each tag...
<html>
Identifies the language used (file type) for the browser, in this case, a web page written in HTML language.
<head>
Acts as a container for the page title and meta data. The title is necessary, but meta data is not. You can learn more about meta data later, I don't want to clutter this up with too much information.
<title>
The title is the name of the page. The title shows up in the title bar at the top of your browser, as the text for bookmarks unless it's changed, and in some search engines as the link text. If you look at the very top of your browser window you should see "The HTML Skeleton Explained" as the title of this web page.
</title>
Closes the title. The forward slash ( / ) in front of the HTML element means that command is now canceled.
</head>
Closes the head section.
<body>
Between the opening and closing body tags is where you place the actual content you want displayed to the public.
</body>
Closes the body section
</html>
Closes the html element, end of page.

HTML Tutorial: What is HTML?

HTML is short for HyperText Markup Language. How the language got so hyper is beyond me, too much caffeine maybe, but anyway, web pages are built using html tags.
So that you understand what a "tag" is, here is an example:
<html>
Each tag consists of the containers, which are the lesser than (<) and greater than (>) arrows, and the HTML element within them. The arrows and the HTML element together are commonly called an HTML tag, or an HTML command by some. The example tag above is the beginning of an HTML document. It tells the browser the document is a page written in the HTML language so it can be interpreted and displayed according to the specifics of that language. There are dozens of tags, but only a few that you have to know to make a simple web page. If it looks confusing, just play along, it really isn't that difficult. These lessons in the basic section will walk you through it one step at a time. In about 20 minutes you'll have made your first web page!
To begin with, you'll need a browser, (d-oh!) and a text editor. There are HTML editors that make web page building easier for some people, but for this tutorial we'll assume you don't have one. If you do and want to use it, feel free, as long as it allows you to enter code directly it doesn't matter what you use. It is best to learn to code by hand even if you plan on using an HTML editor later on. That's the only way you'll know how to troubleshoot problems, and problems do arise from time to time even for the most skilled webmasters.
I use Notepad, so will refer to that later in this tutorial. Notepad comes with every Windows PC, and if you learn the simple language, it's all you really need. You'll find it in your Accessories folder. Mac users will probably want to use SimpleText.

How To Make A Web Page And Create A Website

Congratulations on your decision to learn how to make a web page! Having your own website provides you with the ultimate way to communicate your message to the world. There is absolutely no better way to reach your target audience than by having your own website. Whether you are interested in designing a business website or would like to create a website that is for personal use, you have just taken the first step towards making your dream a reality.

Build a Website

Now that you have made the decision to build your website, how exactly do you do that? What options do you have? Well, that's a great question and one that you will find the answer to right here.

First of all, there are some things that need to be taken into consideration. Your first step will be to think about your budget and how much money you really want to invest in developing your website and how much time you have to invest.

If you don't have a big budget, but have a lot of time, you may want to consider learning how to design your own website and write HTML code. However, if you don't have a lot of time, but have a larger budget, you may want to simply hire a professional web designer to build your web pages for you.

Website Design Options

Create a WebsiteThere are also some other website design options you may be interested in, such as using some pre-designed web page templates you can edit. Or, you can even use an online site building system that will enable you to build your website right online without having to learn any HTML coding. You may also want to consider using a software program you install on your computer to create your own website. Or, better yet, you can use a combination of options, such as purchasing a web design course and using web page templates to make your web pages.

How to Make a Web Page using HTML Video

Although the following video will teach you how to write your own HTML code, you won't have to learn HTML codes unless you choose to. There are many ways you can make your own web pages, such as using an HTML editor, ect.. However, it is HIGHLY recommended that you learn Hyper Text Markup Language (HTML), as it is very easy to learn and will enable you to create and edit your web pages whenever you'd like.
Above all else, make sure that you take some time to educate yourself before you begin. For further information on learning how to make a web page or create a website, please click on the links on the right.
To your success!

Creating an HTML Email Form - Tutorial

If you would like to provide your web site visitors with a simple way to contact you from your web site, but really don't want to display your email address, this HTML form code may be what you're looking for.

You can create a simple form, as displayed below, to enable your visitors to send you comments, questions, product support requests, or whatever you'd like.

Name:
Email:
Comment:
 
Copy and paste the following HTML code into the HTML portion of your web page:

<FORM action="mailto:you@yourdomain.com" method="post" enctype="text/plain">
<TABLE BORDER="0" CELLSPACING="0" CELLPADDING="4" WIDTH="90%">
<TR>
<TD width="30%"><DIV align="right">
<B>Name:</B>
</DIV>
</TD>
<TD width="70%">
<INPUT type="text" name="name" size="20">
</TD>
</TR>
<TR>
<TD><DIV align="right"><B>Email:</B></DIV>
</TD>
<TD>
<INPUT type="text" name="email" size="20">
</TD>
</TR>
<TR>
<TD><DIV align="right">
<B>Comment:</B>
</DIV>
</TD>
<TD><TEXTAREA name="comment" cols="30" wrap="virtual" rows="4">
</TEXTAREA>
</TD></TR>
<TR>
<TD>&nbsp;</TD>
<TD>
<INPUT type="submit" name="submit" value="Submit">
<INPUT type="reset" name="reset" value="Reset">
</TD></TR>
</TABLE>
</FORM>
Change the text indicated in red to your email address.

Displaying an email form on your web page provides a great way to enable your visitors to contact you.