The Midnight SDK documentation says "deploy your contract." It does not mention the two hours you'll spend figuring out why signRecipe() silently corrupts your transaction intent, or why every contract call fails because the network ID defaults to 'undeployed'.

Public blockchains sell transparency as a feature. GDPR and LGPD treat transparency of personal data as a violation. If you store a user's consent status on Ethereum to prove compliance, you have instantly violated compliance. This is not a design flaw you can patch — it's a structural paradox that required a fundamentally different blockchain architecture to resolve.

Public blockchains are transparent by design. GDPR and LGPD require data minimization by default. If you're building applications that need both trust and compliance, you're working against the architecture — unless the architecture was designed for exactly this tension.

When you document a zero-knowledge system, you face a fundamental paradox: you need to explain clearly what the system does without undermining the very privacy guarantees it provides.

Compact is not Solidity. It's not Rust. It's a purpose-built language for writing zero-knowledge smart contracts on Midnight Network — and documenting it required rethinking how we explain smart contract behavior entirely.

When I chose Docusaurus 3 for DPO2U's documentation site, the decision wasn't obvious. Here's why I picked it over Nextra, GitBook, and Mintlify — and the configuration decisions that shaped the final result.