+
+
+
+
diff --git a/htm/footer.html b/htm/footer.html
new file mode 100644
index 0000000..d996a2b
--- /dev/null
+++ b/htm/footer.html
@@ -0,0 +1,2 @@
+
+
diff --git a/img/favicon.ico b/img/favicon.ico
new file mode 100644
index 0000000..2246f15
Binary files /dev/null and b/img/favicon.ico differ
diff --git a/img/greenbar.jpg b/img/greenbar.jpg
new file mode 100644
index 0000000..cfa99c6
Binary files /dev/null and b/img/greenbar.jpg differ
diff --git a/img/greenbar2.jpg b/img/greenbar2.jpg
new file mode 100644
index 0000000..9817bc4
Binary files /dev/null and b/img/greenbar2.jpg differ
diff --git a/img/mainframe-terminal.png b/img/mainframe-terminal.png
new file mode 100644
index 0000000..87741ce
Binary files /dev/null and b/img/mainframe-terminal.png differ
diff --git a/img/socrates-128x128.png b/img/socrates-128x128.png
new file mode 100644
index 0000000..31044bf
Binary files /dev/null and b/img/socrates-128x128.png differ
diff --git a/index.md b/index.md
new file mode 100644
index 0000000..8954f4a
--- /dev/null
+++ b/index.md
@@ -0,0 +1,64 @@
+## The Apache2 Markdown Module Test
+
+What you are looking at on this page, is the product of a markdown file, rendered into html
+automatically, by the apache2 markdown plugin. The plugin offers an optional header and
+footer feature. If this is enabled, then css can be referenced in the header, and all
+your markdown elements will be styled as if they were html elements.
+
+Here is an unordered list:
+
+- this should
+- look like a
+- bullet list
+
+Here is an ordered list:
+
+1. Take out the trash
+2. Make your bed
+3. Eat breakfast
+4. Finish your paper.
+
+Here is a blockquote:
+
+> This is the blockquote. I'll use it for output displays. I gave it a greenbar
+> background, to simulate an actual computer printout. Next up, customizing the
+> code block to look more like an actual terminal display (amber preferably).
+
+This is a standard table:
+
+|This | should | be |
+|:-------|:--------:|-------:|
+|col1 |col2 |col3 |
+|rows2 |rows2 |row22 |
+
+This sentence `should have` several chunks that are `displayed as` inline code blocks.
+
+Here's a [link to a plain text file](txt/test.txt) you can click on!
+
+And here's an embedded image: 
+
+
+And here's a fenced code block:
+
+```bash
+#!/usr/bin/env bash
+echo "Hello, World!"
+exit 0
+```
+
+This time with spaces instead:
+
+ $ echo "Hello, World!"
+ Hello, World!
+ $
+ $ uname -a
+ Linux socrates 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) x86_64 GNU/Linux
+ $
+
+
+How did that work out?
+
+Let's have a look at [another markdown file](md/sample.md), shall we?
+
+---
+Below the line
diff --git a/md/Atari/index.md b/md/Atari/index.md
new file mode 100644
index 0000000..9053c70
--- /dev/null
+++ b/md/Atari/index.md
@@ -0,0 +1 @@
+# The Atari Page
diff --git a/md/DOS/index.md b/md/DOS/index.md
new file mode 100644
index 0000000..a1f88c8
--- /dev/null
+++ b/md/DOS/index.md
@@ -0,0 +1,3 @@
+# The DOS Page
+
+## For MS/PC/DR DOS on the x86 line.
diff --git a/md/JUNK/index.md b/md/JUNK/index.md
new file mode 100644
index 0000000..8e67f8b
--- /dev/null
+++ b/md/JUNK/index.md
@@ -0,0 +1,3 @@
+# The Parts Bin
+
+## Covering anything miscellaneous or uncategorizable.
diff --git a/md/Linux/index.md b/md/Linux/index.md
new file mode 100644
index 0000000..3e44e60
--- /dev/null
+++ b/md/Linux/index.md
@@ -0,0 +1,3 @@
+# The Linux Page
+
+### Covering the whole ecosystem of Linux, BSD, Open Source Unix, and other alternative operating systems.
diff --git a/md/MVS/index.md b/md/MVS/index.md
new file mode 100644
index 0000000..58bc7df
--- /dev/null
+++ b/md/MVS/index.md
@@ -0,0 +1 @@
+# The IBM MVS 3.8j Page
diff --git a/md/sample.md b/md/sample.md
new file mode 100644
index 0000000..0215e75
--- /dev/null
+++ b/md/sample.md
@@ -0,0 +1,54 @@
+## Markdown file 2
+
+This file was linked to from our first file. I want to see if it will still be wrapped in the plugin header and footer. If it is, then we're golden!
+
+Also, I want to see how the paragraphing works with this markdown parser. Will it give me a nice clean break between paragraphs, and legible line wraps, or will it be crushed and stretch and ugly like some of these parsers tend to work. I'm just rambling on here, in order to make this paragraph as long as I can manage. If this works well, I won't even need HUGO by the time I'm done!
+
+So, this is where another lengthy paragraph would start. I'm not going to carry on too long. I just want to see about the gap between the two paragraphs. I also want to see what it looks like to have sub-headingsin a document. So, let's start a sub-heading.
+
+## Sub-Heading
+
+I've started a new sub-heading here. Let's see what this looks like. Another thing I'm curious
+about, is how the plugin will respond to actual html tags in the markdown. For example, an
+IFrame with a video embed:
+
+
+
+
+## Next Test
+
+Ok, so embedding an IFrame works out of the box. But, what about more complicated things, like divs or snippets of javascript? Lets see how that works out. First, here's a div with a span inside of it.
+
+
This is some text inside of the custom span
+
+Well, that's just grand! It seems that I can drop *any* html I want into *any* markdown I want, and it will render just fine! Ok, but what about, say, syntax hilighting, which requires a javascript?. Let's find out. For this, all I *should* need to do, is provide a markdown codefence, specifying the language, because the apache plugin will render it as `
` which is what both highlight.js and prism.js use. In this case, we'll make a python snippet. The key issue here, is that I already have css theming for the code fence. So, will the javascript override it, merge with it, or be ignored? We shall see:
+
+
+```language-python
+print('Hello, World!', end=' | ')
+print(100, end=' | ')
+print(5 + 5)
+vowels = ['a', 'e', 'i', 'o', 'u']
+popped_item = vowels.pop()
+print(popped_item)
+print(vowels)
+```
+
+And there we have it! Highlight.js works, but it overrides my global css, essentially overlaying the pseudo-amber-screen I created, with it's own theme. That's fine, for now. I picked one as close as possible to my theming, but more work will be needed in the future.
+
+If don't want to use the highlighting, I can always just use a generic (unlabelled) fence:
+
+```language-nohighlight
+10 PRINT "HELLO"
+20 GOTO 10
+```
+
+## Final Test
+
+Now, can we add an Iframe with a display of plain text in a different file? If I can do that, then I could even show you this particular markdown file in its raw form. So, you can see there's no special trickery here, beyond the magic of the markdown plugin for Apache2.
+
+The index.md file:
+
+
+The sample.md file (the one you're reading now):
+
diff --git a/robots.txt b/robots.txt
new file mode 100644
index 0000000..62b364d
--- /dev/null
+++ b/robots.txt
@@ -0,0 +1,4 @@
+User-agent: *
+Disallow: /
+
+
diff --git a/txt/index.txt b/txt/index.txt
new file mode 100644
index 0000000..8954f4a
--- /dev/null
+++ b/txt/index.txt
@@ -0,0 +1,64 @@
+## The Apache2 Markdown Module Test
+
+What you are looking at on this page, is the product of a markdown file, rendered into html
+automatically, by the apache2 markdown plugin. The plugin offers an optional header and
+footer feature. If this is enabled, then css can be referenced in the header, and all
+your markdown elements will be styled as if they were html elements.
+
+Here is an unordered list:
+
+- this should
+- look like a
+- bullet list
+
+Here is an ordered list:
+
+1. Take out the trash
+2. Make your bed
+3. Eat breakfast
+4. Finish your paper.
+
+Here is a blockquote:
+
+> This is the blockquote. I'll use it for output displays. I gave it a greenbar
+> background, to simulate an actual computer printout. Next up, customizing the
+> code block to look more like an actual terminal display (amber preferably).
+
+This is a standard table:
+
+|This | should | be |
+|:-------|:--------:|-------:|
+|col1 |col2 |col3 |
+|rows2 |rows2 |row22 |
+
+This sentence `should have` several chunks that are `displayed as` inline code blocks.
+
+Here's a [link to a plain text file](txt/test.txt) you can click on!
+
+And here's an embedded image: 
+
+
+And here's a fenced code block:
+
+```bash
+#!/usr/bin/env bash
+echo "Hello, World!"
+exit 0
+```
+
+This time with spaces instead:
+
+ $ echo "Hello, World!"
+ Hello, World!
+ $
+ $ uname -a
+ Linux socrates 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) x86_64 GNU/Linux
+ $
+
+
+How did that work out?
+
+Let's have a look at [another markdown file](md/sample.md), shall we?
+
+---
+Below the line
diff --git a/txt/sample.txt b/txt/sample.txt
new file mode 100644
index 0000000..5820f9a
--- /dev/null
+++ b/txt/sample.txt
@@ -0,0 +1,54 @@
+## Markdown file 2
+
+This file was linked to from our first file. I want to see if it will still be wrapped in the plugin header and footer. If it is, then we're golden!
+
+Also, I want to see how the paragraphing works with this markdown parser. Will it give me a nice clean break between paragraphs, and legible line wraps, or will it be crushed and stretch and ugly like some of these parsers tend to work. I'm just rambling on here, in order to make this paragraph as long as I can manage. If this works well, I won't even need HUGO by the time I'm done!
+
+So, this is where another lengthy paragraph would start. I'm not going to carry on too long. I just want to see about the gap between the two paragraphs. I also want to see what it looks like to have sub-headingsin a document. So, let's start a sub-heading.
+
+## Sub-Heading
+
+I've started a new sub-heading here. Let's see what this looks like. Another thing I'm curious
+about, is how the plugin will respond to actual html tags in the markdown. For example, an
+IFrame with a video embed:
+
+
+
+
+## Next Test
+
+Ok, so embedding an IFrame works out of the box. But, what about more complicated things, like divs or snippets of javascript? Lets see how that works out. First, here's a div with a span inside of it.
+
+
This is some text inside of the custom span
+
+Well, that's just grand! It seems that I can drop *any* html I want into *any* markdown I want, and it will render just fine! Ok, but what about, say, syntax hilighting, which requires a javascript?. Let's find out. For this, all I *should* need to do, is provide a markdown codefence, specifying the language, because the apache plugin will render it as `
` which is what both highlight.js and prism.js use. In this case, we'll make a python snippet. The key issue here, is that I already have css theming for the code fence. So, will the javascript override it, merge with it, or be ignored? We shall see:
+
+
+```language-python
+print('Hello, World!', end=' | ')
+print(100, end=' | ')
+print(5 + 5)
+vowels = ['a', 'e', 'i', 'o', 'u']
+popped_item = vowels.pop()
+print(popped_item)
+print(vowels)
+```
+
+And there we have it! Highlight.js works, but it overrides my global css, essentially overlaying the pseudo-amber-screen I created, with it's own theme. That's fine, for now. I picked one as close as possible to my theming, but more work will be needed in the future.
+
+If don't want to use the highlighting, I can always just use a generic (unlabelled) fence:
+
+```language-nohighlight
+10 PRINT "HELLO"
+20 GOTO 10
+```
+
+## Final Test
+
+Now, can we add an Iframe with a display of plain text in a different file? If I can do that, then I could even show you this particular markdown file in its raw form. So, you can see there's no special trickery here, beyond the magic of the markdown plugin for Apache2.
+
+The index.md file:
+
+
+The sample.md file (the one you're reading now):
+
diff --git a/txt/test.txt b/txt/test.txt
new file mode 100644
index 0000000..7949f18
--- /dev/null
+++ b/txt/test.txt
@@ -0,0 +1,8 @@
+Hello!
+------
+
+This is a simple text document. I may begin to do much more with plain text,
+as a reaction to the excessive complexity of modern day document presentation.
+
+But will this work? We shall see...
+