Zaions Portfolio

Two portfolios by one person is a decision that has to earn itself.

The obvious version is one site with a different logo on it. That is cheaper, it is faster, and it produces a document that reads as neither a person nor a company, because the two answer different questions and a page trying to answer both answers each of them halfway.

So this one picks a side. It is built as a company surface and it admits it.

It carries a homepage, a searchable directory of work, a content hub, contact and payment routes, and the full legal pages a business has to have somewhere findable. Behind all of that sits a real content management system rather than a settings screen.

That administration layer is where most of the work went.

Posts, pages, portfolio items, taxonomies, media, payment methods, comments and users each get their own screens. Written out as a list it sounds like scaffolding. In practice it is the difference between a site somebody maintains and a site that quietly stops being true, because content edited in source is content shipped by deployment, and content shipped by deployment eventually is not edited at all.

The architecture underneath is strictly zero cost, and that word is doing real work.

Authentication, the database and hosting sit on free tiers. Uploads go to FilesHub rather than to cloud storage. Local state uses the device's own preferences store. There are no serverless functions anywhere in the design, which is the part that usually surprises people, because functions are the default answer to anything needing a moment of trusted compute.

Removing them costs something real.

Anything genuinely requiring a server that a client cannot be trusted with is off the table, and that is a category with real things in it. What is bought in exchange is a site with nothing to keep alive, no invocation billing, and no vendor whose pricing can move underneath it later. For a brand surface expected to sit there being correct for years, that trade is the right way round.

Discovery was built rather than assumed.

The build emits prerendered route shells with per-page metadata, social cards and structured data, alongside a machine-readable file for readers that want the data rather than the page. A single-page application shows a crawler an empty shell until its JavaScript runs, and a company site nobody can find is an expensive way of having no company site.

It installs as a progressive web app.

An offline shell comes with it. That is a small thing, and it is the honest form of a mobile presence here. No store, no review queue, no account with anybody, and an icon on a home screen for whoever wants one.

One more property is worth naming, because it is the reason the directory is worth building at all.

A searchable directory is a different object from a list of links. It has to hold a shape that new entries fit into without renegotiating, which means the taxonomy is the design decision and the search box is the easy part. Get the categories wrong and every item added afterwards either bends to fit them or quietly sits in the wrong place.

What it cost is duplication.

Every fix that matters to both sites has to be made twice, and the temptation to merge them will come back every time that happens. The answer is the same each time: they are two documents with two jobs, and the cost of keeping them apart is lower than the cost of a page that does not know who it is talking to.