# Building an LSP for your docs

DevFeed: [Building an LSP for your docs](<https://devfeed.tech/articles/building-an-lsp-for-your-docs-30994.md>)

Original publisher: [Read original article](<https://www.mintlify.com/blog/building-an-lsp-for-your-docs-by-overcoming-vercel>)

Author: Ricardo Nunez

Published: 2025-10-23T00:00:00Z

Content type: article

Language: en

Sources: [Mintlify Blog](<https://devfeed.tech/sources/mintlify-blog.md>)

Topics: [Documentation](<https://devfeed.tech/topics/documentation.md>), [TypeScript](<https://devfeed.tech/topics/typescript.md>), [Library](<https://devfeed.tech/topics/library.md>), [ide](<https://devfeed.tech/topics/ide.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [docs](<https://devfeed.tech/tags/docs.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [ide](<https://devfeed.tech/tags/ide.md>), [library](<https://devfeed.tech/tags/library.md>), [typescript](<https://devfeed.tech/tags/typescript.md>)

## AI overview

This engineering article explains how to add an IDE-like experience to documentation code examples using Twoslash. It describes Twoslash's in-memory TypeScript project and its use of language services to provide type information on hover.

## Source excerpt

Adding an IDE experience to codeblocks in your docs is one of the issues that comes up often for people looking to add more context to code snippets. It's not a deal-breaker, but it can make your docs feel more connected to the functions and methods you're documenting.