31 Dec 2025

hotseat-game for Units 5 and 6

24 Dec 2025 Update

test for PHP

general-purpose CSV viewer

game for CC2 Unit 5

10 Nov 2025 update:

This is a link to INDEX.HTML in the 10nov2025 directory.

This is a link to algebra_exercise.HTML in the 10nov2025 directory.

This is a link to algebra_double.HTML in the 10nov2025 directory.

This is a link to equation_builder.HTML in the 10nov2025 directory.

24 Oct 2025 update:

This is a link to INDEX.HTML in the 24oct2025 directory.

Here is the actual code:


This is a link to mp3demo.HTML in the 24oct2025 directory.

We need a Tic-Tac-Toe game: This is a link to TTT.HTML in the 24oct2025 directory.

Here is the actual code:


19 Sep 2025 update: SOUND FILES

19 Sep 2025 update: This is a link to INDEX.HTML in the 19sep2025 directory.

Many students want to start spending money on LLMs to make customized chat programs; because that costs money, we won't do it unless it is a core learning objective. We can make a new chat demo easily enough.

Before we worry about PHP and JavaScript, we should introduce old-fashioned HTML and perhaps a little bit of CSS.

We should start with some old-fashioned a-href HTML Links:

HTML links are defined with the A HREF and /A tags:

The following links use HTTPS to point at other sub-websites in this domain.

This is a link to the fancy "emotional wellness" page. It uses https://emotionalwellness.gadgeteering.org/ because it is going to a separate sub-website in this domain.

This is a link to the forum, which requires wordpress.

This is a link to the wordpress blog.

This is a link to the demonstration page that was written in April of 2025.

We can use P and /P tags to define paragraphs, but old-fashioned HTML is forgiving: we can throw paragraph breaks in almost anywhere and the page will render correctly.

Every website must be "hosted" on someone's machine. In the early days of the web, only universities or research laboratories were sophisticated enough to host websites. Most commercial websites are either hosted by partner companies or by the company that owns the website. The files for this particular section of the website exist in a particular directory of the host's server. In this case, we don't know where the server really is located: we do know that the server has a file directory called "public_html."

We should also note that old-fashioned HTML sites can be pretty forgiving with directory structure. For example, suppose we want to have a subdirectory for cute animal pictures: This is a SUSPICIOUS link to the "cute" subdirectory with no HTTPS. It just uses "public_html/cute" Does it work in your browser, or does the extra "public_html" mess it up?

This is a link to INDEX.HTML in the "cute" subdirectory that does use HTTPS but does not include the "public_html". It uses "https://plainhtml.gadgeteering.org/cute/index.html" Does it work in your browser?

This is a link to INDEX.HTML in the "cute" subdirectory that does not use HTTPS and also does not include the "public_html". It uses "/cute/index.html" Does it work in your browser?

This is a link to the "cute" subdirectory without the "public_html" string in its path and with no HTTPS. It uses "/cute" but does not specify a page name. We expect it will go to a default page. Does it work in your browser?

Let's try to make a meaningless link to demonstrate how 404 works:

This is a link to a page that does not exist in the "cute" subdirectory.

Old-fashioned HTML uses a HEAD tag. However, you probably won't see the title embedded in the HEAD tag unless you hover your mouse over the browser tab.

If we line up our image correctly with a directory name, we should see an actual image and not just an icon for a broken image link: