Building a Markdig Extension for DocFX: Remote Content Inclusion with AI Rewriting

May 22, 2026 · 10:35 PM UTC ·4 min read · 0 reactions · 0 comments · 35 views

#ai #dotnet #opensource #documentation #Microsoft #DocFX #Markdig

TL;DR · WeSearch summary

A new Markdig extension called docfx-remote-include has been developed to enhance DocFX by allowing remote content inclusion. This tool enables documentation teams to fetch and inline content from various sources without duplicating it. The extension also incorporates AI capabilities for content adaptation, ensuring that the integrated material matches the surrounding documentation style.

Key facts

▪DocFX is an open-source documentation generator by Microsoft that traditionally does not support remote content inclusion.
▪The docfx-remote-include extension allows users to fetch markdown content from remote sources during the build process.
▪It includes AI features that can rewrite fetched content to match the tone and style of the surrounding documentation.

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	DEV.to (Top)
Canonical URL	https://dev.to/saipramod/building-a-markdig-extension-for-docfx-remote-content-inclusion-with-ai-rewriting-hb7
Publication time	Fri, 22 May 2026 22:35:09 +0000
Retrieval time	2026-05-22T23:02:03.354Z
Last seen	2026-05-22T23:02:03.354Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	5Z9LAGXZAz5n
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3946841) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } sai pramod Posted on May 22 Building a Markdig Extension for DocFX: Remote Content Inclusion with AI Rewriting #ai #dotnet #opensource #markdig The Problem Every Documentation Team Hits If you've worked on a documentation platform at any scale, you've hit this problem: content lives in multiple places, and you need to compose it into a single, coherent site at build time. Maybe your API reference is generated from code. Maybe your troubleshooting guides live in a separate service.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments