Because there's more to life than one's self, status or material things.
(for those dealing with real-life issues and who enjoy participating in stimulating discussions on issues and ideas, crave the thrill of geographic, mental and spiritual exploration and discovery and value local and global community, belonging and old and new friendships)
Are popularity, accomplishment, recognition, respect, wealth, power, fame, even religion not cutting it? Have you tried all the world’s got to offer and in doing so come up empty and unsatisfied? Feel like there's nowhere to turn? How to make your life explode with relevance.
Was Jesus just a man who married Mary Magdalene? Has the church been hiding information from us for years about Jesus? Don't decide too quickly. Examine the evidence first.
Think conclusive cases can't be made for the Bible and Jesus' claim to be the God/Man Messiah? You'd be surprised. The overwhelming mountain of factual, historical evidence is too compelling, too convincing to be ignored.
'' This book is, quite simply, the most easy to understand, fun, and comprehensive guide to learning HTML and CSS!'' - SitePoint.com
Note: The following steps are for those who want to create a personal or nonprofit home page or web site, not a commercial one. For that, check out these e-commerce resources.
Use a standards-compliant and accessibility-friendly editor or template, or learn HTML 4.01 Strict or XHTML 1.1
WYSIWYG (What You See Is What You Get) editors allow you to create a web page without having to learn and use HTML or XHTML code (more on them later), but they don't allow you to have as much control over its appearance.
If you don't mind that limitation, and want to comply with web standards, use only one of the following WYSIWYG (What You See Is What You Get) web page editors or the TypePad web service (for web journals, photo albums, etc.).
All other WYSIWYG editors create HTML and XHTML that isn't standards-compliant, and as a result is inaccessible to visitors with disabilities.)
As with WYSIWYG editors, using a standards-compliant and accessibility-friendly template allows you to create a web page without having to learn and use HTML or XHTML code, but with limited control over its appearance.
If you don't mind that limitation, and want to comply with web standards, use only one of the following sites' templates. skip
Learning and editing HTML or XHTML code in a nonWYSIWYG editor gives you more control over how your web page looks.
The original purpose of web page code was to make it easy for database servers, search engines, etc. to find what they and you are looking for and to exchange and share that data.
To do that, a set of standard specifications called GML (Generalized Markup Language) was created, which evolved into SGML (Standard Generalized Markup Language). It tells devices, web browsers and other software what's called the structure of a web page, a description of its content, as opposed to its presentation, or how it looks.
But it's so complex and hard to learn, that the web standards folks at the World Wide Web Consortium (W3C) created HTML, a limited but easy-to-learn programming language.
Unfortunately however, due to fierce browser wars, Microsoft and Netscape later added code to it designed to present or display data, instead of describe them, which made them less searchable.
And unfortunately W3C incorporated Netscape's and Microsoft's extensions in HTML 3.2. Because of that, people got used to coding their web pages improperly, instead of keeping structure and presentation separate.
To correct that mistake and bring us slowly and painfully but surely back to where data is easy to search again, the folks at W3C separated it into three forms, signified by Document Type Definitions, commonly referred to as DTD: Strict, which doesn't have any presentational code in it, and Transitional and Frames, which do, for backwards compatability.
They also created XML, a version of SGML that's slightly easier, but still difficult, to learn, and XHTML, a replacement for HTML and a bridge between HTML and XML, designed to both describe data and display them, without making them less searchable.
So web browser programmers, as well-meaning as they were, got us away from the original purpose. HTML Transitional and Frames, because of the presentational code they added to them, aren't able to make data easy to find.
But now there's XHTML 1.0 Strict and XHTML 1.1, which are. And the way it's done is by keeping presentation (colors, fonts, layout, positioning) separate from structure, which includes using CSS (Cascading Style Sheets) and coding for semantics, and depending on your point of view, keeping structure separate from content as well.
But there's a catch. Most servers are serving XHTML web pages to web browsers as regular, but invalid, HTML, or as some programmers call it, tag soup. And only the addition of a bit of code will get your web site's server to serve your web pages as XHTML.
The problem is, all versions of Internet Explorer - including 7.0 - are currently unable to render, or process, pages served as XHTML (actually ''application/xml+xhtml'' - this is called a MIME type and is in the web server's "Content-type" HTTP header - HTML uses a ''text/html'' MIME type).
And Mozilla-based browsers are currently unable to display such pages as they render them. They only display them after rendering the whole page, which causes a delay of a dozen seconds or more on a dialup connection.
So others may disagree, but I personally recommend coding with HTML 4.01 Strict for now to get used to keeping structure and presentation separate with CSS, and consider implementing HTML5 (Web Applications 1.0) when it's issued, until you can someday serve your XHTML pages to Internet Explorer as XHTML and to Mozilla-based browsers without a delay.
If in spite of those and other drawbacks you decide to create your web page with XHTML 1.1, the current standard, and your hosting account has access to PHP, Python or an .htaccess file, you can serve XHTML pages to Internet Explorer as text/html with one of the following methods, but that'll make the code invalid, so I don't recommend it.
(some more information on XHTML's ''dirty little secret,'' the bit of code to serve a page as text/html to Internet Explorer, and as valid XHTML 1.1 to XHTML-supporting browsers, and what's required to make it work)
If your hosting account doesn't have access to PHP, Python or an .htaccess file, I recommend converting your XHTML pages to HTML 4.01 Strict instead for Internet Explorer. If you're willing to learn a new language, convert XHTML pages to HTML 4.01 Strict with XSLT via one of these implementations for PHP, Python and other server-side languages. XSLT stands for eXtensible Stylesheet Language Transformations and is a complex language that requires in-depth knowledge of XSLT functions and other related technologies like XPath.)
If you don't want to learn XSLT, use one of the following free XSLT tools: skip
For nonWYSIWYG editing, use one of these free editors that come with the HTML Tidy validator and support XHTML. (Be sure to clean and validate your code with HTML Tidy to make them standards-compliant before uploading your pages to your web site.)
HTML and XHTML come in two main versions, Transitional and Strict. And each web page needs what's called a DOCTYPE or DTD (Document Type Definition) to tell the browser what W3C standards it should apply to the page and how strictly it should follow those standards.
If, after making your code comply with the lastest standards and making it as accessible as possible, you don't use a DOCTYPE or use an outdated DOCTYPE, Internet Explorer and possibly some other browsers will detect your valid, accessible code as invalid, nonstandard ''tag soup,'' switch to Quirks Mode (called doctype switching) and render it in compliance with outdated standards, instead of in Strict or Standards Mode in compliance with the current standards.
This will cause your accessible web page to have accessibility problems.
To make your pages accessible to as many visitors and devices as possible, I recommend avoiding using the Transitional DOCTYPE and using or converting to the Strict DOCTYPE.
Use a scalable, or liquid design to make your web pages accessible to as many sighted visitors as possible, no matter what screen size, resolution, or browser they view your site with.
Then test your pages in as many different browsers and devices (pdas, cell phones, etc.) as you can to see how they look, and with a screen reader to hear how it sounds, and adjust your code if necessary or possible.
NOTE: It's currently not possible to make a web page accessible to all user agents, as the W3C folks call them. So either create separate pages for different user agents, or try to make your pages accessible to as many of them as you can.
Instead, if your site doesn't have access to PHP, use HForm.com's inexpensive e-mail form service in combination with a standards-compliant and accessible e-mail form. Read one of the following guides to learn how. HForm uses your account number instead of your e-mail address in your e-mail form code.
If your web site has access to PHP, create a customized e-mail form with ASoft's AContact Form (rated 5 out of 5 by HotScripts.com), a free, customizable, PHP, contact form script that prevents e-mail address harvesting, bandwidth theft and automatic form filling by spam bots (with a customizable verification word instead of an image for accessibility).
AContact Form puts your e-mail address in a separate PHP script file, which is inaccessible to spammers' harvesting bots, instead of your e-mail form code.
Note: You'll need to either tell others in person or by e-mail what the word is, or post the word on the page your contact form is on, so visitors will know what to enter. But don't make it appear automatically in the form entry with the value attribute! That will disable it's protection!
Then if you start getting spam from that form, change the word both in the config file and on your form page. But that should be very rare, since instead of visiting and viewing the form themselves, most spammers search for contact forms with software which won't be able to learn the word. skip
Other free, secure form scripts, tutorial and image converters:
Tip 3: If your web host supports SSI (Server Side Includes), use this feature to download and display your navigation links on every web page from one external file, so that when you need to make changes to them, you can do it only once to that one file, instead of to every web page.
CAUTION: If you'll be using highly confidential ASP / PHP code (or any other web technology), like your database connection string or some business logic, in your include file, make sure the include file is named .asp/.php so that no one can open the include file and see your code.
You'll want to write your HTML or XHTML carefully, of course, but none of us are perfect. We're only human, so once in a while you'll make mistakes which may make content on your web pages inaccessible to some visitors or devices.
These mistakes can be found and for the most part, corrected by a program called a linter. And they can be pointed out by another program called a validator, which compares your code with W3C's standards and lists the errors. You then need to correct the errors manually.
Here are some articles on the benefits of validation:skip
''W3C has made 2 programs to verify the HTML syntax. Both uses different algorithms: - W3C Validator is based on SGML and the verification of the DTD of the page (defined in the DOCTYPE) - HTML Tidy is called a 'linter', [or] lexer. In short, it parses the page and tr[ies] to understand the errors. Both technologies have their advantages and disadvantages.'' - Marc's CyberHome
''Unlike a validator, a linter doesn't check specifically against a published set of rules for HTML. Instead, it looks for common mistakes (and sometimes just poor formatting that isn't necessarily technically wrong) and points them out... Since linters and validators look for different types of errors on a web page, it's very often a good idea to use them both.'' - AnyBrowser.org
First, run your web pages through HTML Tidy to fix, or try to fix, most of the HTML or XHTML errors you may have made. (Make sure the Output to XHTML setting is set to YES if you want your web pages to be in XHTML.)
And if you want to check your web pages for accessibility problems to visitors with disabilities, or older computers, software or devices with TidyUI for example, set the Accessibility setting to A, AA or AAA. After running TidyUI on a page, the accessibility problems and other errors will be listed in the bottom window if you maximize TidyUI to fit your whole screen.
Then make sure to either add the accessibility code you need manually for the problems it didn't fix, or if you have Windows, create the necessary accessibility code with A-Prompt (see below). skip
After cleaning the code in your pages with HTML Tidy, check your HTML or XHTML with W3C's HTML / HXMTL validator to make sure it's valid and fix any remaining errors manually. Also check your CSS with W3C's CSS validator, if you have any.
Note: You need to have DOCTYPE information in your web pages before using the HTML / XHTML validator.
Here's the DOCTYPE information to add to your web pages:
If you want free web space without banner ads or popup ads on your web pages, check out these free web space providers, and these. Look for the ones that don't require you to register or transfer a domain name. Don't ask me how they can afford it, but such providers really do exist! (Some restrictions apply.)
RootsWeb's Freepages provides free and unlimited web space for genealogy-related web sites. (One banner ad will appear at the top of each page and one at the bottom.) (Some restrictions apply.)
If you don't want restrictions on your account, find super cheap web hosting at FindMyHosting.com. (You won't believe how cheap these are!)
If you have links to other sites's web pages on your web pages, prevent broken links, also known as link rot, by checking them often with Xenu's Link Sleuth, to find pages which have been moved or removed.
Then when you find that a page is no longer where it was when you linked to it, try to find its new address by searching for the title of the page with the search engine on the web site that hosted it or, if it doesn't have one or it can't find the page, search for the page's title, enclosed by quotation marks: ''Page Title'', at one of the top search engines.
Note: Search engines' cached copies of pages are stored for a fairly short time, so I don't recommend linking to them.
If you can't find the page's new location in the search results, search Archive.org's Wayback Machine for the page's old location. If you find a viewable copy of the page, replace the old location's URL in the broken link with the URL of the viewable copy. Otherwise, remove the broken link.
Tip 2: Use an FTP Client
If your web host doesn't have an upload utility to upload your web pages to their server with, you'll need to upload them with an FTP client.
I recommend avoiding the following FTP clients for the reasons I give for each one.
AceFTP (saves your password by default and can't be deleted)
SmartFTP (saves your password by default, no local files window in the default layout and you have to click and drag to
FTP Navigator (only starts in administrator account and the tranfer log is unhelpful) and...
FreeFTP (no transfer log and it doesn't disconnect).
I recommend using FileZilla, Core FTP or ESftp (requires flash player). They let you choose if you want to save your password before connecting, they have a helpful transfer log and you can transfer files by double-clicking them.
If your web pages seem boring and you want to make them fun and interesting, there are many web sites that provide scripts, gizmos and services you can add to your web pages for free. If you have your own domain name, check out the free scripts. If you don't have your own domain name, check out the remotely-hosted scripts.