useContentEngineering Documentation

A wallet-native content platform with access policies, on-chain subscriptions, protected files, and creator billing.

Start with Overview

View Architecture

Wallet-native identity

Users sign nonce challenges with an EVM wallet and receive a short-lived JWT session.

Policy-based access

Posts and projects are protected through reusable access policies with subscription, token, NFT, AND and OR rules.

Protected content delivery

Metadata is stored in MongoDB, binary content is stored in MinIO, and private downloads are issued through backend-verified signed URLs.

On-chain subscriptions

Smart contracts handle reader-to-author subscriptions and author-to-platform billing with events confirmed by the backend.

What this documentation is

This portal describes useContent as an engineering system. It is not an end-user help center. The goal is to explain the current implementation: architecture, flows, data model, smart contracts, deployment and testing.

The documentation is intentionally focused on implemented behavior. Potential future features are not mixed into the core pages.

Fast paths

ArchitectureArchitecture OverviewSee how the browser, backend, MongoDB, MinIO and EVM networks interact.FlowRuntime FlowsFollow file upload, subscription confirmation, billing and promoted feed paths.FrontendFrontend Data FlowUnderstand TanStack Query, API classes, session state and mutation invalidation.OpsDeploymentReview Coolify runtime, GitHub Actions, contract workflows and static docs deploy.