Nathan's Technology Wiki

Purpose

This wiki turns technical work into a durable learning record. It connects applications, security controls, network design, testing, roadmaps, release processes, and operational lessons in an article format inspired by traditional wikis.

Architecture

The application uses Vinext with React and Next.js-style App Router pages. A shared WikiArticle component supplies consistent header, navigation, contents, article layout, and footer behavior. Concept and project pages remain independent routes, so large subjects can grow without turning the home page into one monolithic document.

Content model

Docker and Nginx Proxy Manager

A multi-stage Node.js image builds the site and runs the production output on port 3256. Docker Compose names the container, publishes the port, and restarts it unless stopped. NPM routes the wiki hostname to the Docker host, forces HTTPS, enables HTTP/2 and WebSockets, and uses a Let's Encrypt certificate whose name matches the domain.

Security and privacy

• The public wiki documents architecture without publishing credentials, exact proxy targets beyond the approved wiki route, or firewall rules.
• Build artifacts contain site content but no application database or user authentication secrets.
• HTTPS is validated through the public hostname and direct NPM path.
• Every page checks internal anchor targets so navigation does not silently break.
• Infrastructure administration remains separate from public learning content.

History and lessons

The initial repository history records the first wiki on July 30, a Wikipedia-inspired redesign, and the vibe-coding project playbook on July 31. Subsequent work added network documentation, secure coding, testing, project delivery, future planning, Docker/NPM deployment, and separate concept/project routes.

• Documentation architecture matters when a single page grows too large.
• Public deployment requires the application, proxy, DNS, and certificate to agree.
• Validation is strongest when it checks container health, HTTP behavior, certificate identity, route content, and internal links.

Roadmap

The roadmap grows this site from a hand-maintained article collection into a searchable, evidence-driven technology knowledge system. Planned work covers consistent project records, real search, recent changes, safe repository integration, diagrams, release evidence, backup and recovery, accessibility, and carefully governed local AI assistance.