Markdown is something you are already using. But do you colocate your internal docs with code? We will unpack how to use open source to record and share tribal knowledge buried in your team's bash aliases & histories – ensuring code and internal docs will no longer diverge.

We'll illustrate how Notebooks, Devcontainers, Web Components, and the VS Code platform, first conceived for analysis, excel at delivering runnable internal docs, reliably describing your team’s tasks, workflows, and solutions. An IDE for Ops is a human-centric approach that isn’t mutually exclusive with CI/CD.

We will learn:
1. Open tech applied for shareable and reliable docs via notebooks
2. How to bridge terminal, browser, and editor
3. Complementary nature with existing best practices

This approach paves the way to DevX & OpsX equilibrium. Allowing devs to trust abstractions (pipelines and internal platforms) while teams owning them benefit from the transparency of runnable docs' self-documenting properties.