The matrix

Three sites, one practice.

An academic identity has to introduce, demonstrate and account. Those are different readers, different time scales, and different pages. The matrix gives each job a domain — and keeps them one body of work.

The argument

One site usually tries to be three things at once: a homepage, a notebook, and a CV. It ends up being a homepage with a CV link. The matrix separates the jobs without splitting the person.

The sites share a typographic hand, a role palette and one small dock. They do not share a CMS, a deployment pipeline or a copy of the same page. If one domain is down, the other two still work.

The rule

One artifact, one canonical home. A note lives on the Index, the full paper lives in the Lab, the CV lives in the Record. Other sites may keep a reading edition for context — the Index's thesis page is one — but the canonical copy is the one named below, and the reading edition links back to it.

Different temperature, same hand. The Index is a dark signal; the Lab is an instrument; the Record is paper. The base types, hairlines and page rhythms are shared. A visitor should recognise the family before reading the domain.

Every site works alone. A reader who arrives at the Record from a search result should get the record, not a redirect to a homepage. The matrix is a set of doors, not a maze.

The canonical map

The current allocation:

TABLE I. Content ownership across the matrix.
ArtifactCanonical siteWhy
Profile, Now, field noteszhengxs.comThe living signal; updated often.
Thesis, instruments, computationsqmentropy.comThe full text, figures and computations; the Index keeps a reading edition.
CV, education, publication listzhengxiangsheng.comThe stable dossier; the full name is the DOI.

The dock

One shared widget carries the matrix: a small dock at the lower left of every page. It knows which site it is on, marks the current role, and steps aside when the footer is in view. It is the only piece of JavaScript the three sites share.

The dock is injected by matrix.js. Installing the matrix on a new site is two lines and one meta tag:

<link rel="stylesheet" href="/assets/matrix/matrix.css">
<script defer src="/assets/matrix/matrix.js"></script>
<meta name="matrix-site" content="index">

Copy matrix.css, matrix.js and the two font files into the site; edit the ROLES array at the top of matrix.js to add a fourth node. The dock is deliberately site-local: no cross-domain script, no shared failure point.

The palette

Three role colours, used at the edges. They are navigation signals, not decoration, and never carry body text.

Index#FF6A3Don paper: #C2441C
Lab#7FDCF2on paper: #0E6F7A
Record#8FA6FFon paper: #1F3A93
Base#08090B / #F3F0E7ink and paper

Why not one site?

Because a CV is read in ninety seconds and a lab note is read for an hour. Because a search result for a paper and a search result for a person should land on different pages. Because a matrix lets each surface be excellent at its own job, while the cross-links do the work a single navigation bar cannot.

This page is the specification. The sites are the implementation. If you are building a matrix of your own, use the structure, replace the content, and keep the rule: one artifact, one canonical home.