Skip to content

docs: add OKF integration guide (.graphifyignore fix for index.md clutter)#2097

Open
avps82 wants to merge 1 commit into
Graphify-Labs:v8from
avps82:docs/okf-integration
Open

docs: add OKF integration guide (.graphifyignore fix for index.md clutter)#2097
avps82 wants to merge 1 commit into
Graphify-Labs:v8from
avps82:docs/okf-integration

Conversation

@avps82

@avps82 avps82 commented Jul 22, 2026

Copy link
Copy Markdown

Summary

  • Adds docs/okf-integration.md — a guide for using Graphify alongside OKF (Open Knowledge Format)
  • Documents the friction point: OKF places index.md bundle manifests inside project subdirectories, which Graphify picks up as graph nodes and mixes into the code graph
  • Covers three options: .graphifyignore for isolated OKF folders, --ast-only for scattered index files, and intentional inclusion when you want docs + code in one graph
  • Includes a recommended project layout and per-scope /graphify invocation examples

Why this matters

OKF is a lightweight knowledge structuring standard (Google Cloud Platform, MIT licence). Teams adopting both tools need to know how to keep their code graph clean without losing their documentation graph.

🤖 Generated with Claude Code

… clutter

OKF (Open Knowledge Format) places index.md bundle manifests inside
subdirectories. Without filtering, Graphify picks these up as graph
nodes, mixing documentation metadata into the code graph.

This guide covers three options:
- .graphifyignore to isolate a dedicated OKF folder
- --ast-only mode when index.md files are scattered alongside code
- intentional inclusion when you want docs and code in one graph

Also includes a recommended project layout and per-scope /graphify
invocation examples.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant