Public knowledge
Product structure and general principles can be open.
KNOWLEDGE & CONTROL
Knowledge, access and operations. Together.
One controlled place for documentation, support, downloads, status and trust material.
Documentation
Product structure, functions and deployment.
→EPTTSupport
Clarification, faults and escalation.
→EPTTDownloads
Controlled clients and releases.
→EPTTService status
Service areas and monitoring.
→EPTTTrust Center
Data, responsibility and operating model.
→EPTTSecurity
Security principles and open documentation requirements.
→KNOWLEDGE CONTROL
Resources should lead to action — not just more pages.
Documentation, support, downloads, status and trust serve different roles. They belong together, but access and evidence level should remain explicit.
Controlled material
Clients, releases and customer-specific documents need managed access.
Live data
Status should look live only when monitoring is actually connected.
01Documentation
Explain product and workflows without exposing owner internals.
02Support
Start from the concrete operation or problem type.
03Downloads
Tie packages to version, platform and release context.
04Trust
Separate documented facts from open release gates.
The resource area is a control surface for knowledge and access — not a dump of loose links.