Aether Static gives front-end, documentation, and design-system teams a durable place to publish file inventories, cache behavior, checksums, and public references beside existing static hosting.
List release files with filenames, versions, sizes, types, owners, and human-readable notes. The catalog gives writers, designers, and engineers one shared reference for what changed in a static build.
On this site: the current catalog distinguishes updated metadata from stable logo and favicon assets.
Keep a compact manifest beside each release. It can describe the release name, asset groups, public references, and supporting notes that explain how files should be consumed.
On this site: release 2.2.0 links to an immutable JSON manifest and the current catalog pointer.
Document intended cache windows for frequently changed indexes and long-lived versioned assets. The policy notes help reviewers understand which files should update quickly and which can remain stable for longer periods.
On this site: status.json uses a five-minute policy while product.css is stable for one day.
Add checksum notes for key files so release reviewers can compare what was prepared with what was published. The values are short reference points, not a replacement for the team's normal release approval process.
On this site: each stable file includes a shortened SHA-256 reference in the catalog.
Publish stable pages for teams that need simple references: what was released, where files live, and which notes explain the cache or version choices.
On this site: catalog JSON, status JSON, release manifests, and the Atom feed are all static public resources.
Aether StaticView catalog{
"release": "[email protected]",
"assets": [
{"file": "product.css", "cache": "1 day"},
{"file": "status.json", "cache": "5 minutes"}
]
}