Static content catalogs keep launches repeatable
Why FabricBloc publishes reviewed content through generated catalogs instead of letting the browser fetch source files at request time.
The public site should not depend on a visitor's browser reaching GitHub. FabricBloc uses generated content catalogs so builds can validate schema, content hashes, review state, source paths, and canonical public URLs before publishing static pages.
That model keeps content easy to edit without making production fragile. Authors work in source-controlled Markdown and JSON, reviewers approve the catalog, and the site deploys pinned output that crawlers and agents can cite consistently.
Next step
Read the docs quickstart
Why FabricBloc publishes reviewed content through generated catalogs instead of letting the browser fetch source files at request time.
Continue