Add images to MiSTery Core page with passthrough copy

eleventy.config.js

@@ -46,6 +46,7 @@ module.exports = function (eleventyConfig) {
   eleventyConfig.addPassthroughCopy("retro/atari-vga/*.jpg");
   eleventyConfig.addPassthroughCopy("retro/laser-mouse/*.jpg");
   eleventyConfig.addPassthroughCopy("retro/mega-st-high/*.jpg");
+  eleventyConfig.addPassthroughCopy("retro/mistery-core/*.jpg");
 
   // Root-level shared assets
   eleventyConfig.addPassthroughCopy({ "shared/base.css": "shared-base.css" });

retro/mistery-core/index.njk

@@ -20,12 +20,33 @@ parent: "/retro/"
 <h2>My configurations</h2>
 <p>I've prepared five configurations, each for a different use case:</p>
 
+<img src="mistery-configs.jpg" alt="The MiSTery Core configuration selection screen" width="640" height="640" loading="lazy">
+<p class="caption">The MiSTery Core configuration selection screen, showing all five available setups.</p>
+
 <h3>1. iTOS 1.04 (same as the Low)</h3>
 <p>The same setup as on the <a href="/retro/mega-st-low/">Mega ST 4 "Low"</a>. With iTOS, pressing a number key and then space during boot selects the boot drive: 1 boots from D (GAMES), 2 from E (DEMOS), 3 from F (Medium Resolution). Exactly the way I have it on the real machine.</p>
 
+<img src="itos1.jpg" alt="iTOS boot screen showing drive selection" width="640" height="640" loading="lazy">
+<p class="caption">The iTOS boot screen with the drive selection prompt.</p>
+<img src="itos2.jpg" alt="iTOS booting from the selected drive" width="640" height="640" loading="lazy">
+<p class="caption">iTOS booting from the selected drive.</p>
+<img src="itos3.jpg" alt="iTOS demo running after boot" width="640" height="640" loading="lazy">
+<p class="caption">A demo running after boot on the iTOS configuration.</p>
+
 <h3>2. 68020 14 MB with Viking Card</h3>
 <p>This is the most interesting configuration. On the real Mega 4 "Low", high resolution is limited to 640x400, which always felt small to me, hence the <a href="/retro/et4000-experiment/">ET4000</a> experiments and eventually the <a href="/retro/mega-st-high/">Mega ST 4 "High"</a>. On the MiSTery Core, I can activate an FPGA recreation of the Viking graphics card. The original Viking had 1280x900, the FPGA version uses 1280x1024, which matches exactly the native resolution of my <a href="/retro/atari-monitor-compatibility/">NEC monitor</a>. Unlike the ET4000, which gives me 256 colours, the Viking is black and white only. But paired with Geneva and the faster 68020 processor, it's genuinely pleasant to work on. The core also emulates an EtherNEC and I have STinG configured for networking.</p>
 
+<img src="viking1.jpg" alt="Viking configuration booting via EmuTOS" width="640" height="640" loading="lazy">
+<p class="caption">The Viking configuration booting via EmuTOS.</p>
+<img src="viking2.jpg" alt="Viking GEM desktop loading" width="640" height="640" loading="lazy">
+<p class="caption">The Viking GEM desktop coming up.</p>
+<img src="viking3.jpg" alt="Viking GEM desktop at full resolution" width="640" height="640" loading="lazy">
+<p class="caption">The Viking GEM desktop at full 1280x1024 resolution.</p>
+<img src="viking4.jpg" alt="Geneva desktop on the Viking card" width="640" height="640" loading="lazy">
+<p class="caption">Geneva running on the Viking card.</p>
+<img src="viking5.jpg" alt="Geneva desktop with windows open" width="640" height="640" loading="lazy">
+<p class="caption">The Geneva desktop with windows open, the final result.</p>
+
 <h3>3. 68000 8 MB</h3>
 <p>A slightly improved version of my high resolution configuration without the Viking card. I use this one for testing only.</p>