A feed answers one question very well:
What is new?
An archive answers a different question:
What is here?
That difference shaped the ARCHIVE section of this site.
I did not want another chronological stream of posts, experiments and images slowly disappearing beneath newer material.
I wanted a place where unrelated things could remain useful.
Recency is not structure
Feeds are effective because they require almost no information architecture.
Publish something.
Put it at the top.
Everything else moves down.
That works well when recency is the most important property of the content.
It works less well for a utility I built two years ago, a reference image I still use, a machine I keep modifying, a design system, a small experiment or an artifact connected to a larger project.
Those things do not become less relevant simply because they are older.
The archive therefore needed another organizing principle.
Categories have to describe the thing
The taxonomy became:
ART / IMAGES
SYSTEMS / LIBRARIES
TOOLS / UTILITIES
MACHINES
GAMES
OBJECTS
PLACES
REFERENCES
EXPERIMENTS
The labels are intentionally plain.
Their job is retrieval.
I was particularly interested in keeping three categories distinct.
SYSTEMS / LIBRARIES are reusable authored frameworks.
TOOLS / UTILITIES are small functional things that perform a job.
EXPERIMENTS exist mainly because something was being tested or learned.
Those can easily collapse into one vague bucket called “projects.”
Separating them preserves why the thing exists.
Records instead of cards
The interface followed the same logic.
ARCHIVE uses a directory rather than a card grid.
Each item behaves like a record.
There is an ID, a type, a title, an availability state and a date. Selecting the record opens a detail area rather than sending the user immediately into another page.
The interaction is closer to browsing a file system than scrolling a gallery.
That is useful because visual prominence is not the ranking system.
A small utility can sit beside a large image study without pretending they are equivalent portfolio projects.
They simply occupy the same archive.
Availability is part of the record
Not everything in an archive should be downloadable.
Some things can be viewed.
Some can be demonstrated.
Some are real tools.
Some can be requested.
Some should remain private.
So availability became part of the metadata:
VIEW ONLY
DEMO
DOWNLOAD
WEB
ON REQUEST
PRIVATE
That is more useful than forcing every artifact into the same call to action.
It also keeps the archive honest.
A prototype does not need to pretend to be a product.
A private system does not need to be made public just because its name appears in an index.
Search changes the value of old work
The interesting thing about an indexed archive is that old work can become useful again.
A system built for one project can be rediscovered when another project needs the same principle.
A small tool can remain available long after it would have disappeared from a feed.
A reference can sit next to the work it influenced.
The archive becomes less like a publication stream and more like external memory.
That is the value I wanted.
Not nostalgia.
Retrieval.
An archive does not have to be complete
There is a risk in this kind of system.
Once everything can be indexed, everything starts feeling indexable.
That can turn an archive into an administrative project.
I do not want that either.
The archive should contain things worth finding again.
It does not need to document every file, every unfinished idea or every object I have ever owned.
Selection still matters.
The difference is that selection is based on future usefulness, evidence and context rather than whether something deserves a large case-study page.
A different relationship with time
A feed is built around now.
An archive is built across time.
That makes it a better home for the parts of my work and interests that do not behave like conventional portfolio projects.
Tools can remain tools.
Experiments can remain experiments.
Machines can continue changing.
References can keep being references.
And an artifact does not have to become content just to stay visible.
That is the distinction.
A feed wants the next thing.
An archive wants the thing to remain findable.
