Visibility
Stable| Level | Audience | May be published to this site |
|---|---|---|
public | Anyone | Yes |
research | The research community; unreviewed work shared openly | Yes, with a status marker |
advisor | Advisor and committee only | No |
confidential | Author only, or under an agreement | No |
What “may be published” means here
This site is deployed publicly. Anything committed to content/ is on the
internet the moment it is deployed, whatever a front-matter field says. The
visibility field is a statement of intent that governs what may be written
into content/ at all; it is not an access control.
Material at advisor or confidential belongs in the archive/ tree or in
docs/, both of which are outside the published page tree, and docs/ is not
committed at all.
Enforcement
| Layer | What it does |
|---|---|
.gitignore | Keeps docs/ and common secret-bearing files out of Git |
| Repository layout | content/ is published; archive/ and docs/ are not |
| Robots and metadata | Preview deployments are noindex; production is indexed |
| Review | A human check before anything is committed |
Before committing
Unpublished results, data under an agreement, anything with a person’s private information in it, and any credential are checked for before every commit. This is the one convention where the failure is not recoverable: a public Git history keeps what was pushed even after it is deleted.
Preprints
Posting a preprint is publication for the purposes of many venues. Check the
target venue’s preprint policy before anything reaches public, and record
the policy on the publication’s own page. This is recorded per publication
rather than assumed, because the policies genuinely differ.