• Movable Type - offers a free single-user edition that supports one user and unlimited blogs. Requires perl and a MySQL, SQLite or Berkeley database.
• Wordpress - Requires php and a MySQL database.
• NucleusCMS - Requires php and a MySQL database.
• b2evolution - Requires php and a MySQL database.
• TextPattern - Requires php and a MySQL database.
• Serendipity - Requires php and a MySQL database.
• boastMachine - Requires php and a MySQL database.
• Geeklog - Requires php and a MySQL database.
• ExpressionEngine - Comes in a limited capability free version. Requires php and a MySQL database.

cd \inetpub\adminscripts
cscript adsutil.vbs set w3svc/MaxConnections 40
iisreset
 

]]>The first command connects you to the adminscripts folder. The second command runs a script that sets the MaxConnections value in the IIS metabase to 40 (the maximum allowed). The third command (iisreset) shuts down and then restarts IIS.

quote:

---

Welcome User

---

quote:

---

Welcome Entelligence

---

Pick a markup language and include a valid DOCTYPE.

Pick a standard language for your markup, and code in accordance to its guidelines. Add the proper DOCTYPE at the top so the browser gets a heads up as to how your page should look. A DOCTYPE is important because without it, the browser will usually fall back on "quirks mode", rendering whatever tags it comes across basically up to its own interperetation.

Put all style information about the page into CSS.

Many of the old style tags found in HTML4 are deprecated. CSS is the new standard for defining how a page should look. CSS code can be placed either inline with the markup, or linked to an external file.

Avoid vendor-specific tags.

Some companies like Microsoft and Netscape have added to the language by coming up with coming up with codes that only work in their browsers. These additions are not approved by the W3C (although sometimes they are incorporated later on) and they will not provide a consistent look and feel for your site.

Validate your code.

Use tools like The W3C Markup Validation Service for your HTML and The W3C CSS Validation Service to make sure your pages are up to spec. There are also tools for checking accessibility standards, such as Cynthia.

Use meaningful, well-formed link text.

Links are the heart and soul of hypertext pages. You want to make sure the text you use in your link is meaningful to the link it represents, even if it's out of context of the page. Don't ever use the phrase "click here". Most people already know what to when presented with a link, so these directions are redundant. Also it's not relevant to the page you're linking to. A good rule of thumb is to think of links as nouns, not verbs. So avoid linking to action words, only people, places, and things. One good reason to do this is because people with vision impairments may use screen readers when visiting your page. A screen reader is software that speaks the text on the page with the use of a text-to-speech engine. A user with a screen reader may be tabbing through the links on your page and they need to know what each link represents.

Avoid use of frames.

In almost all cases use of frames is not needed and results in problems in accessibility, browser compatibility, search engine spidering and links found in search results. Read more in /faq/11216

Test your pages in as many browsers and platforms as possible.

Don't test exclusively in one browser, use a variety. Also keep in mind that even the same browser will render differently on alternate platforms. Take a look at your page in Windows, Mac OS, and Linux to get a better feel for how others view your site. If you don't have access to some of these systems, ask for a site check in /forum/webmonk and many users will be happy to provide screenshots.

• 
 

]]>The  shortcut icon sets the type of link, and the file name really must be favicon.ico for best compatibility.

Technical information on how favicon works can be found at http://www.jamesshuggins.com/h/web1/favicon.htm.  Another excellent resource is http://www.favicon.com/.

.box {
  padding: 5px;
  margin: 0;
  width: 100px;                /* for ie5 */
  voice-family: "\"}\"";
  voice-family: inherit;
  width: 90px;                /* for compliant browsers */
  }
  html>body .box { width: 90px }  /* for opera */
 

]]>We want a box that is 90px wide, with 5 px padding on each side.  First we set the width wider for 5.5, to include the 5px padding. The first voice-family confuses the IE 5.5 parser, rendering trash which it ignores until it sees the next } which resets his parser. For all other browsers, the voice family is reset back to its inheritied value, then the correct 90px width is set. The last line is called the "be nice to Opera" rule. It resets the width back to 90px for Opera 5 which is confused by the voice-family hack (like IE 5.5) but "gets" the box model (like all the other browsers do). Newer browsers (and hopefully all future browsers) will support the html> selector and they will also use the correct (90px) width.

IE 5.5 also has its own idea of what the font-size keywords scale your font to. What in IE 5.5 is "small" is the size of "medium" everywhere else. So, if you use font sizes by keywords (as many people do), you will also find yourself using the voice-family hack to set the font size for 5.5. This page has an excellent explanation: »diveintoaccessibility.or ··· zes.html

What a mess. But from here on it gets easier.

Safari and Konqueror

With the Mac, Safari usually takes a small bit of stylesheet changes, mostly having to do with Safari (and Konqueror) collapsing blocks when they shouldn't. Addition of a few display: blocks and setting widths on blocks floated next to each other seems to help.

IE 5.2

IE 5.2/Mac is the last release for the Mac of IE, and it's idea of the box model is somewhere between 5.5 (wrong) and 6.0 (mostly right). It just blows the width of certain text lines, and has other bugs which can cause other rendering issues for 5.2. 

Fortunately we have a CSS hack for that, which makes the style a bit uglier (avert your eyes for the voice-family plus 5.2 hack)
.box {
  padding: 5px;
  margin: 0;
  width: 110px;                / * for ie5.2 Mac */
  /* \*/
  overflow: hidden;
  width: 100px; 
  voice-family: "\"}\"";
  voice-family: inherit;
  width: 90px ;  
  /* */
  }
  html>body .box { width: 90px }  /* 5.2 mac doesn't see  */
 

]]>First we set the width to a value that makes things look right under IE 5.2. The odd looking comment screws up 5.2: because it doesn't end the comment on that line 5.2 ignores all the rules until it sees the next */. All other browsers end the comment on that same line (comment ending characters are never quoted with backslash). Between the comments, you can set things that will not apply to 5.2, like overflow: hidden (which causes entire links to disappear in 5.2).

NN4

So the last thing you want to try to get going is NN4. They are lucky to see anything other than unstyled text. You can give them colors, but some rudiumentry elements like background images are beyond NN4's capability. 

So let's say you used tables for layout, but your page looks odd because the page has margins on NN4. There's another flavor of the comment hack just for NN4. 

To make a borderless page on anything but NN4 you just set margin: 0; this doesn't work in NN4. What does work is setting the margins to exactly -10 pixels. To make this come out the easy way just use the "NN4 comment confusion hack", which looks like this.
body
{
  margin: -10px 0px 0px -10px;
/*/*/
  margin: 0;
/* */
}
 

]]>
How it works is that that NN4 gets confused by the first comment line. It doesn't think the first comment line ends. NN4 treats everything from the first comment until the next */ as a comment. All other browsers see this as code between two comments. So the margin is set up for NN4, then reset to 0 for all other browsers.

If you don't want to mess around trying to get NN4 to work, just enclose most of your styles between the goofy-looking NN4 comments. If your markup is clean, NN4 users will get a site that still works, but looks unstyled. Don't worry, in most cases they will never notice. After all, they are probably using an antique computer.

Here are some resources for learning JavaScript.

1. Webmonkey JavaScript online
2. JavaScript Guide from Netscape
3. JavaScriptkit.com

There are a number of free editors that people use. In the end, it boils down to personal preference as to which is "best".

Please check the licensing for each piece of software. While some of what is listed is wide-open, some is free for personal use only.

• Notepad: basic text editing
• Notepad ++: A souped-up version of Notepad, with code coloring, collapsing, and more.
• NVU: a free WYSIWYG editor, in the genre of Dreamweaver. Cross platform (Win, Lin, Mac), fairly robust, standards-aware.
• HTML-KIT:"HTML-Kit is a full-featured editor designed to help HTML, XHTML and XML authors to edit, format, lookup help, validate, preview and publish web pages.">
• XStandard: "XStandard is the leading standards-compliant plug-in WYSIWYG editor for Windows desktop applications and browser-based content management systems (IE/Mozilla/Firefox/Netscape)"

Additional information about HTML Tools is available on W3C's HTML Tools page. Also see this post listing additional free HTML editors.