/terminal
Explore the Pakkit network.
A keyboard-friendly, terminal-style map of Brandon Donaly's professional work, projects, writing, music, games, experiments, and collaboration paths — type a command or just follow the links.
This terminal only navigates public pages on pakkit.net. It does not execute code, connect to systems, or send your input anywhere.
Live terminal
LOCAL NAVIGATORPakkit Terminal
A local navigator for the public site.
Type "help" to see available commands.
Try: help · map · search music · open contact
JavaScript is off, so the live input is disabled. Everything is still here — use the command reference and directory below; each command maps to ordinary links.
Command reference
Every command is also a normal way to browse — these all work the same whether you type them or use the directory below.
- help
- List the available commands and what they do.
- whoami
- A short identity summary with links to the about pages.
- map
- Show the high-level site map, grouped by area.
- build
- Engineering, projects, services, and trust links.
- create
- Writing, resources, speaking, and music links.
- play
- Gaming, PakkitPup, and experiment links.
- projects [term]
- Highlighted work; an optional term filters the index.
- services
- Where to start working together.
- read
- Writing and reusable knowledge.
- now
- Current focus, tools, and the lab.
- trust
- How the work is built and shared responsibly.
- contact
- Ways to reach Brandon.
- search <term>
- Find a destination by name, tag, or description.
- open <name>
- Jump to a destination by its short name.
- clear
- Clear the screen.
Destination directory
Every public page the terminal can reach, grouped by area. These are ordinary links.
Identity
Who Brandon is and where to start.
- Home — The front door — the three-sided overview of Brandon's work.
- About — The longer story: disciplines, values, and how he works.
- Pakkit — The handle and the playful, fox-flavored identity behind it.
- Start Here — A guided first-visit map for finding the right page fast.
- Brandon Donaly — The full-name landing page for the person behind Pakkit.
Build
Engineering, projects, services, and trust.
- Build — The engineering pillar: software, security, infra, automation.
- Work — Selected professional work and what each piece proves.
- Projects — The full project index — case studies and experiments.
- Services — The service menu — concrete ways to work together.
- Trust — How access, data, and responsibility are handled.
- NexusPort — A current product concept under a working name.
Create
Writing, resources, speaking, and music.
- Create — The making pillar: writing, music, and creative tech.
- Blog — Field notes on building, security, and weird ideas.
- Resources — Reusable playbooks and checklists for slicing and automation.
- Speaking — Talks, topics, and what Brandon likes to speak about.
- Music — DJ PakkitStorm — bass-forward sets and the creative side.
- Building in Public — How the work and the product get shared as they're built.
Play
Gaming, the fox, and side experiments.
Learn
How the work is made and explained.
- Reading Paths — Curated routes through the writing by topic and goal.
- How I Build — The slicing-and-validation loop behind every change.
- Colophon — How and why this site itself is built.
Current
What's happening right now and the gear behind it.
Connect
Ways to reach Brandon and collaborate.
- Work With Me — Practical ways to collaborate and where Brandon fits.
- Contact — The direct ways to reach Brandon.
- Media Kit — Reusable bios, identity labels, and links for collaborations.
- Mentorship — Technical mentorship and how that collaboration works.
What this is (and isn't)
- It's a site navigator styled like a terminal.
- It is not a real shell, a command runner, a remote console, or a security demo.
- It is not a chatbot, an AI agent, or a downloadable app.
How it works
- Commands are parsed locally in your browser — nothing is sent to a server.
- There is no account, login, or code execution of any kind.
- Command history lives only in memory for this page session; refreshing clears it.
- The terminal does not add its own command-input tracking or storage.
- Every link works without JavaScript via the directory below.
Exit terminal
Prefer a normal conversation?
If you'd rather just talk it through — a technical problem, a product idea, a creative collaboration, a community tool, or an unusual cross-disciplinary project — reach out directly.