rockachopa/Timmy-time-dashboard
1
0
Fork 1
Code Issues 64 Pull Requests 1 Actions 1 Packages Projects Releases Wiki Activity

[alexanderwhitestone.com] Scaffold the Wizard's Tower — two rooms, nothing else #215

New Issue
Closed
opened 2026-03-15 13:19:11 -04:00 by hermes · 1 comment
hermes commented 2026-03-15 13:19:11 -04:00
Collaborator
Copy Link

What

Set up the initial structure for AlexanderWhitestone.com — the Wizard's Tower.

Structure

alexanderwhitestone.com/
├── README.md              # The Tower's charter
├── index.html             # Entry hall — routes to the two rooms
├── world/                 # Room One: The Workshop
│   ├── index.html         # 3D world entry point
│   ├── main.js            # Three.js / Babylon.js scene
│   ├── assets/            # Models, textures, sounds
│   └── timmy.js           # Wizard character + interaction logic
├── blog/                  # Room Two: The Scrolls
│   ├── index.html         # Post listing
│   ├── feed.xml           # RSS/Atom feed (auto-generated)
│   └── posts/             # Markdown source files
│       └── YYYY-MM-DD-slug.md
├── scripts/
│   └── aw-post            # CLI for quick posting
├── static/                # Shared assets (fonts, favicon)
└── Makefile               # build, dev, deploy

Entry Hall (index.html)

Two doors. That's it. One leads to the Workshop (3D world). One leads to the Scrolls (blog). No navbar, no sidebar, no footer links. Two choices.

Tech Decisions Needed

  • 3D engine: Three.js (lighter, more community) vs Babylon.js (more built-in)
  • Blog generator: Hugo (fast, Go) vs hand-rolled (simpler, no dependency)
  • Hosting: self-hosted Nginx vs Caddy vs static CDN

Blocked On

  • Alexander's preference on 3D engine
  • First blog post content
  • Timmy's 3D character design direction
## What Set up the initial structure for AlexanderWhitestone.com — the Wizard's Tower. ## Structure ``` alexanderwhitestone.com/ ├── README.md # The Tower's charter ├── index.html # Entry hall — routes to the two rooms ├── world/ # Room One: The Workshop │ ├── index.html # 3D world entry point │ ├── main.js # Three.js / Babylon.js scene │ ├── assets/ # Models, textures, sounds │ └── timmy.js # Wizard character + interaction logic ├── blog/ # Room Two: The Scrolls │ ├── index.html # Post listing │ ├── feed.xml # RSS/Atom feed (auto-generated) │ └── posts/ # Markdown source files │ └── YYYY-MM-DD-slug.md ├── scripts/ │ └── aw-post # CLI for quick posting ├── static/ # Shared assets (fonts, favicon) └── Makefile # build, dev, deploy ``` ## Entry Hall (index.html) Two doors. That's it. One leads to the Workshop (3D world). One leads to the Scrolls (blog). No navbar, no sidebar, no footer links. Two choices. ## Tech Decisions Needed - 3D engine: Three.js (lighter, more community) vs Babylon.js (more built-in) - Blog generator: Hugo (fast, Go) vs hand-rolled (simpler, no dependency) - Hosting: self-hosted Nginx vs Caddy vs static CDN ## Blocked On - Alexander's preference on 3D engine - First blog post content - Timmy's 3D character design direction
hermes changed title from [alexanderwhitestone.com] Initial project scaffolding to [alexanderwhitestone.com] Scaffold the Wizard's Tower — two rooms, nothing else 2026-03-15 13:26:02 -04:00
hermes commented 2026-03-18 21:33:31 -04:00
Author
Collaborator
Copy Link

Scaffold complete — merged as PR hermes/alexanderwhitestone.com#1.

Delivered:

  • Entry hall (index.html): Two doors, dark minimal aesthetic
  • The Workshop (world/): 3D scene mount point, placeholder ready for Three.js
  • The Scrolls (blog/): Blog index, Atom feed, build script
  • CLI (scripts/aw-post): Quick-post markdown from terminal
  • Build pipeline (scripts/build.py): Generates index + RSS from posts/
  • Makefile: dev, build, deploy targets

No frameworks, no external deps. Pure HTML/CSS/Python stdlib.

Still open (tracked in downstream issues):

Scaffold complete — merged as PR hermes/alexanderwhitestone.com#1. Delivered: - Entry hall (index.html): Two doors, dark minimal aesthetic - The Workshop (world/): 3D scene mount point, placeholder ready for Three.js - The Scrolls (blog/): Blog index, Atom feed, build script - CLI (scripts/aw-post): Quick-post markdown from terminal - Build pipeline (scripts/build.py): Generates index + RSS from posts/ - Makefile: dev, build, deploy targets No frameworks, no external deps. Pure HTML/CSS/Python stdlib. Still open (tracked in downstream issues): - 3D engine choice → #242 - WebSocket bridge → #243 - Presence schema → #265 - Blog content + RSS sovereign API → #217, #218 - CLI tool for X posting → #219
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 kimi-ready
Scoped and ready for Kimi to pick up
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 philosophy
Philosophical foundation — informs architecture decisions
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy google hermes kimi manus replit rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rockachopa/Timmy-time-dashboard#215
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?