Blog excerpts

_layouts/blog.html

@@ -14,6 +14,7 @@ layout: default
         <h2>
           <a class="post-link" href="{{ post.url | prepend: site.baseurl }}">{{ post.title }}</a>
         </h2>
+        {{ post.excerpt | replace:'</p>','...</p>'}}
       </li>
     {% endfor %}
   </ul>

_posts/2015-06-01-debugging-the-ibm-vga-rom.md

@@ -8,10 +8,11 @@ permalink: /blog/2015/06/01/
 
 The IBM VGA ("Video Graphics Array") standard was introduced as part of the IBM PS/2 line of computers;
 it was not a feature you could purchase or install in older PC, XT or AT-compatible machines.  In fact, full VGA
-support was not even available in all PS/2 models.  Of the first four PS/2 models -- the 8086-based Model 30, the
-80286-based Model 50 and Model 60, and the 80386-based Model 80 -- VGA support was available only in the three
-higher-end models.  The Model 30 came with MCGA ("Multicolor Graphics Array") video hardware that supported a subset
-of VGA modes (eg, 640x480 2-color and 320x200 256-color graphics).
+support was not even available in all PS/2 models.
+
+Of the first four PS/2 models -- the 8086-based Model 30, the 80286-based Model 50 and Model 60, and the 80386-based
+Model 80 -- VGA support was available only in the three higher-end models.  The Model 30 came with MCGA ("Multicolor
+Graphics Array") video hardware that supported a subset of VGA modes (eg, 640x480 2-color and 320x200 256-color graphics).
 
 It wasn't until October 1987 that IBM finally introduced an 8-bit ISA card that brought VGA capability to older PCs.
 The card was called the **IBM PS/2 Display Adapter**.  However, I think the name is a bit confusing, since the card

_posts/2015-07-17-windows-95.md

@@ -7,8 +7,9 @@ permalink: /blog/2015/07/17/
 ---
 
 This week (July 14, 2015) was the 20th anniversary of Windows 95 RTM ("Release To Manufacturing").  So I decided to
-throw a PCjs party and try running Windows 95 Setup inside a PCjs machine for the first time.  Sadly, it immediately
-failed:
+throw a PCjs party and try running Windows 95 Setup inside a PCjs machine for the first time.
+
+Sadly, it immediately failed:
 
 	Please wait while Setup initializes.
 	Windows requires a computer with an 80386 processor or higher.

_posts/2015-10-27-windows-95-and-early-80386-cpus.md

@@ -6,7 +6,7 @@ categories: windows-95 80386
 permalink: /blog/2015/10/27/
 ---
 
-Every time Windows 95 starts up, its real-mode loader performs the following CPU identification test:
+Every time Windows 95 starts up, its real-mode loader performs the following CPU identification test.
 
 	&0654:121E 9C              PUSHF   
 	&0654:121F 33C0            XOR      AX,AX           ; try to clear bit 15 of flags

_posts/2015-12-10-rebuilding-the-pcjs-website.md

@@ -6,7 +6,7 @@ categories: blog
 ---
 
 It's been nice using Node.js to power the PCjs website, using Amazon's Elastic Beanstalk service, but that combination
-has also been a source of some frustrations:
+has also been a source of some frustrations.
 
 * When someone posts an article or a tweet linking to a PCjs page, the website bogs down, and while Amazon's Elastic
 Beanstalk service makes it easy to automatically scale up, each new instance automatically multiplies my expenses as well,
@@ -71,6 +71,16 @@ configuration file if not using the default `machine.xml`, `template` to specify
 using the default `components.xsl` file, and `state` to specify a JSON-encoded machine state file if the machine
 requires a predefined state.
 
+For example, the PCjs home page contains two machines, and so this appears at the top of the root [README.md](https://raw.githubusercontent.com/jeffpar/pcjs/gh-pages/README.md):
+
+	machines:
+	  - type: pc
+	    id: ibm5150
+	    config: /devices/pc/machine/5150/mda/64kb/machine.xml
+	  - type: c1p
+	    id: demoC1P
+	    config: /devices/c1p/machine/8kb/large/machine.xml
+
 I will continue to include a Node web server with the PCjs project, but it remains to be seen whether I'll update the
 Node components to parse the new Jekyll "Front Matter" that's been added to all the Markdown files, or whether I'll leave
 leave the Node support as-is on the old "master" branch, and make the "gh-pages" the new default branch.