update intro

ibishal · Feb 28, 2024 · ce4af35 · ce4af35
1 parent 384f5b5
commit ce4af35
Show file tree

Hide file tree

Showing 6 changed files with 15 additions and 58 deletions.
diff --git a/docs/getting_started/installation.mdx b/docs/getting_started/installation.mdx
@@ -1,6 +1,6 @@
 ---
 title: Installation
-sidebar_position: 1
+sidebar_position: 2
 slug: /getting_started
 ---
 

diff --git a/docs/getting_started/introduction.md b/docs/getting_started/introduction.md
@@ -0,0 +1,13 @@
+---
+title: Introduction
+sidebar_position: 1
+slug: /
+---
+
+Good APIs craft a broad spectrum of functionalities. Yet, the broader their scope, the more they diverge from being the perfect fit for any specific use case. This fundamental discrepancy — the impedance mismatch between the general capabilities of an API and the precise needs of a particular scenario — amplifies the necessity for an orchestration layer. Such a layer adeptly bridges this gap, tailor-fitting generic APIs to meet exact requirements with finesse. Tailcall stands at the forefront of this innovation, seamlessly transforming the way APIs are integrated and interacted with.
+
+Tailcall introduces a robust DSL (Domain-Specific Language), enabling developers to fine-tune how APIs are orchestrated. This DSL facilitates specifying different caching and batching strategies to enhance the system's efficiency. It also enables precise governance and access control mechanisms. Tailcall serves as a central hub for team collaboration, offering a unified point for managing all APIs, documentation, and more. Once configured, it positions itself between the clients and microservices, adeptly managing all requests and orchestrating them as needed.
+
+![Architecture Diagram](/images/docs/architecture.png)
+
+Manually crafting BFF (Backend for Frontend) layers has become outdated. With Tailcall, API orchestration evolves into a streamlined and highly optimized process. It functions as an essential intermediary, intelligently directing requests and assembling responses from each microservice. This approach diminishes the development burden associated with traditional BFF layers but also bolsters performance, reliability, and scalability throughout the application infrastructure.
diff --git a/docs/guides/context.md b/docs/guides/context.md
@@ -91,4 +91,4 @@ type Query {
 
 Here, `headers.userId` refers to a header called `userId` that should be present in the `context`. The server can use this `userId` to fetch comments for the specified user.
 
-[operator]: /docs/intro/operators
+[operator]: /docs/operators
diff --git a/docs/intro/_category_.json b/docs/intro/_category_.json
diff --git a/docs/intro/introduction.md b/docs/intro/introduction.md
diff --git a/static/images/docs/architecture.png b/static/images/docs/architecture.png
Original file line number	Diff line number	Diff line change
Expand Up		@@ -91,4 +91,4 @@ type Query {

		Here, `headers.userId` refers to a header called `userId` that should be present in the `context`. The server can use this `userId` to fetch comments for the specified user.

		[operator]: /docs/intro/operators
		[operator]: /docs/operators