Aether Static View catalog

Keep static release assets organized.

Publish a readable catalog and machine-friendly manifest beside static assets. Release reviewers get one source for files, cache policy, checksums, and public paths.

Explore live catalog Read the docs
Current release[email protected]
Manifest formatVersioned JSON
Release updatesAtom feed available
Security contactsecurity.txt published
Documentation sitesPublish reference files alongside docs builds.
Design systemsTrack icons, tokens, stylesheets, and package notes.
Static app releasesKeep release assets and cache rules easy to review.
Public resource indexesShare stable references without a heavy backend.
Product

A small publishing layer for files teams already ship.

Release manifest

Describe each release with version, asset list, checksum notes, public page references, and source context. The manifest stays readable for engineers, writers, and build automation.

Asset catalog

Keep filenames, file types, sizes, versions, and public references in one static HTML or JSON-friendly index.

Cache policy notes

Document which files can be cached for a day, a week, or only briefly after publication.

Checksum references

Attach short checksum values to files so release reviewers can compare expected and published assets.

Latest catalog

Current files from the Aether Static 2.2.0 release.

FilenameVersionTypeSizeChecksumCache rule
product.css2.2.0css55.6 KB69543c402c871 day
site.css2.2.0css40 B3ee122d673831 day
logo.png2.0.0png193.9 KB17148fd7cf281 day
manifest.json2.2.0json722 B6b71f04163795 minutes
status.json2.2.0json769 Ba0ec8ff1beaf5 minutes
feed.xml2.2.0xml1.4 KB6c76a90bfa691 hour
security.txt2.2.0txt268 B163f8e9696f81 day
Manifest health12 / 12 rows completeEvery published row resolves to a public path and includes cache intent.
Cache split3 metadata, 9 stableMetadata stays short-lived while versioned media and styles remain stable.
Review surfaceHTML + JSON + AtomThe same release is available to readers, build tools, and feed clients.
Release workflow

Simple enough to add to an existing static publishing process.

  1. Prepare assetsCollect stylesheets, indexes, SVGs, notes, and status files from the release build.
  2. Write manifestRecord version, asset names, checksums, cache rules, and public references.
  3. Publish static filesUpload the catalog and references next to the released assets.
  4. Review cache behaviorConfirm short-lived files and long-lived files have the intended headers.
Implementation

Publish the catalog next to the files your team already serves.

Recommended file structure

/catalog/index.json
/releases/[email protected]
/assets/product.css
/assets/logo.png
/status.json
/releases/feed.xml

Integration example

Read the catalog from a build note, docs page, or release checklist without adding a database.

curl https://aetherstatic.com/catalog/index.json

fetch("/catalog/index.json")
  .then((res) => res.json())
  .then((catalog) => {
    console.log(catalog.release, catalog.assets.length);
  });

Status

Catalog
Online
Manifest
Available
Docs
Available
Last updated
July 10, 2026
FAQ

Practical answers for teams publishing static files.

Is this a CDN?

No. Aether Static is a catalog and documentation layer. It describes what was published, where files live, and how cache rules should be read.

Can it work with existing static hosting?

Yes. Catalogs and manifests are plain HTML and JSON files, so they can sit beside assets on object storage, static hosting, or a docs site.

Do I need a backend?

No backend is required for the public catalog. Teams can generate the JSON during a release job and publish it with the rest of the static output.

How are cache rules documented?

Each row can include a short cache note, such as "10 minutes" for search indexes or "7 days" for versioned SVG sprites.