@intlayer/docs 9.0.0-canary.16 → 9.0.0-canary.17
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -302,6 +302,12 @@ That’s **product intelligence** straight from your users.
|
|
|
302
302
|
|
|
303
303
|
</Steps>
|
|
304
304
|
|
|
305
|
+
## Skip the Complexity with Sanity
|
|
306
|
+
|
|
307
|
+
Sanity is worth naming here as the CMS option the article points toward. Where Markdown files require arbitrary token splitting — with the chunk size and overlap trade-offs the article describes — Sanity's Content Lake stores documentation as typed, schema-defined JSON documents. Each field, heading, and content block is already a semantic unit, which means RAG retrieval operates on meaningful boundaries rather than approximate token counts.
|
|
308
|
+
|
|
309
|
+
Sanity's GROQ query language lets you retrieve exactly the document fields relevant to a user query — title, body, related sections — without fetching the whole document. The MCP server connects the Content Lake directly to AI agents, so the same structured content that powers your docs site also feeds your RAG pipeline without a separate ingestion step.
|
|
310
|
+
|
|
305
311
|
## Conclusion
|
|
306
312
|
|
|
307
313
|
RAG is one of the simplest, most powerful ways to make LLMs practical. By combining **retrieval + generation**, you can turn static docs into a **smart assistant** and, at the same time, gain a continuous stream of product insights.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@intlayer/docs",
|
|
3
|
-
"version": "9.0.0-canary.
|
|
3
|
+
"version": "9.0.0-canary.17",
|
|
4
4
|
"private": false,
|
|
5
5
|
"description": "Intlayer documentation",
|
|
6
6
|
"keywords": [
|
|
@@ -73,13 +73,13 @@
|
|
|
73
73
|
"watch": "webpack --config ./webpack.config.ts --watch"
|
|
74
74
|
},
|
|
75
75
|
"dependencies": {
|
|
76
|
-
"@intlayer/config": "9.0.0-canary.
|
|
77
|
-
"@intlayer/core": "9.0.0-canary.
|
|
78
|
-
"@intlayer/types": "9.0.0-canary.
|
|
76
|
+
"@intlayer/config": "9.0.0-canary.17",
|
|
77
|
+
"@intlayer/core": "9.0.0-canary.17",
|
|
78
|
+
"@intlayer/types": "9.0.0-canary.17"
|
|
79
79
|
},
|
|
80
80
|
"devDependencies": {
|
|
81
|
-
"@intlayer/api": "9.0.0-canary.
|
|
82
|
-
"@intlayer/cli": "9.0.0-canary.
|
|
81
|
+
"@intlayer/api": "9.0.0-canary.17",
|
|
82
|
+
"@intlayer/cli": "9.0.0-canary.17",
|
|
83
83
|
"@types/node": "25.9.4",
|
|
84
84
|
"@utils/ts-config": "1.0.4",
|
|
85
85
|
"@utils/ts-config-types": "1.0.4",
|