A Reference for Static and Custom Publishing
Standalone Blog 1.0.0 demonstrates how a static site generator, custom CMS, newsroom tool, documentation site, or hand-built blog can display VeriFact results. The sample uses plain HTML, CSS, and JavaScript so developers can understand the contract and adapt the interface without adopting a specific frontend framework.
The demonstration article shows a normal reading experience with compact numbered fact markers, article-level verification status, confidence, source cards, and a readable representation of the API response. The included sample response is simulated and its factual examples link to NASA primary sources; production sites must render the evidence returned for their own licensed request.
Reader Experience
- Keep the article as ordinary prose rather than separating every paragraph into fact and commentary blocks.
- Place a compact source marker at the end of the factual sentence it supports.
- Open evidence in a new tab and provide descriptive link text, accessible labels, keyboard focus, and responsive source panels.
- Show article-level status and evidence details without claiming that opinions, predictions, or unresolved statements were verified.
- Preserve the host site’s navigation, typography, content width, sidebar, feed, sitemap, and mobile layout.
Production Integration Architecture
A production standalone site should send editor content through a trusted backend or backend-for-frontend. That server authenticates to VeriFact API 3.5.0, submits claims or documents, validates and redacts the response, stores the approved public fields, and then publishes the resulting citations with the article.
Never embed a VeriFact license, API key, bearer token, Vault export, or private provider credential in browser JavaScript. Credentials belong in the OpenClaw Vault or another approved secret manager and should be delivered to the server process through safe environment mappings.
Deploy and Extend
The 1.0.0 reference can be served locally with Python’s zero-dependency HTTP server or copied to a static host. Developers can replace the included simulated response with a server-side VeriFact adapter, map evidence to their own article model, add approval gates to their publishing pipeline, and write verification metadata into a database, content manifest, or build artifact.
For automated publishing, run claim extraction before final rendering, require an explicit editorial policy for unresolved claims, preserve idempotency so retries do not duplicate articles, validate all generated HTML, and confirm that the landing page, feed, sitemap, images, navigation, sidebar, and responsive layout still pass after citations are inserted.
Product Boundaries
The Standalone Blog is a client and integration reference. It is separate from the VeriFact API service and the VeriFact WordPress plugin, and its 1.0.0 version does not change when either of those products ships a new release. It requires a licensed API connection for real verification.