Intel OpenVINO Developer Docs
Owned developer documentation for the OpenVINO and Tiber Edge AI platforms: two inference toolchains, two deployment environments, covering the full developer journey from install to production.
Two toolchains, two platforms, one developer journey
OpenVINO and Tiber Edge AI serve distinct deployment environments, cloud edge and on-device, with overlapping but not identical developer audiences. Each toolchain has its own model conversion pipeline, inference engine API, and deployment workflow.
The documentation challenge was maintaining a coherent developer journey across both platforms without duplicating content or creating navigation dead-ends for developers who needed to move between toolchains.
OpenVINO toolkit
Model optimization and inference for Intel hardware: install, model conversion, inference API, deployment walkthroughs.
Tiber Edge AI
On-device AI platform documentation covering the edge deployment pipeline and platform-specific APIs.
Cross-platform IA
Unified information architecture and navigation serving developers across both toolchains.
Full information architecture ownership
Owned the complete documentation stack, not just writing, but the architecture that determined how content was structured, versioned, and published across both platforms.
- Designed the information architecture from the ground up: topic hierarchy, cross-references, and navigation that served both beginner and expert developer paths.
- Built a versioning approach that kept multiple OpenVINO releases accurate and navigable without creating maintenance overhead.
- Owned the Sphinx-based build and publish pipeline running on GitHub Actions: responsible for both the content and the system that delivered it.
- Wrote and maintained install guides, model conversion walkthroughs, inference engine API references, and deployment documentation across release cycles.
Documentation as a system
DITA-based structure
Topic-based authoring with structured reuse across overlapping content between the two platforms.
CI/CD publishing
GitHub Actions pipeline building and deploying docs on every merge: documentation treated as a software artifact.
Multi-audience IA
Separate entry points and progressive disclosure for developers new to edge AI versus experienced OpenVINO users.
What this project demonstrates
- 1Owning the toolchain is as important as owning the content. A well-architected build pipeline keeps documentation accurate across release cycles without heroic manual effort.
- 2Cross-platform documentation requires explicit architectural decisions, not just good writing. Navigation structure determines whether developers find what they need.
- 3DITA topic-based authoring pays dividends when content overlaps across platforms: structured reuse prevents drift between parallel documentation sets.