Native Markdown Wiki for Google SecOps

I can’t speak for all teams, but we specifically centralize our docs in something like Confluence because other teams, auditors, external stakeholders, etc. frequently need access to our SOC documents.

That said, I love the idea of automatically pulling relevant docs into specific cases based on tags. Imo, instead of a native wiki, a great middle-ground FR for the roadmap might be robust integrations/API connectors to tools like Confluence, Loop, OneNote, etc. That way, we get the 'single pane of glass' workflow in Google SecOps without creating another isolated documentation silo.

We found something that works really well for our team. We built an API connected to our documentation stored in SharePoint/OneNote and other cloud-based tools. Based on tags, we pull the HTML output directly into an HTML widget at the bottom of the page.

The widget always shows two options:
- **"Show Documentation"** — an inline hide/show toggle (hardcoded HTML)
- **"Jump to Documentation"** — a direct "open in new tab" link

It is just shown in smalles possible html widget at the bottom of the page - when you need it you just use extend icon to have it more fullscreanish way.

It wasn't particularly difficult to implement. The only real requirement is having some logic in the first playbook that is responsible for view - a single action block written in the IDE - to fetch the relevant solution based on tags. Tag management itself is straightforward and can be handled via data tables, which keeps the whole thing easy to maintain as your documentation grows.

Downsize might be if you have ticket that it’s there for more than 10days and you activly updated docs but I would say if this would be an issue there probably can be some job or refresh button to fix it :)