Keppi Graph: Navigating Your Notes Through Structured Connections

Written by

in

How to Auto-Generate Wiki Links with Keppi Maintaining an internal knowledge base or project wiki is a notorious bottleneck for scaling teams. As documentation grows, manual cross-referencing fails, resulting in isolated “knowledge silos” and outdated pages.

Keppi solves this problem by using artificial intelligence to analyze your documentation structure and automatically generate bidirectional wiki links across your entire workspace. This guide outlines how to configure Keppi to index your files, auto-generate markdown hyperlinks, and keep your documentation connected. Why Auto-Generating Wiki Links Matters

Manual documentation management forces creators to remember every relevant page that already exists when writing new content. Auto-generating these connections via Keppi offers several advantages:

Eliminates Dead Ends: Automatically maps orphan pages to relevant hub topics.

Contextual Discovery: Surfaces related internal documents for readers without forcing manual searches.

Enforces a Dynamic Knowledge Graph: Calculates concept relationships based on shared keywords and document structural affinities.

Saves Engineering Hours: Keeps documentation maintained programmatically without developer intervention. Step 1: Install and Initialize Keppi

To begin auto-linking your files, you need to install Keppi and point it toward your local documentation folder or connected cloud repository.

Download the Keppi CLI or log into your Keppi cloud interface. Initialize your workspace by running the setup wizard: keppi init –dir ./your-docs-folder Use code with caution.

Configure your AI model provider (such as OpenAI, Anthropic, or a local LLM instance) by adding your API keys to the newly created .keppirc configuration file. Step 2: Configure Your Linking Rules

Keppi allows you to customize how aggressively it connects text strings to existing wiki articles. Open your workspace settings file to tune the linking behavior:

{ “autolink”: { “enabled”: true, “format”: “markdown”, “match_case”: false, “min_word_length”: 4, “exclude_folders”: [“/templates”, “/drafts”] } } Use code with caution.

Format Options: Choose between traditional Markdown links Title or internal WikiLinks [[Title]] based on your platform (e.g., Obsidian, Notion, GitHub Wiki, or DokuWiki).

Exclusions: Specify directories containing scratchpads or archives that the engine should ignore to avoid generating redundant links. Step 3: Run the Keppi Indexer

Before Keppi can link your documents, it needs to analyze your workspace to understand your core entities, glossary terms, and project architecture. Run the ingestion pipeline: keppi ingest Use code with caution.

During this phase, Keppi reads your source files, creates internal embeddings, and registers all page titles and major subheadings as “target destinations.” It builds a local index mapping out how different concepts naturally overlap. Step 4: Execute the Auto-Link Command

Once your index is populated, you can trigger Keppi to scan the text inside your documents and automatically insert hyperlinks wherever a registered keyword or topic is mentioned. Execute the following command to update your files: keppi link –apply Use code with caution. What Happens Behind the Scenes?

Text Analysis: Keppi reads through raw Markdown paragraphs to isolate key phrases.

Context Verification: The AI distinguishes between generic words and specific project entities to avoid over-linking common terms.

Link Insertion: Keppi injects the formatted links directly into the source file without disrupting your existing formatting or text layouts.

Bidirectional Updates: If Page A links to Page B, Keppi flags the relationship, allowing frontend wiki tools to render backlink networks seamlessly. Step 5: Automate with CI/CD

To make sure your wiki stays continuously updated without human intervention, integrate Keppi directly into your continuous integration workflow (like GitHub Actions or GitLab CI).

Add this step to your deployment pipeline to check and auto-link documents on every pull request:

- name: Auto-Generate Wiki Links with Keppi run: | keppi ingest keppi link –apply - name: Commit Updated Documentation uses: stefanzweifel/git-auto-commit-action@v5 with: commit_message: “docs: automatic wiki cross-linking by Keppi” Use code with caution.

This automation ensures that whenever a team member adds a new document or updates a feature guide, all existing references throughout the wiki adapt and link to the new asset immediately. If you want to optimize your configuration, let me know:

Which wiki platform or markdown parser you use (e.g., Obsidian, GitHub, DokuWiki). The approximate size of your documentation repository.

Whether you prefer strict keyword matching or AI-driven semantic linking.

I can provide a tailored script or config file for your specific setup! Saved time Comprehensive Inappropriate Not working

A copy of this chat, including the images and video, will be included with your feedback A copy of this chat will be included with your feedback

Your feedback will include a copy of this chat and the image from your search

Your feedback will include a copy of this chat, any links you shared, and the image from your search.

Thanks for letting us know

Google may use account and system data to understand your feedback and improve our services, subject to our Privacy Policy and Terms of Service. For legal issues, make a legal removal request.