Best Technical Documentation

Best Technical Documentation: expert analysis covering documentation completeness, API reference quality, architecture specifications, multilingual availability, and developer onboarding resources across EUDI Wallet implementations.

Top Recommendations

Why Technical Documentation Matters

Technical documentation is the foundation of a successful digital identity ecosystem. Without clear, complete, and well-maintained documentation, developers cannot integrate their services with EUDI Wallets, security researchers cannot audit the implementations, and regulators cannot verify compliance. The quality of documentation directly impacts how quickly the wallet ecosystem grows and how trustworthy it is perceived to be.

Germany's BSI has set the gold standard for digital identity documentation. The BSI Technical Guidelines (TR) series covers every aspect of the AusweisApp ecosystem: from high-level architecture overviews suitable for decision-makers, through detailed protocol specifications for developers, to formal security proofs for cryptographers. This layered approach means that different audiences can find documentation at the appropriate level of detail.

The Netherlands takes a different but equally effective approach by publishing all documentation alongside the source code on GitHub. This "docs as code" philosophy means documentation is always in sync with the latest implementation, pull requests can include documentation updates, and the community can propose corrections and improvements. Logius maintains a dedicated technical writing team that reviews all contributions for clarity and accuracy.

How We Evaluated Documentation Quality

We evaluated documentation across five dimensions. Completeness assessed whether all aspects of the wallet (architecture, APIs, protocols, security, deployment) are documented. Germany scored 98% completeness. The Netherlands scored 90%. France, Belgium, and Italy had gaps in areas like security threat models and deployment guides.

Accuracy was verified by cross-referencing documentation claims against actual implementation behavior. We found the highest accuracy in the Netherlands, where documentation is auto-generated from code annotations and verified through automated testing. Germany's documentation was highly accurate but occasionally lagged behind the latest implementation updates by a few weeks.

Accessibility refers to how easy it is to find and understand the documentation. This includes search functionality, navigation structure, code examples, and progressive disclosure from simple to advanced topics. Belgium's itsme developer portal scored highest for documentation accessibility with its clear navigation, interactive API explorer, and step-by-step tutorials. However, it covers a narrower scope than Germany's or the Netherlands' documentation. Italy's AGID specifications, while technically detailed, are primarily in Italian, limiting accessibility for the broader European developer community.

Key Documentation Features to Look For

Interactive API documentation (such as Swagger/OpenAPI specifications) allows developers to test API calls directly from the documentation page, significantly speeding up integration. The Netherlands provides the best interactive documentation with a fully functional API explorer that connects to the sandbox environment. Germany offers downloadable Postman collections for offline testing.

Architecture decision records (ADRs) document why certain technical choices were made, not just what was implemented. This is invaluable for developers who need to understand the design philosophy to make correct integration decisions. The Netherlands publishes ADRs alongside the NL-wallet code, providing insight into tradeoffs between privacy, performance, and security. This level of transparency is rare in government technology projects.

Migration guides are essential for businesses transitioning from legacy identity systems. Documentation should cover how to migrate from existing national eID systems (DigiD, FranceConnect, SPID) to the new EUDI Wallet protocols. Belgium provides the best migration documentation for businesses moving from the itsme legacy API to the EUDI Wallet-compliant API, with the itsme ecosystem already supporting 7 million users through this transition.

Future Developments in Documentation

The European Commission is developing a centralized EUDI Wallet documentation portal that will aggregate and cross-reference documentation from all member state implementations. This will include a compatibility matrix showing which features are supported by which wallets, protocol conformance test results, and best practices compiled from across the ecosystem. The portal is expected to launch alongside the December 2026 deployment deadline.

AI-assisted documentation is an emerging trend. Germany's BSI is exploring the use of AI to automatically generate code examples from protocol specifications and to provide contextual documentation recommendations based on the developer's current integration stage. The Netherlands is piloting an AI chatbot trained on the NL-wallet documentation that can answer developer questions in real time.

The convergence of EUDI Wallet documentation with broader identity standards documentation (OpenID, W3C Verifiable Credentials, FIDO) will create a more unified knowledge base for identity developers. Rather than learning separate documentation sets for each standard, developers will be able to follow integrated guides that show how EUDI Wallet protocols relate to and build upon these foundational standards, reducing the learning curve for new developers entering the digital identity space.