gig-line

93 Commits 2 Branches 11 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
zwitschi	e93c27054a	docs: reconvert architecture.adoc to markdown via asciidoctor→docbook→pandoc Replaced the Python-converted architecture.md with a proper pandoc conversion chain: asciidoctor -b docbook5 → pandoc -f docbook -t gfm This fixes table rendering (pipe tables instead of grid tables), interpolates AsciiDoc attributes ({project-name} → Gig Line), strips anchor IDs, and normalises escaping. Post-processed: glossary italic leak from cols="e,2e" table, ® → (R) for the reset key, \>/> escapes. Also: - prettier 3.9.10 installed globally as the Markdown formatter/linter - .prettierrc: proseWrap=never, tabWidth=2 - .prettierignore: skips Binaries/, .uasset, .umap, *.blend, images - architecture.md passes prettier --check	2026-11-08 13:26:17 +01:00
zwitschi	d03829b699	docs: add Markdown rendering of arc42 architecture documentation architecture.md is the combined 450-line single-page rendering of all 12 arc42 sections. The Asciidoctor source (.adoc) files remain for future editing; the Markdown is the readable deliverable.	2026-11-08 13:12:33 +01:00
zwitschi	72705268b5	docs: arc42 architecture documentation for Gig Line Populated from the arc42-template (EN/adoc) with project-specific content across all 12 sections: 1. Introduction and Goals — requirements overview, quality goals, stakeholders 2. Architecture Constraints — technical (engine, collision, coordinates), organisational (squash-merge, visual review, provenance), conventions 3. Context and Scope — business and technical context tables 4. Solution Strategy — technology decisions, top-level decomposition, quality achievement approach 5. Building Block View — Gameplay (6 C++ classes), Site (7 meshes + 7 materials), Facades (9 buildings), Art Pipeline, QA & Review; Level 2 white boxes for input flow and collision model 6. Runtime View — walk, screenshot capture, QA self-test, build/import pipeline scenarios 7. Deployment View — dev workstation and packaged build infrastructure 8. Cross-cutting Concepts — coordinate system, collision model, lighting, materials, data provenance, QA harness 9. Architecture Decisions — 7 ADRs (dynamic lighting, UE materials, C++ collision helper, grounded reset, core ticker, Y convention, headless Blender) 10. Quality Requirements — overview table + 7 measurable scenarios 11. Risks and Technical Debts — 5 risks, 2 debts with mitigations 12. Glossary — 16 domain-specific terms Master document: Docs/Architecture/architecture.adoc Config: Docs/Architecture/config.adoc	2026-11-08 13:08:35 +01:00

Author

SHA1

Message

Date

zwitschi

e93c27054a

docs: reconvert architecture.adoc to markdown via asciidoctor→docbook→pandoc

Replaced the Python-converted architecture.md with a proper pandoc
conversion chain:

  asciidoctor -b docbook5  →  pandoc -f docbook -t gfm

This fixes table rendering (pipe tables instead of grid tables),
interpolates AsciiDoc attributes ({project-name} → Gig Line), strips
anchor IDs, and normalises escaping. Post-processed: glossary italic
leak from cols="e,2e" table, ® → (R) for the reset key, \>/> escapes.

Also:
- prettier 3.9.10 installed globally as the Markdown formatter/linter
- .prettierrc: proseWrap=never, tabWidth=2
- .prettierignore: skips Binaries/, *.uasset, *.umap, *.blend, images
- architecture.md passes prettier --check

2026-11-08 13:26:17 +01:00

zwitschi

d03829b699

docs: add Markdown rendering of arc42 architecture documentation

architecture.md is the combined 450-line single-page rendering of all 12
arc42 sections. The Asciidoctor source (.adoc) files remain for future
editing; the Markdown is the readable deliverable.

2026-11-08 13:12:33 +01:00

zwitschi

72705268b5

docs: arc42 architecture documentation for Gig Line

Populated from the arc42-template (EN/adoc) with project-specific content
across all 12 sections:

1.  Introduction and Goals — requirements overview, quality goals, stakeholders
2.  Architecture Constraints — technical (engine, collision, coordinates),
    organisational (squash-merge, visual review, provenance), conventions
3.  Context and Scope — business and technical context tables
4.  Solution Strategy — technology decisions, top-level decomposition,
    quality achievement approach
5.  Building Block View — Gameplay (6 C++ classes), Site (7 meshes + 7
    materials), Facades (9 buildings), Art Pipeline, QA & Review; Level 2
    white boxes for input flow and collision model
6.  Runtime View — walk, screenshot capture, QA self-test, build/import
    pipeline scenarios
7.  Deployment View — dev workstation and packaged build infrastructure
8.  Cross-cutting Concepts — coordinate system, collision model, lighting,
    materials, data provenance, QA harness
9.  Architecture Decisions — 7 ADRs (dynamic lighting, UE materials,
    C++ collision helper, grounded reset, core ticker, Y convention,
    headless Blender)
10. Quality Requirements — overview table + 7 measurable scenarios
11. Risks and Technical Debts — 5 risks, 2 debts with mitigations
12. Glossary — 16 domain-specific terms

Master document: Docs/Architecture/architecture.adoc
Config: Docs/Architecture/config.adoc

2026-11-08 13:08:35 +01:00