Back to site Product Export Preview

Knowledge / Reference Tool

Tuxborn Wiki Field Atlas

A maintained reference layer for the Tuxborn Skyrim modpack. This package is built for rapid route-finding across setup guidance, content planning, follower notes, FAQs, and completion checklists.

Open Upstream Wiki View Repository

What it is, and why it exists

Tuxborn has broad gameplay scope and many route decisions early in a run. The wiki structure reduces friction by keeping install choices, quest routing, and support answers in one indexed reference space.

The repo keeps authoring in wiki markdown while automation handles sync, link normalization, checklist rendering, and static deployment.

Reference systems

Wiki-first publishing

Contributors continue editing where they already work: GitHub Wiki pages.

Structured topic hubs

Major gameplay areas are grouped into navigable indices like Getting Started, Content and Quests, Followers, and FAQ.

Checklist dashboard

Spreadsheet data is rendered into searchable checklist pages with local progress tracking.

Automated rebuild cadence

Builds run on push, manual dispatch, and scheduled refreshes to keep content current.

How it fits player workflow

  1. 01. Set up the run

    Start with installation and configuration guides, then select profile and device-safe behavior.

  2. 02. Route content intentionally

    Use indexed quest and follower pages to choose starts, level timing, and path dependencies.

  3. 03. Track progress and unblock

    Check FAQ and known issues first, then escalate to support channels when needed.

Visual reference panel

The export includes a custom atlas preview image intended for catalog cards and social metadata. Replace this later with official branded captures when available.

  • Current preview is local and lightweight
  • Suitable as import-time fallback thumbnail
  • No external media dependency
Tuxborn Wiki atlas preview artwork
Export preview asset: ./assets/tuxborn-atlas-preview.svg

Proof and availability

100+

synced reference pages

3x

update paths (push, manual, weekly)

Wiki

authoring source of truth

Support route used in source docs: Aetherius Modding Discord.

FAQ

Where should maintainers edit content?

Edit the upstream GitHub Wiki. The static site is generated from that source.

Is this only for one hardware profile?

No. The docs include Steam Deck and non-Deck handheld guidance in addition to general setup content.

How is checklist completion handled?

The generated checklist pages store checkbox progress in the browser's local storage.

What if a page looks stale?

Confirm the upstream wiki version, then trigger the sync/build workflow to refresh this static mirror.

Need a route right now?

Use the source wiki for immediate navigation, then keep this export as the central-site product record under /products/tuxborn-wiki/.

Go to Tuxborn Wiki Open FAQ Index