feat: add doc for headers

docs/getting_started/configuration.mdx

@@ -25,29 +25,36 @@ schema
 }
 
 type Query {
-  # Specify the http path for the users query
-  users: [User] @http(path: "/users")
+
+# Specify the http path for the users query
+
+users: [User] @http(path: "/users")
 }
 
 # Create a user type with the fields returned by the users api
+
 type User {
-  id: Int!
-  name: String!
-  username: String!
-  email: String!
-
-  # Extend the user type with the posts field
-  # Use the current user's id to construct the path
-  posts: [Post] @http(path: "/users/{{value.id}}/posts")
+id: Int!
+name: String!
+username: String!
+email: String!
+
+# Extend the user type with the posts field
+
+# Use the current user's id to construct the path
+
+posts: [Post] @http(path: "/users/{{value.id}}/posts")
 }
 
 # Create a post type with the fields returned by the posts api
+
 type Post {
-  id: Int!
-  title: String!
-  body: String!
+id: Int!
+title: String!
+body: String!
 }
-```
+
+````
 
 </TabItem>
 <TabItem value="yml" label="yml">
@@ -109,7 +116,7 @@ types:
         required: true
       website:
         type: String
-```
+````
 
 </TabItem>
 <TabItem value="json" label="json">

docs/getting_started/installation.mdx

@@ -9,7 +9,11 @@ import Version from "../../src/components/Version"
 import InstallCommand from "../../src/components/install"
 
 <>
-  You can install the latest version - <b><Version /></b>, by using<b> NPM</b>.
+  You can install the latest version -{" "}
+  <b>
+    <Version />
+  </b>
+  , by using<b> NPM</b>.
 </>
 ## NPM
 

docs/guides/http-cache.md

@@ -32,12 +32,12 @@ This configuration instructs Tailcall to cache responses from the designated ups
 
 ### Cache-Control headers in responses
 
-Enabling the `cacheControlHeader` setting in Tailcall ensures that [Cache-Control] headers are included in the responses returned to clients. When activated, Tailcall dynamically sets the `max-age` directive in the `Cache-Control` header to the minimum `max-age` value encountered in any of the responses from upstream services. This approach guarantees that the caching duration for the composite response is conservative, aligning with the shortest cache validity period provided by the upstream services. By default, this feature is disabled (`false`), meaning Tailcall will not modify or add `Cache-Control` headers unless explicitly instructed to do so. This setting is distinct from the general HTTP cache setting, which controls whether responses are cached internally by Tailcall; `cacheControlHeader` specifically controls the caching instructions sent to clients.
+Enabling the `cacheControl` setting in Tailcall ensures that [Cache-Control] headers are included in the responses returned to clients. When activated, Tailcall dynamically sets the `max-age` directive in the `Cache-Control` header to the minimum `max-age` value encountered in any of the responses from upstream services. This approach guarantees that the caching duration for the composite response is conservative, aligning with the shortest cache validity period provided by the upstream services. By default, this feature is disabled (`false`), meaning Tailcall will not modify or add `Cache-Control` headers unless explicitly instructed to do so. This setting is distinct from the general HTTP cache setting, which controls whether responses are cached internally by Tailcall; `cacheControl` specifically controls the caching instructions sent to clients.
 
-Here is how you can enable the `cacheControlHeader` setting within your Tailcall schema to apply these caching instructions:
+Here is how you can enable the `cacheControl` setting within your Tailcall schema to apply these caching instructions:
 
 ```graphql
-schema @server(cacheControlHeader: true) {
+schema @server(headers: {cacheControl: true}) {
   query: Query
   mutation: Mutation
 }
@@ -47,7 +47,7 @@ schema @server(cacheControlHeader: true) {
 
 ### Best Practices for Enhancing REST API Performance with Tailcall
 
-The combination of `httpCache` and `cacheControlHeader` provides a comprehensive caching solution. While `httpCache` focuses on internal caching to reduce the impact of high latency and frequent requests, `cacheControlHeader` manages client-side caching policies, ensuring an optimal balance between performance, data freshness, and efficient resource use.
+The combination of `httpCache` and `cacheControl` provides a comprehensive caching solution. While `httpCache` focuses on internal caching to reduce the impact of high latency and frequent requests, `cacheControl` manages client-side caching policies, ensuring an optimal balance between performance, data freshness, and efficient resource use.
 
 These caching primitives are beneficial for REST APIs that are latency-sensitive, have a high rate of request repetition, or come with explicit caching headers indicating cacheable responses. Together, they tackle the common challenges of optimizing REST API performance by minimizing unnecessary network traffic and server load while ensuring response accuracy.
 

docs/operators/server.md

@@ -45,14 +45,18 @@ This example sets the `port` to `8090`, making Tailcall accessible at `http://lo
 Always choose non-standard ports, avoiding typical ones like 80 or 8080. Make sure your chosen port is free.
 :::
 
-## cacheControlHeader
+## headers
 
-Activating the `cacheControlHeader` configuration directs Tailcall to send [Cache-Control] headers in its responses. The `max-age` value in the header matches the smallest of the values in the responses Tailcall receives from upstream services. By default, this is `false`, which means Tailcall does not set any header.
+Allows intelligent configuration of the final response headers that's produced by Tailcall.
+
+### cacheControl
+
+Activating the `cacheControl` configuration directs Tailcall to send [Cache-Control] headers in its responses. The `max-age` value in the header matches the smallest of the values in the responses Tailcall receives from upstream services. By default, this is `false`, which means Tailcall does not set any header.
 
 [cache-control]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control
 
 ```graphql showLineNumbers
-schema @server(cacheControlHeader: true) {
+schema @server(headers: {cacheControl: true}) {
   query: Query
   mutation: Mutation
 }

src/css/custom.css

@@ -389,8 +389,9 @@ aside.theme-doc-sidebar-container {
   width: 100%;
 }
 
-pre code, code {
-  font-family: var(--ifm-font-family-monospace) !important;  
+pre code,
+code {
+  font-family: var(--ifm-font-family-monospace) !important;
 }
 
 nav.menu {