Merge pull request #24 from AlexHedley/challenges

Add the Challenges section.

Author: KubaO

docs/Challenges/index.md

@@ -0,0 +1,15 @@
+---
+title: Challenges
+nav_order: 12
+permalink: /Challenges
+---
+
+# Challenges
+
+From **#general** on Discord:
+
+[From Wayne](https://discord.com/channels/927638153546829845/927638154192748606/1457062373465788671) in Discord:
+
+> As we kick off 2026, we’re introducing monthly twinBASIC challenges, giving you the chance to win a £100 account credit redeemable against future twinBASIC licences.
+
+See this on [twinBASIC Update: January 6, 2026](https://nolongerset.com/twinbasic-update-january-6-2026/) from Mike Wolfe.

docs/Challenges/self-contained_diagnostic_tool.md

@@ -0,0 +1,76 @@
+---
+title: Self-Contained Diagnostic Tool
+parent: Challenges
+nav_order: 1
+permalink: /Challenges/1
+---
+
+# twinBASIC Monthly Challenge #1
+
+## Self-Contained Diagnostic Tool
+
+Build a **self-contained Windows diagnostic tool** using **twinBASIC**.
+
+Your tool should report **useful information about the system it is running on**.
+
+There is **no single correct output** - different approaches and interpretations are expected.
+
+## Prize
+
+- £100 twinBASIC account credit
+- (non-transferable, no cash alternative, can only be used towards future twinBASIC licences)
+
+## Requirements
+
+- Built using **twinBASIC**
+- Submission must be a **single** `.twinproj` **file**
+- Produces a **single Windows EXE**
+- Runs on **Windows 10 and later**
+- No admin rights required (optional enhanced output when elevated)
+- **No external dependencies**  
+  (Built-in twinBASIC packages and built-in OS / WinAPI features only)
+- Output may be **console or GUI**
+
+## Diagnostic content
+
+Report information from **at least three distinct categories**.
+
+Examples:
+
+- OS version / build
+- CPU information
+- Memory usage
+- Disk information
+- Process information
+- Environment variables
+- System uptime
+- Locale / codepage
+- Network configuration
+- Installed runtimes (e.g. .NET)
+
+## Judging
+
+Entries will be judged across multiple categories, including:
+
+- Usefulness of reported information
+- Performance
+- Smallest EXE size
+- Well-documented or self-documenting code
+- Interesting or clever use of APIs
+- Derived or inferred system metrics
+- Overall elegance and polish
+
+Bonus points may be awarded for:
+
+- Use of newer twinBASIC features (e.g. delegates, generics)
+- Particularly clean or insightful design
+
+Winner selected at the **sole discretion of the twinBASIC team**.
+
+## Deadline
+
+Saturday 31st January 2026
+
+Submissions will be locked after the deadline.
+
+🔗: https://discord.com/channels/927638153546829845/1457060903332614357/1457060903332614357