Code + editing
VS Code, terminal-first workflows, and Git as the ground truth for change and rollback.
Uses
A practical toolkit for calm, maintainable work.
This is not a gear flex list. It is the stack and operating posture behind the studio: lightweight where possible, explicit where trust matters.
Foundation stack
Publishing
GitHub Pages for durable public surfaces with low ops overhead and clear deployment behavior.
Site architecture
Plain HTML/CSS/JS with small JSON files and scripts where automation genuinely removes repetitive work.
Workflow principles
- Prefer simple systems: fewer moving parts usually means better uptime and cleaner handoffs.
- Automate selectively: catalog generation, feed rendering, and repetitive sync jobs are good automation targets.
- Keep failure visible: if an integration fails, the site should still function and communicate clearly.
- Stay local when useful: private drafts and focused model work benefit from local-first workflows.
Current tool groups
Software tools
- GitHub: source control, issue tracking, and publishing routes.
- Python scripts: lightweight content syncing and data generation tasks.
- Vanilla JS: progressive enhancement for filters, feed widgets, and transitions.
Physical + planning tools
- Notebook capture: quick route notes and system sketches before formal structuring.
- Desk workflow: small, repeatable setup that supports shipping without setup drag.
- Field context: travel and site conditions influence reliability decisions in product design.