docs: add showcase

docs/guides/playground.md

@@ -0,0 +1,42 @@
+---
+title: "Playground"
+description: "Explore and test server configurations with @server directive's showcase feature in a controlled environment. Ideal for quick experimentation and learning with dynamic GraphQL schema configurations. Not recommended for production due to performance and security considerations."
+---
+
+The `@server` directive's `showcase` option allows for hands-on experimentation with server configurations in a controlled environment. This feature simplifies the process of exploring and testing different settings. This enables experimenting with random configurations hosted, without the need to restart the server or affect existing setups.
+
+#### Example Usage
+
+```graphql showLineNumbers
+schema @server(showcase: true, graphiql: true) {
+  query: Query
+}
+
+type User {
+  notId: Int
+  notName: String
+}
+
+type Query {
+  notUser: User
+    @http(
+      path: "/users/1"
+      baseURL: "http://jsonplaceholder.typicode.com"
+    )
+}
+```
+
+To test it out, append `/showcase/graphql?config=YOUR_CONFIG_URL` to your GraphQL base URL when querying the data.
+
+![Showcase](/images/docs/showcase.png)
+
+The above example shows loading a schema file from Tailcall's Github repository [examples](https://github.com/tailcallhq/tailcall/tree/main/examples) and querying it.
+
+## Performance and Security
+
+- **Performance Impact**: The `showcase` feature prioritizes flexibility and ease of testing over speed, leading to slower response times due to the overhead of dynamically applied configurations.
+- **Security Risk**: There's a potential security risk as it may allow unauthorized access to files and environment variables.
+
+:::important
+Due to these concerns, this mode is **not recommended** for production environments.
+:::

docs/operators/link.md

@@ -1,5 +1,6 @@
 ---
 title: "@link"
+description: "Discover how the @link operator can transform your GraphQL schema, enabling seamless integration of external resources like configurations, .proto files, and SSL/TLS certificates for enhanced functionality and security. Learn to streamline and secure your GraphQL configurations with our comprehensive guide."
 ---
 
 The **@link** operator is used for bringing external resources into your GraphQL schema. It makes it easier to include configurations, .proto files for gRPC services, and other files into your schema. With this operator, external resources are either merged with or used effectively in the importing configuration.

docs/operators/server.md

@@ -235,6 +235,16 @@ schema @server(key: "./key.pem") {
 The key can be of any extension, but it's highly recommended to use standards (`pem`, `crt`, `key`).
 :::
 
+### showcase
+
+The `@server` directive's `showcase` option allows for hands-on experimentation with server configurations in a controlled environment. This feature simplifies the process of exploring and testing different settings.
+
+```graphql showLineNumbers
+schema @server(showcase: true) {
+  query: Query
+}
+```
+
 ## batchRequests
 
 Batching in GraphQL combines requests into one, reducing server round trips.