Skip to content

Commit

Permalink
website: update home page
Browse files Browse the repository at this point in the history
  • Loading branch information
tusharmath committed Feb 9, 2024
1 parent 7fe05c5 commit c4d639a
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 7 deletions.
6 changes: 3 additions & 3 deletions src/components/home/Configuration.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,8 @@ const Configuration = (): JSX.Element => {
Get <span className="rounded-lg px-SPACE_02 bg-tailCall-yellow">Started</span>
</Heading>
<p className="text-content-small sm:text-content-medium mb-SPACE_11">
Setup the Tailcall via npm to build high-performance <b>GraphQL</b> APIs on top of existing REST endpoints. To
dive deeper into TailCall checkout our <Link href="/docs">docs</Link> for detailed tutorials and guides.
Setup Tailcall via npm to build a high-performance <b>GraphQL API</b> on top of existing REST endpoints.
Checkout our <Link href="/docs">docs</Link> for detailed tutorials and guides.
</p>
</div>
<div>
Expand Down Expand Up @@ -44,7 +44,7 @@ type Post {
title: String!
body: String!
userId: Int!
# Expand a post with user information
user: User @http(path: "/users/{{value.userId}}")
}
Expand Down
9 changes: 5 additions & 4 deletions src/components/home/LegacyGateway.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -21,10 +21,11 @@ const LegacyGateway = (): JSX.Element => {
</Heading>

<p className="text-content-tiny font-normal sm:text-content-small lg:text-content-medium text-tailCall-dark-500">
A traditional API Gateway restricts operations to an API's route, method, or headers, without affecting the
request and response bodies. This limitation constrains the operations that can be performed on an API,
ultimately compelling engineering teams to either intertwine API orchestration logic with business logic or
to develop and maintain a separate layer of abstraction that helps solve this problem.
A traditional API Gateway restricts operations to an API's route, method, or headers, and doesn't allow
modifications to the request and response bodies. This limitation constrains the operations that can be
performed on an API, ultimately compelling engineering teams to either intertwine orchestration logic with
business logic or to develop and maintain a separate layer of abstraction such as BFF (backend for frontend)
that helps solve this problem .
</p>
</div>
</div>
Expand Down

0 comments on commit c4d639a

Please sign in to comment.