How to Make Kehilalinks Pages

Starting to Use Composer

Introduction

This is one of the longer lessons because I want to cover a lot of the basics right up front. Don't let the length of this lesson frighten you -- if you are already familiar with things like changing fonts in a word processing document, you will find most of the stuff in this lesson to be pretty simple.

Install the Software

If you have not already done so, install the SeaMonkey software that includes Composer. You can download SeaMonkey from the SeaMonkey project web site: http://www.seamonkey-project.org/releases/

Notation

Composer, like most programs, uses pull down menus.  You click on a menu name (e.g., "Edit"), and are then presented with a list of menu options (e.g., "Cut, Copy, Paste...").  Sometimes, menu options will themselves be menu names, and you will be presented with more options.  To indicate what menu and options to select, I will use "arrow" notation, e.g., 
    Edit -> Paste

Composer Basics

Starting Composer

Start by running SeaMonkey (e.g., by double-clicking the SeaMonkey icon on your desktop, if it's there). This opens a single SeaMonkey browser window. PC users should see these words near the top of the window (Mac users will see this line at the top of their screen, as with all programs on Macs), in this order from left to right:
          File, Edit, View, ...
These are the pull-down menus.

From this point there are several ways to start Composer.  One way is to select in the SeaMonkey browser
    File -> New -> Composer Page
(I.e., click on "File", then in the pull-down menu click on "New", then in the menu that opens click on "Composer Page".)

Try it. This opens a new window whose title is something like  "untitled - Composer"  The body of the Composer window will be empty.  This is a brand new, but blank, web page -- an empty canvas just waiting for us to fill it.

Toolbars

You will notice near the top of your Composer window three lines of commands, menus, and symbols. (Again, Mac users will see the top line on the top of their screen, not in the Composer window.)

Composer
                commands, menus, and symbols

If you don't see all 3 rows then you may have one or more hidden. To show them all, in the top row select
  View -> Show/Hide -> Format Toolbar
which will show (or hide, if you already have it showing) the bottom row, and select
  View -> Show/Hide -> Composition Toolbar
to show or hide the middle row.

If you don't see all the tools from left to right, your Composer window is probably too narrow.  Make the window as wide as you can to show all the tools.

Most of the commands in the middle line, the Composition Toolbar, are self-explanatory: "New", "Open", and "Save" are for creating new pages, opening existing pages, or saving the page you are working on (you can do the same things in the "File" menu on the top line). "Print" is for printing the page you are working on. "Spell" invokes the built-in spell checker. "Publish" is for uploading your page, which we will do a few lessons from now. "Link", "Image", and "Table" are things we will also cover in upcoming lessons.

One more command is "Browse" (might also be called "Preview" in some versions of Composer). You use this command to display your page in the SeaMonkey browser.

Note: If you don't see the highlighter tool button highlight
        tool button on the bottom row, you need to set one of the Composer options. In a Composer window, click Edit -> Preferences -> Composer, then in the Editing section check "Use CSS styles instead of HTML elements and attributes". That will enable the text highlight button on the editing toolbar and several other features .

Entering Text

You will see a blinking, vertical bar in the upper left part of the Composer window.  This is the cursor.  Note that this is different from the arrow or other icon that indicates where your mouse is pointing. 

Editing text in Composer is almost the same as editing text in a word processing program like Microsoft Word or WordPerfect. When you type or insert some object  into the web page, the text or object will go wherever the cursor is.  To see how this works, type the words "I am looking forward to making web pages for Kehilalinks."  After you type this you should see the blinking cursor after the final period.  Now move your mouse and click just before the words "web pages."  You should now see the blinking cursor just in front of the "w."  Type the word "terrific," followed by a space.  The blinking cursor should still be in front of the "w," but the whole line that you typed in should now read "I am looking forward to making terrific web pages for Kehilalinks."

Save your Web Page

Now that we have made a (very, very simple) web page, we want to save it.  To do this, in Composer select "File -> Save". Before saving the file, Composer first asks us to give the page a title. The web page title is what is shown in the title line of a browser window (usually at the top of the window) when you open the page, and it is also used by web search engines. Call your page "I just made a web page!", or something else that reflects how triumphant you feel at this point. Then click "OK".

Don't worry if you can't think of a good page title; you can always change it later (we'll talk about how to do that in an upcoming lesson).

Choose a Good Filename

Composer then asks us where to save the file and to choose a file name. Choose a name for the file, such as "example1.html". I'll be referring to this file by the name "example1.html" from now on so it might be easiest if you use the same name for your file.  Whichever name you choose, use only letters or numbers in the file name; DO NOT use any spaces or special (e.g., punctuation, except for the period) characters in the file name. I must repeat: DO NOT use any spaces or special characters in the file name.  Although the newer versions of Windows and Macs and the web browsers that run on them can use file names that contain special characters and spaces, not every operating system can.  For example, while "example1" is a good file name for a web page, "example #1" is not, because it contains a space and a special character (the "#").  You should also try to keep the file name fairly short (because it makes the name easier to type).  I also usually prefer to make the name all lower-case to make it easier to manage my web site (for reasons we will discuss in a later lesson about links), but that is not a requirement.

Be sure the file name has the ".html" (or ".htm"; they are equivalent) file name extension. Web pages are actually text files written in a language called "HTML". Web browsers sometimes depend on seeing this extension to know how to display the page.  If you save the file without a ".html" (or ".htm") extension, web browsers won't necessarily display the file as you intend it to look. They may treat the HTML commands as regular text so you would see all the HTML commands in your web browser and not the web page you were expecting.

The method of saving a file should be exactly the same as the method you use for saving files in Microsoft Word, WordPerfect, or other word processing program, so I won't need to say more about that. Just be sure to save the example1.html file in a folder or on the desktop where you can easily find it again. I suggest keeping all of your work in this class in a folder that you only use for the class, so you can easily find your work again.

Special Note for Windows UsersHidden file extension

Windows is configured by default to "hide extensions for known file types". This means that, when you look in a folder at a file name, the entire file name may not be shown. For example, even though you may have given your example1.html file the name "example1.html", it will only show in a folder as "example1". If you right click on the file and select "Properties", then click on the "Details" tab, you will see the full file name. A common mistake is to add an extra ".html" to the file name, because you can't see the original one, making the real file name "example1.html.html"!  Later on in the class, when we create links to different pages, it will be important to know the real name of the files, so it is good to become familiar now with how file naming works on your computer. Be sure to get rid of the extra ".html" if it's there.

I recommend un-hiding extensions for known file types. You'll find that that will make things a lot less confusing for you. To do this, in the Control Panel:

  1. Double-click the "Folder Options" icon (called "File Explorer Options" in Windows 10)uncheck "hide file
          extensions..."
  2. Click on the "View" tab
  3. UN-check "Hide file extensions for known file types"
  4. Click OK to finish.

In order to see the "Folder Options" icon in the Control Panel, depending on your version of Windows, you might first need to change your Control Panel view to "Small Icons" (Windows 7), or "Classic View" (Vista). In Windows 10, you can reach the Control Panel by typing "Control Panel" in the "Search Windows box. (You are on your own if you still use Windows 8.)

Preview or Browse your Page

Although Composer is a "WYSIWYG" (What-You-See-Is-What-You-Get) editor, there are situations where what you see in the Composer window is not exactly the way that the web page will look in a web browser.  A simple way to see what your web page will (probably) look like in the SeaMonkey browser is to click on the "Preview" tab at the bottom of the window.

Tabs at the bottom
        of the Composer window

We will use the "Normal" tab for most of our editing (because it shows some things that are invisible when using the "Preview" tab), but you can edit your text in Preview mode, too.

Preview mode gives a pretty good idea of how your page will look in the SeaMonkey browser, but it isn't perfect. To really know how your web page will look in the browser, you need to look at it in the browser. To see how the SeaMonkey web browser displays your web page, click on the "Browse" icon in the Composer toolbar near the top of the Composer window (between the "Publish" and "Print" icons).  This will open a new browser window that will display your web page.  If you have made a change to the web page, but have not saved the file before you browse the page, Composer will ask you if you want to save the file first. It is a good idea to frequently save your work to avoid losing it in case of a computer crash, software crash, or user crash.

Note that version 2.1 and up of SeaMonkey introduced a bug (at least on PCs; I don't know about Macs) so that the "Browse" button is disabled when you create a new page, even after you save the file. To enable the Browse button, click on any of the tabs at the bottom of the window (e.g., "Preview") first. That will enable the "Browse" button. Then in Composer you can click back on Normal to resume editing.

View your Page in Other Browsers

Believe it or not, although HTML is an international standard, different browsers may display the same page differently! For example, your page may look good when you view it in Firefox but not in Safari. It is a good idea to also look at your pages in web browsers other than SeaMonkey. Mac users by default have Safari, Windows users have Internet Explorer (or Edge), and there's also Google Chrome and Opera, which work on both Windows and Macs, among others. (SeaMonkey is, under the hood, essentially the same as Firefox, so I don't expect there to be any differences in the way that Firefox and SeaMonkey display pages. Please let me know if you find some differences.)

To view your page in another browser, you must first open a window of the other browser and then "Find" your page. Every browser, like SeaMonkey, has the ability to open specific files on your computer, as well as on the web. In SeaMonkey, for example, you click on "File -> Open File", then browse to the file (which means you have to know where the file is on your computer). In older versions of Internet Explorer, by contrast, it's "File -> Open" (if the menu toolbar that contains "File" isn't showing, click on "Tools -> Toolbars" and put a check by the "Menu Bar").

In Firefox, if the menu bar is showing, you use "File -> Open File". If you only have a Firefox button in the upper-left corner of the window instead of the File, Edit, etc., menus, right-click on an empty area of the tab strip near the top of the window and check "Menu Bar" in the pop-up menu.

In IE 11, it is very similar to Firefox. The only difference is that you use "File -> Open". As with Firefox, if the File menu is not showing, right-click on an empty area of the tab strip near the top of the window and check "Menu Bar" in the pop-up menu.

There may be slight variations in other browsers, but it will always be basically the same idea. (Except for Edge; I honestly have no idea how to open a file on my computer from within Edge itself.)

Be very careful that, when you open your pages in browsers other than SeaMonkey, don't accidentally save the file from the other browser. That could add extra HTML commands that would confuse Composer (and confuse you, because you wouldn't know why Composer suddenly doesn't do what you expect it to do). Only save your web pages from inside Composer and you will (usually) avoid this problem.

Closing Windows

You probably now have three windows open: the original SeaMonkey browser window, the Composer window, and the new browser window, and your screen may seem cluttered. Go ahead and close the original browser window by selecting in that window
  File -> Close (might also be "Close Window", if you have multiple tabs open)

Be careful to not select
  File -> Exit
which will completely exit SeaMonkey, closing all the windows, including Composer, at once!

Opening an Existing File

Now go ahead and select "File -> Exit", completely shutting down SeaMonkey, including Composer. Then restart SeaMonkey and in the SeaMonkey browser windows select "File -> Open File". Browse to the "example1.html" file that you created a little while ago and open it. With that file in the browser window, select "File -> Edit Page" to open the file in Composer.

Adding Text

At this point we know how to create a new HTML file and how to save it. Now it is time to learn more about adding and editing text in Composer.

Paste Without Formatting

To add text to your document, you can either type it directly into Composer, as you've been doing, or you can copy and paste text from other web pages and documents.

Under the Edit menu you might have noticed that there are two kinds of paste: "Paste" (<CTRL>+V), and "Paste Without Formatting" (<CTRL>+SHIFT+V). Very often, you will want to copy and paste text that you find in other web pages or documents. This text is formatted (e.g., using HTML or other commands), and if you use the regular "Paste" command then you will also copy all of the original formatting. That would be fine, except that you didn't use Composer to insert the formatting commands and Composer might get all mixed up when you want to change the formatting. It is much, much better to always use the "Paste Without Formatting" command when you copy and paste text into Composer.

Note that even "Paste Without Formatting" doesn't help if you copy and paste text from a Microsoft Word document. The copied text will still contain a lot of extraneous commands that will confuse Composer (and you, when you start editing). To copy and paste material from a Word document, first save the ".doc" (or ".docx") file as a text file, then open the text file in a text editor, like Windows "Notepad" program, then copy the text from the text file. Under no circumstances should you copy anything directly from a document opened using Word.

Text Wrapping

Right now, the example1.html web page has the single sentence "I am looking forward to making terrific web pages for Kehilalinks."  Move the cursor to the end of the sentence and backspace to erase the period.  Then continue typing this: "now that I know how to use the Composer.  I thought that it would be difficult but now I see how easy it can be, thanks to the Kehilalinks Web Class. " (I'm intentionally having you type a very long sentence, so we can see how Composer handles text wrapping.)

Unless you are using a very wide Composer window, the text should have wrapped onto a second line.  If the text still fits on one line, make the Composer window narrower so that the text wraps to a second line.  

[You can adjust the width of a window either by clicking on one corner or side and dragging the edge inward, or, if you have the window at full-screen size and cannot see the corners, by first reducing the size of the window (in Windows, by clicking on the middle icon at the top right hand corner of the window; MacOS has a similar feature) and then dragging a corner or side.]

Notice that Composer automatically wrapped the text to fit the width of the window (either as you were typing or when you resized the window).

See how the web page looks in the browser by clicking on "Browse".  The browser will automatically wrap the text to fit the width of its window, too.  HTML is a "markup language" that only describes the content of a web page, but not its precise layout.  This is one example why it does not specify the precise layout: different people have different size monitors and use different size windows, so browsers should be free to adjust the page layout to fit the size of the window.

You can close the browser window, if you'd like, by selecting in that window
  File -> Close (or "Close Window")

Line Breaks

Go back to the Composer window that contains "example1.html" and move the cursor to the end of the text.  Press the "enter" key (sometimes called "return") and type "That's enough subliminal advertising, let's learn more."  View the page in a browser window and make the browser window narrower, then make it extremely wide.  You should see that, although the text up to "...how easy it can be" automatically adjusts to fill the width of the window, the new text always begins on a new line.

What we did when we pressed the "enter" key was insert a "line break."  For things that are in the same paragraph, you generally want to avoid inserting line breaks so that the text will automatically adjust to different size windows. A frequent mistake made by people starting out with a WYSIWYG editors like Composer is to use line breaks and spaces or tabs to make the text line up the way they want it to, but they forget that that won't work if you change the size of the browser window! Don't do that! Frequently viewing your page in different size browser windows will help you find where you have made the mistake of pressing the "enter" key when you shouldn't have.

Remember, no matter how strong the temptation, don't use line breaks and spaces and tabs to make text line up. We'll learn a more reliable method of doing that later in the course. If you do it now then, when you get closer to finishing your page, you'll suddenly notice that things no longer line up when you change the window size and it will be hard to strip out all of the extra spaces and tabs and line breaks.

Paragraphs

Go back to the Composer window and move the cursor to after "...learn more."  Then press the "enter" key twice and type "Now we are learning about paragraphs."  You should have a blank line between the original text and the new text.

Basic HTML does not have a standard for indenting paragraphs; typically, paragraphs are denoted using extra space. We can denote paragraphs by inserting an extra line break, as we just did, or by using the "paragraph format" tool, which we'll learn about shortly.

The Format Menu

Clicking on "Format" on the top toolbar gives you the format menu. Some of the tools on the Format Menu can also be found on the Format Toolbar (third row of menus/commands/icons), but some can only be accessed in the Format Menu. In this lesson, I will discuss the format commands in the Format Menu that affect text.Format Menu

Changing the Font

To change the text font, select
  Format -> Font
and you will be presented with a list of font choices. You can either select some text and then change the font, or else select a font and then start typing.

Of particular note are the font choices at the top of the menu: "variable width", "fixed width", plus the fonts "Helvetica/Arial", "Times", and "Courier". "Variable width" tells a browser to use its default "variable width" font, which means that the browser will do some automatic typesetting and adjust the spaces between letters so that it looks like the text was typeset. This feature makes the text more attractive and easier to read.  "Fixed width", on the other hand, tells a browser to use its default fixed width font so that the letters are all the same distance apart. Note that these font commands do not tell the browser what actual fonts to use, only that one font is variable width and one is fixed. Different browsers may use different fonts.

The default font for Composer is "Times," which is a "serif" font.  The difference should be easy to see: the serif fonts have extra flourishes on the characters, while the sans serif fonts, like Helvetica and Arial are relatively plain.  The Times and the Helvetica/Arial fonts are both variable width fonts. The Courier font, on the other hand, is a standard fixed-width font that looks like something created on a typewriter.

Although Composer offers you a choice of possibly dozens of fonts or more -- whatever is installed on your computer -- I recommend that you don't use most of them.  The reason for this is that not every computer has the same set of fonts. Windows and Mac systems have different sets of fonts, for example, and different applications may install additional fonts.  If you select a font that someone else's computer doesn't have, what that person sees on their screen will be different from what you see. For example, on my computer I have a font called "Gyparody". It is a font intended to look like the font used on the TV "Jeopardy" game show title. It looks like this:

Example of the Gyparody font

This entire paragraph is written in the "Gyparody" font. If you don't have the Gyparody font on your computer then this paragraph will probably look like all the other text. Lots of beginning web page makers make this mistake, using fonts that only they have, but you will always be safe if you use the three standard fonts.

There are three basic fonts that are built into SeaMonkey and virtually all other browsers: Times (a variable width serif font), Arial (also called Helvetica, a variable width sans serif font), and Courier (a fixed width, serif font).  If you use these fonts then chances are very good that other people looking at your page will see on their computers what you see on yours.  If you use anything else, chances are that at least some people will see something different (probably the default font -- usually Times or Courier, depending on whether the font is variable or fixed width -- will be used). 

Whatever you do, absolutely DO NOT use a picture font like "Zapf Dingbats" or "Wingdings"!  While an unusual character font might not appear on someone else's computer as you intended, at least it will appear as characters.  The "picture" fonts, although they might draw cute pictures when displayed on your computer, will display as letters on other computers, which will really confuse things..

Practice changing fonts by changing the font of various words in your example1.html file.

Text Size

On the Format menu, there are many options for formatting text. "Format -> Size", for example, let's you adjust the font size. You can make the size larger or smaller by one "step", or select some pre-defined sizes. These sizes are not given in numbers, like "16 pixels", which would be the same on anybody's computer, but in relative sizes. The sizes are relative to the default font sizes in a browser. Every browser has a default setting for font sizes so that, if a web page does not specify the size, the browser will use the default size. The default size can be configured by a user to, for example, make web pages easier to read by increasing the font size. This is another example of why you cannot assume that everyone who looks at your web pages will see them the same way that you do -- they might be using different font sizes in their browser than you are.

The "smaller" and "larger" size options that you see when you slick on "Format -> Size" make the font size one smaller ("-1") or larger ("+1") than the default size. The pre-defined sizes "x-small", "small", "medium", "large", "x-large", and "xx-large" correspond to -2, -1, default, +1, +2, and +3. The exact amount that the size is changed, however, may be different on different browsers. (Remember, if you use a very small font, it may be too small for some people to read on their computers!) Here is an example of the difference between the sizes:

Try changing the size of fonts in your example1.html page.

To change the default font size in SeaMonkey's browser (and in Composer), select Edit -> Preferences -> Appearance -> Fonts (to see "Fonts", click on the small arrow or triangle that is just to the left of "Appearance"). That will let you set the size in pixels of the default size for variable ("proportional") and fixed ("monospace") width fonts. Try changing the default font size in SeaMonkey to see how the sizes of fonts in this lesson page change.

Text Style and Color.

"Format -> Text Style" lets you select the common styles of boldface, italic, and so forth -- but also lets you select things like "strikethrough", "superscript", and "subscript". These should look just about the same in all browsers, although sometimes strikethrough looks different.

Also in the "Text Style" menu are additional, HTML styles like "emphasis", "stronger emphasis", and so on. Experiment with each of these styles to see how they look in SeaMonkey and in your computer's default browser, because they may look different in different browsers.

"Format -> Text Color" lets you choose the color of the text. You will be presented with a choice of colors. Select a color by clicking in one of the color boxes and then click OK. You can even make every letter in a word a different color. Text
      Color Window

Each time you pick a color by clicking in a color box, notice how the string of letters and numbers that start with "#" in the box near the bottom left of the Text Color window changes. (In the figure here, the box contains "#330000".) This is the HTML color string. If you want to be exact about colors, you specify them using an HTML color string.

For example, here are the HTML color strings that Jewishgen uses on its web pages. All of the text,buttons, backgrounds, and logos on the site use these standard colors, which helps make the site look neat and professional. When you create your site, try to use a consistent color palette. It doesn't have to be the same as Jewishgen's colors, but pick a small set of colors that go well together and use them consistently.

Jewishgen Web Site Standard Colors
HTML Color String
Color
Where used
#BEC49F Light green menu bar background, tables bgcolor & footer
#949C51 Dark green menu bar buttons, table header, text hover
#646C24 Darkest green menu bar buttons down
#E8E1D1 Grey footer background, table cell alternate
#134B7D Blue text
#C9D2D7 Light blue body background - sides
#505527 Very dark green H2, H3...
#063358 Very dark blue text
#092E27 Blue-green overlay logo overlap

Experiment with changing the style and color of the text in your example1.html file.

Discontinuing and Removing Text Styles

If you have finished with using a font, style, size, or color different than the defaults and want to go back to the defaults as you continue typing, you can "turn off" the things that are different by selecting "Format -> Discontinue Text Styles". Everything you type after that will be the default size, color, font, etc.

If you have some text that you already typed and from which you want to remove non-default styles, colors, etc., use your mouse to select the text and then click on "Format -> Remove All Text Styles". (That option only appears in the menu if you select text that has some styles on it.)

Paragraph Formats

"Format -> Paragraph" gives you a choice of paragraph styles, "Body Text," "Paragraph", "Heading 1," "Heading 2," etc. Here's a quick explanation for the paragraph formats straight from the SeaMonkey Help, after which I'll describe them in more detail.

To apply a format to a paragraph, begin from the Composer window:

   1.   Click to place the insertion point where you want the format to begin, or select the text you want to format.
   2.   Choose a paragraph format using the drop-down list in the Format toolbar:

Pay careful attention as you enter text as to what kind of paragraph format you are using.

Body Text Format

This is the default format. Unless you explicitly change the font, size, color, etc., the default text settings will always be applied to body text.

Paragraph Format

Paragraph format makes everything in the paragraph a separate "block" of text. It also automatically adds space before and after the paragraph, to set it apart from the rest of the text. Although it is difficult at this point in the lesson for you to see the difference between using the paragraph format and simply using two line breaks to separate text, there is an important difference. We we haven't used any tools yet that are based on "blocks", but this difference will become clearer in a later lesson, when we look at background colors for blocks.

To practice applying the paragraph format to some text, first type 3 lines separated by line breaks:

1
2
3

Now put the cursor just before the "2" and then select  "Format -> Paragraph -> Paragraph". The three lines should now look like this:

1

2

3

Notice the space before and after the 2? Using Paragraph style changed all of the line breaks to HTML "paragraphs", which have special attributes that we'll talk about later in the course.

Heading Styles

In most documents, text is divided up into separate sections.  Breaking up a document in this way helps to group related information and makes a document easier to read.  Each section has its own title, called a section heading.  For example, the heading for this section is "Heading Styles."

The text in headings is treated as special by browsers, to make headings distinct from normal text.  Typically, headings are automatically boldfaced and otherwise displayed differently than the normal text (although the precise way that a browser should display headings is not defined by the HTML standard and may differ between browsers).  The boldface and other changes are automatic, but you can also use different fonts, colors, alignments, and styles in headings. 

In general, the higher the heading style number, the smaller the size, so that Heading style1 is the largest and Heading style 6 is the smallest. For example, the heading for this section, "Heading Styles", uses Heading 3 style. The heading "Introduction" at the beginning of this lesson uses Heading 1 style.

Don't make the mistake of using a Heading style when all you really want is to increase the size of some text. That's what the font size tool is for. Headings have special uses and you should only use Heading styles for real headings.

Address Style

The address style is an HTML directive to the browser to display the text in some way that is different than the regular text, but the precise way is not specified.

In SeaMonkey, this means to italicize the text, but that may be different in other browsers.

At the dawn of HTML, someone must have thought that this was a good idea and that there would be a lot of addresses in web pages -- enough that it required its own paragraph style.

Preformat Style

The "preformat" paragraph style is intended to allow you to import text into HTML and preserve all the text's original line breaks, paragraphs, indenting, etc., without having to convert the text into HTML format.  SeaMonkey displays "preformat" paragraphs in the default fixed width font, but this may not be true for all browsers.

For example, if you type a really, really long line of text while in "preformat" mode, Browsers won't automatically break the text to fit the window until you insert a line break (e.g., by pressing "Enter"). You have to remember to break the line because the browser won't. Do you notice that in your browser? 
An alert user will notice the scroll bar on the bottom of the browser window. This is an indication that at least one line on the page is wider than the browser window currently is.

Indenting

Type some lines of text in your Composer page and make sure that they are all "body text", click in one of the lines to put the cursor there, and select "Format -> Increase Indent".
You should see the entire line indent to the right.
Try increasing the indenting multiple times.
Now choose "Format -> Decrease Indent" (multiple times, if necessary). The line should move back to the left.

The Formatting Toolbar

The formatting toolbar is the bottom-most of the three lines of tools.  Although many of the commands in this toolbar are also in the Format Menu, this toolbar is often more convenient and there are some unique commands found only in this toolbar. As with the Formatting menu, I'll focus for now only on the tools for formatting text.

Paragraph Alignment Tool

  When you type a paragraph of text into Composer, you'll notice that the text automatically is aligned with the left side of the window.  This means that the text is adjusted so that it is flush with the left side of the window, and the right side of the text is "ragged" (i.e., uneven).  Composer also allows you to also align the text to the Alignment toolsright side of the window (leaving the left side ragged), and to center text. The symbols should be familiar to you from using word processors.  Probably the symbol for left alignment has already been selected.  This is the default setting.  You can also click on the other symbols to choose
center or
right alignments.

There's also a button for complete page justification (spaces in the text will expand to make the text in the paragraph fill the entire page evenly, so you don't have ragged lines in the paragraph on either side.

Practice using this tool.  Be sure to "browse" the page each time to see how the web page looks in the browser.  Adjust the size of the browser window and notice how the browser adjusts the text, depending on the alignment.

Indenting Tool

indent tool The two symbols to the left of the paragraph alignment tool icons will, from left to right, decrease the indent of some text (arrow points left) or increase the indent (arrow points right).  They work the same as "Format -> Increase Indent" and "Format -> Decrease Indent" in the Format Menu.

Boldface, Italics, and Underline Styles Tool

 On the text formatting command line you will notice these 3 symbols: one looks like a bold, capital "B," Boldface, italics, and
      underlineanother looks like an italic "I," the third is an underlined "U".  These symbols are how we can make the text on our web page boldface, italic or underlined. The same commands can be found in the Format Menu when you select "Format -> Text Style".

The icon for each Boldface style selectedof these styles changes color when it is active. To undo these style changes you need to highlight the affected text and click the icon for the style that you want to undo. The icon for that style will change back to the normal color, indicating that it is inactive. Practice changing the same word to different combinations of boldface, italic, and underline.

Font Size Tool

Also on the format tool line Size toolare two icons that control the text size. These look like a small "A" and a larger "A", both with arrows on their right side. The arrow for the smaller "A" points down, indicating that this will make text smaller, while the up-pointing arrow on the larger "A" indicates that it makes text larger. These do the same thing as "Format -> Size -> Smaller" and "Format -> Size -> Larger".

Be careful when you change font sizes of text to change the size of any spaces in the sentence as well, or else your lines of text may be spaced unevenly even though the visible characters are all the same size.  Try this in your example1.html page by selecting just the space in between the words "subliminal advertising" and clicking on the larger "A" with the up arrow several times.  You should notice a large vertical gap between that line and the line above it because Composer must allow for the height of the space! But spaces are invisible, so if you notice a large gap between lines in your text that you can't explain, a tall space might be the culprit.

Paragraph Format Tool

Styles toolOn the far left of the Format Toolbar is the paragraph format tool. This does the same thing as "Format -> Paragraph".

Assignment

Now that you have learned these text formatting tools, let's get started creating our new Kehilalinks pages.

First, download to your computer a web page "template": kc-template.html . In SeaMonkey, you can download this page by right-clicking on the link and selecting "Save Link Target As...". Save the file in a folder that you have created for your class work. The assignment this lesson is to edit this template page, trying out different styles, fonts, and colors.

You'll notice some lines that form boxes around different parts of the text. These are called HTML "tables", and they are used for arranging things on a page. We'll study tables in a later lesson. For now, just focus on modifying the text.

Experiment with different text fonts, sizes, and colors. Also try different alignments and formats. As an example, here is what I did: kc1.html .

Edit the template page, then view it in SeaMonkey and at least one other browser. Resize the browser windows to see how the page looks in different size windows. When you save your file, use the file name "index.html" (or "index.htm") for your saved file, for reasons to be explained later in the course.

Note in the template and my example how I've included some things that are required by Kehilalinks policy. This includes the name of the Kehila and its alternate names, and the latitude and longitude. You can copy these from Jewishgen. (If you just "copy and paste" the latitude and longitude, the degree symbol "º" should also copy. If it doesn't, don't worry, we'll learn how to add that in the next lesson!) On the main JewishGen page (http://jewishgen.org/), where it says "search for a town", enter the name of your Kehila and it will give you a list of towns from the JewishGen Communities Database whose name matches. Choose the correct town and copy and paste the information from there. (Be careful to use "paste without formatting" when you paste lest the pasted text have the same font as in the original page. Then change the formatting to match what you want on your page after you insert the text.)

Other things that you should include in your page to conform to Kehilalinks policy are the block with your name, the last date that you updated the page, and the copyright notice.

And please don't forget the request for donations. JewishGen is a non-profit that depends on donations to operate. Even though it has a lean staff, it costs a lot of money to run a major web site that is accessed by thousands of people every day. JewishGen could really use all the help it can get!

Be sure to save the web page that you make, as we will use it again in the next lesson, and remember to use the file name "index.html" (or "index.htm") for your saved file.

 


Top of the page Back to the Course Outline

Copyright © 2009, 2010, 2012, 2013, 2014, 2016 Mark Heckman.  All rights reserved.
 

Visitor count