CRT Terminal UX Case

Concept

CRT Terminal turns a portfolio page into an interactive command-line object. The interface removes traditional navigation and asks the user to explore through typed commands, making the act of discovery part of the visual identity.

UX Problem

Most project pages explain interaction from the outside: menu, hero, cards, text, CTA. This concept needed the opposite feeling. The user should feel like they have found an old machine and are learning its language, while still understanding what can be done next.

Goals

• Create a memorable first interaction instead of a standard landing layout.
• Make commands discoverable through help, feedback, and short system responses.
• Keep the interface readable inside a noisy retro visual style.
• Use motion, scanlines, color modes, and glitches as feedback rather than decoration only.
• Support keyboard-first interaction while keeping the experience simple enough for casual users.

User Flow

1. The terminal boots automatically and confirms that the system is ready.
2. The user is invited to type help.
3. Help reveals a small command vocabulary, reducing uncertainty.
4. The user tries commands such as about, color, matrix, scan, glitch, and ux.
5. Each command returns an immediate state change or response, so the system feels alive.
6. The ux command opens this dossier as the deeper case-study layer.

Interaction Logic

The terminal uses typed input as navigation. This makes every action intentional: the user chooses a command, receives feedback, and learns the system through repetition. The prompt, cursor, loading bars, scan sequence, matrix mode, and color modes all reinforce the same interaction language.

Design Decisions

• The CRT frame creates a physical boundary for the interface.
• Text is short in the terminal so the screen never becomes visually overloaded.
• The UX dossier opens as a separate folder because long reading does not belong inside the tiny terminal log.
• Green, amber, and blue modes let the user customize the mood without changing the system model.
• Glitch and matrix effects are temporary, so they feel expressive without blocking the core flow.

Accessibility Notes

The project keeps high contrast, large monospaced text, visible system feedback, reduced command count, and a close button for the dossier. The design is intentionally stylized, but the user should always understand whether the system is waiting, loading, responding, or shutting down.

Result

The final experience behaves like a tiny operating system for a portfolio concept. It communicates personality through interaction, not through a static hero section, and gives the UX case its own readable folder layer.