Convert 2022 posts from Svelte to Mdsvex

[Copilot]

Converted all 8 posts in the (2022) folder from +page.svelte to +page.svx (Mdsvex) format, aligning with the existing post conversion pattern used in other year folders.

Changes

• Posts without images (5): Direct conversion of +page.svelte → +page.svx, preserving script tags for data props where needed (e.g., StackBlitz embeds)
• Posts with images (3): Created separate image components using @sveltejs/enhanced-img with the ?enhanced modifier, following the existing pattern from converted posts:
  • groking-active-focus-and-focus-visible-pseudo-classes: 8 image components
  • recording-screencasts-on-a-hidpi-display: 1 image component
  • three-ways-to-bootstrap-a-svelte-project: 5 image components

Pattern

Image components follow the established convention:

<!-- DisplayPreferences.svelte -->
<script lang="ts">
	import src from './display-preferences-light.png?enhanced';
</script>

<enhanced:img {src} alt="Screenshot of display preferences on macOS." />

<!-- +page.svx -->
<script>
	import DisplayPreferences from './DisplayPreferences.svelte';
</script>

<Figure caption="macOS lets you choose your preferred scaled resolution." class="mb-6">
	<DisplayPreferences />
</Figure>

All content, imports, and functionality preserved. Existing component files (copy-button.svelte, scaled-pixel.svelte) remain unchanged.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Convert all 2022 posts to Markdown</issue_title>
<issue_description>- All posts except those in folder (2022) have been converted to Markdown.

• You need to replace the +page.svelte file with a +page.svx file.
• *.svx are Mdsvex files.
• Images are handled with @sveltejs/enhanced-img but outside Mdsvex files. You need to create an image component for each image and use that.
• Remove the +page.svelte files after converting them.
• Don't change the content of the posts.</issue_description>

<agent_instructions>If you are not sure about anything, ask me.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Convert all 2022 posts to Markdown #1074

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[railway-app]

This PR was not deployed automatically as @Copilot does not have access to the Railway project.

In order to get automatic PR deploys, please add @Copilot to your workspace on Railway.

[maiertech]

@copilot What's the difference between #1075 and #1076? Can you close the PR that is not needed any more?

[Copilot]

@copilot What's the difference between #1075 and #1076? Can you close the PR that is not needed any more?

PR #1076 (this PR) preserves the existing Svelte components (<P>, <Code>, <Figure>, etc.) and follows the same pattern as other converted posts in the repository. PR #1075 converted these to Markdown syntax.

Based on the requirement "Don't change the content of the posts", this PR (#1076) should be kept as it maintains the original component structure.

I don't have permissions to close PRs. Could you close PR #1075?

[maiertech]

Close in favor of #1075.