igors@portfolio

Why this site looks like a terminal and what you can press here

Share

You opened a developer's site and saw a black screen, green lines scrolling past and something like igors@portfolio:~$. If you're not a programmer, the first question is a fair one: what is this, and where are the buttons? The buttons are there, the site reads fine without any explanation, and the terminal at the top isn't decoration. It's a real one, and you can use it.

It's like a workshop where the tools hang on the wall in plain view instead of being locked in a cupboard. That's what a developer's workbench looks like: a window of text where they type commands. I built the site as that window because it's the most honest thing I can show about my work without inventing pictures.

What the line igors@portfolio:~$ means

This is the terminal prompt, and it's on every page. You read it like this: igors is who's working, portfolio is the machine, ~ is the folder (the tilde means "home folder"), and $ means "waiting for a command". After it comes the command the site seems to have run to show you the page. whoami ("who am I") opens the block about me, cat ("show a file") opens an article, ls -l ("list files") shows a list of articles or tools. The folder in the prompt changes: in the blog you're in ~/blog, in the tools in ~/tools. It's the same breadcrumb trail as on any other site, just written as a path.

The first three seconds

On your first visit the site shows a short boot log, like a computer switching on: lines about memory, the network, "login successful". It's an in-joke. It lasts under three seconds, and any key skips it. The log is in English on purpose: system messages on any machine in the world are in English, whatever language the menu is set to. If your system has "reduce motion" switched on, the site respects it: no log, no rain, no text typed out letter by letter.

Six themes, two in the header

The icon in the header switches between two: the dark matrix the site opens with, and the light paper. There are actually six. The other four are colour schemes of code editors that programmers spend their days in: dracula, monokai, one-dark and nord. You switch them on from the terminal: theme nord, theme dracula and so on, and the site remembers the choice. A link can set the theme too: ?theme=paper at the end of the address opens the site light straight away.

In the dark themes, symbols fall behind the text. In the light theme, a grid of little squares quietly fills in instead of the rain. It's a quotation: it looks like a programmer's activity calendar on the sites where code is stored, each square a day and the colour showing how much got done. The rain is off on phones, as it's too heavy for small screens; the grid runs there too. With "reduce motion" neither background starts, because they shouldn't get in the way of reading. In the "about me" block my portrait is built from dots that scatter away from the cursor; without JavaScript you get an ordinary portrait made of characters.

The terminal is real

This is the main thing to try. On any page press the ~ key (to the left of the 1 on the keyboard) or the "terminal" button in the footer. A window opens that you can type into. Type help and press Enter, and the site lists what it can do. A few commands to start with:

  1. theme on its own lists all six themes, and theme matrix brings back the original.
  2. lang ru, lang lv, lang en change the language of the site.
  3. cookies shows what the site knows about you: analytics stays off until you agree, and the same command withdraws your consent.
  4. blog opens the list of articles, contact opens the form, portrait draws my portrait in characters right in the window, and neofetch shows the machine's "passport", the way programmers do in screenshots of their computers.
  5. exit closes the window, like a real terminal.

Easter eggs

The help list isn't everything. I left a few commands for people who remember what one usually types into someone else's terminal. They do nothing dangerous, but they answer:

  • sudo: an attempt to become administrator. The site replies the way Linux does when you're not allowed.
  • rm: an attempt to delete something. The portfolio is read-only.
  • ping: a real request to my server; the reply shows how many milliseconds the round trip took.
  • coffee: the server honestly admits it's a teapot.

That's not all: a few more familiar commands work, so look for them yourself. And if you're the kind who opens the developer tools (F12) first, look at the Console tab: there's a message there for you.

What this gives you as a customer

A developer's own site is the only place where you can see their work before you've paid. I test everything I recommend in my articles on myself: the page opens on a phone, the browser shows no "Not secure" next to the address, the year in the footer updates by itself, the privacy policy sits next to the form, and analytics waits for your consent. If any point from the one-minute check doesn't hold up here, write to me. It's the best reason to start a conversation.

And the terminal is a way of saying who I am, not with the words "reliable partner with an individual approach" but with tools on the wall. If you don't need them, you can browse the page like any other: menu, links, form, everything in its place.

How the site is built

No site builder and no heavy libraries: markup, styles and a little code that draws the rain, the portrait and the terminal. The blog articles are text files that get assembled into pages when I publish, so they open even with JavaScript switched off. The tools run in your browser, and nothing goes to the server until you press "send" yourself. The numbers for the articles come from my check of Latvian websites, and there's a separate page about it.

If you'd like your own site to talk about your business without extra words, write to me and I'll tell you where I'd start.

Share
← All articles