feat: createHonoRouter to core pkg

Author: GuptaSiddhant

apps/website/docs/aws/index.md

@@ -12,7 +12,9 @@ npm i @storybooker/aws
 
 ### Hosting
 
-- [AWS Lambda + API Gateway](lambda)
+Refer Hono docs for deployment instructions: https://hono.dev/docs/getting-started/aws-lambda
+
+The hono app-router should be created using the `createHonoRouter` function from the [`@storybooker/core`](../core) package.
 
 ### Database
 

apps/website/docs/aws/lambda.md

@@ -5,23 +5,22 @@ tags:
 
 # Bun
 
-Run following with `bun server.ts`
+Run following with `bun run --hot server.ts`
+
+> Refer Hono docs: https://hono.dev/docs/getting-started/bun
 
 ```ts
 // server.ts
 
-import {
-  createRequestHandler,
-  type RequestHandlerOptions,
-} from "@storybooker/core";
+import { createHonoRouter } from "@storybooker/core";
 import {
   LocalFileDatabase,
   LocalFileStorage,
 } from "@storybooker/core/adapters";
 import { createBasicUIAdapter } from "@storybooker/ui";
 
-// Create StoryBooker router handler
-const handler = createRequestHandler({
+// Create StoryBooker router
+const router = createHonoRouter({
   // provide a supported database service adapter
   database: new LocalFileDatabase(),
   // provide a supported storage service adapter
@@ -30,5 +29,8 @@ const handler = createRequestHandler({
   ui: createBasicUIAdapter(),
 });
 
-Bun.serve({ fetch: handler });
+export default {
+  fetch: router.fetch,
+  port: 8000,
+};
 ```

apps/website/docs/core/bun.md

@@ -9,21 +9,20 @@ Run following with `deno serve -REW server.ts`
 
 > Note: You can change permissions based on your adapter choice.
 
+> Refer Hono docs: https://hono.dev/docs/getting-started/deno
+
 ```ts
 // server.ts
 
-import {
-  createRequestHandler,
-  type RequestHandlerOptions,
-} from "npm:@storybooker/core";
+import { createHonoRouter } from "jsr:@storybooker/core";
 import {
   LocalFileDatabase,
   LocalFileStorage,
-} from "npm:@storybooker/core/adapters";
+} from "jsr:@storybooker/core/adapters";
 import { createBasicUIAdapter } from "npm:@storybooker/ui";
 
-// Create StoryBooker router handler
-const handler = createRequestHandler({
+// Create StoryBooker router
+const router = createHonoRouter({
   // provide a supported database service adapter
   database: new LocalFileDatabase(),
   // provide a supported storage service adapter
@@ -32,5 +31,5 @@ const handler = createRequestHandler({
   ui: createBasicUIAdapter(),
 });
 
-export default { fetch: handler };
+export default router;
 ```

apps/website/docs/core/deno.md

@@ -17,15 +17,15 @@ npm i @storybooker/core
 
 ## API
 
-### `createRequestHandler`
+### `createHonoRouter`
 
-> [API Docs](https://jsr.io/@storybooker/core/doc/~/createRequestHandler)
+> [API Docs](https://jsr.io/@storybooker/core/doc/~/createHonoRouter)
 
-Callback to create a request-handler based on provided options.
+Callback to create a Hono router that can be used as a request handler.
 
-The request handler takes Standard Request and returns a Response asynchronously.
+The Hono router can be deployed to any platform that supports Hono framework.
 
-[Read more about options](./request-options)
+[Read more about options](./router-options)
 
 ### `createPurgeHandler`
 
@@ -56,3 +56,4 @@ A simple storage adapter that uses local folder to store files. Defaults to curr
 - [NodeJS](node)
 - [Deno](deno)
 - [Bun](bun)
+- Others: Refer [Hono docs](https://hono.dev/docs/getting-started/basic)

apps/website/docs/core/index.md

@@ -6,23 +6,24 @@ tags:
 
 # NodeJS
 
+> Refer Hono docs: https://hono.dev/docs/getting-started/nodejs
+
 Run following with `node server.mjs`
 
 ```js
 // @ts-check
 // server.mjs
 
-import { createServer } from "node:http";
-import { createRequestListener } from "@remix-run/node-fetch-server";
-import { createRequestHandler } from "@storybooker/core";
+import { serve } from "@hono/node-server";
+import { createHonoRouter } from "@storybooker/core";
 import {
   LocalFileDatabase,
   LocalFileStorage,
 } from "@storybooker/core/adapters";
 import { createBasicUIAdapter } from "npm:@storybooker/ui";
 
-// Create StoryBooker router handler
-const handler = createRequestHandler({
+// Create StoryBooker Hono router
+const router = createHonoRouter({
   // provide a supported database service adapter
   database: new LocalFileDatabase(),
   // provide a supported storage service adapter
@@ -31,10 +32,6 @@ const handler = createRequestHandler({
   ui: createBasicUIAdapter(),
 });
 
-// Create a standard Node.js server
-const server = createServer(createRequestListener(handler));
-
-server.listen(8000, () => {
-  console.log("Server running at http://localhost:8000");
-});
+// Create a  Node.js server
+serve(router);
 ```

apps/website/docs/core/node.md

@@ -4,9 +4,9 @@ tags:
   - api
 ---
 
-# Request Handler Options
+# Router Options
 
-When creating a request handler using `createRequestHandler` (or a wrapper like `registerStoryBookerRouter` in Azure), you have to pass an options object which contain various service adapters and other options.
+When creating a request handler using `createHonoRouter` (or a wrapper like `registerStoryBookerRouter` in Azure), you have to pass an options object which contain various service adapters and other options.
 
 ```ts
 {
@@ -30,3 +30,21 @@ When creating a request handler using `createRequestHandler` (or a wrapper like
   config?: RequestHandlerConfigOptions;
 }
 ```
+
+## Config Options
+
+The `config` object can contain additional custom options to be passed to the request handler. Some of the common options include:
+
+### Middlewares
+
+You can pass an array of middlewares to be used by the request handler. These middlewares should be compatible with the Hono framework.
+
+```ts
+import { logger } from "hono/logger";
+
+const config = {
+  middlewares: [logger()],
+};
+```
+
+Any middlewares provided by Hono can also be used here. Refer to the [Hono documentation](https://hono.dev/docs/guides/middleware) for more details.

apps/website/docs/core/request-options.md apps/website/docs/core/router-options.mdapps/website/docs/core/request-options.md renamed to apps/website/docs/core/router-options.md

@@ -12,9 +12,9 @@ npm i @storybooker/gcp
 
 ### Hosting
 
-Currently no hosting adapter available for GCP. Though you can use GCP's App Engine or Cloud Run to host your StoryBooker application.
+Refer Hono docs for deployment instructions: https://hono.dev/docs/getting-started/google-cloud-run
 
-To convert Express app request and response to StoryBooker compatible request and response, you can use the [`@remix-run/node-fetch-server`](https://npm.im/@remix-run/node-fetch-server) package with [`@storybooker/core`](../core).
+The hono app-router should be created using the `createHonoRouter` function from the [`@storybooker/core`](../core) package.
 
 ### Database
 

apps/website/docs/gcp/index.md

@@ -14,7 +14,7 @@ StoryBooker is composed of 3 main parts:
 
 The router is the core of StoryBooker. It is responsible for routing requests to the page/api and using the appropriate adapter to render the response.
 
-The entire router is maintained in the [`@storybooker/core`](./core) package. The package is used to create a router-handler that takes a WebRequest and returns a WebResponse. The router is framework agnostic and can be used in any server environment that supports NodeJS api (NodeJS, Deno, Bun, etc.).
+The entire router is maintained in the [`@storybooker/core`](./core) package. The package is used to create a Hono app-router. The router is framework agnostic and can be used in any server environment that supports NodeJS api (NodeJS, Deno, Bun, etc.).
 
 ## Adapters
 
@@ -24,10 +24,11 @@ The adapters are maintained in their respective packages and can be mixed and ma
 
 The Adapters implement following services:
 
-- Hosting: Responsible for serving the StoryBooker application. Examples: Azure Functions, AWS Lambda, etc.
 - Storage: Responsible for storing StoryBooker assets. Examples: Azure Blob Storage, AWS S3, etc.
 - Database: Responsible for managing StoryBooker data. Examples: Azure CosmosDB, AWS DynamoDB, etc.
 - Auth: Responsible for authenticating users. Examples: Azure EasyAuth, etc.
+- Logger: Responsible for logging events and errors. Examples: Azure Application Insights, AWS CloudWatch, etc.
+- UI: Responsible for providing HTML UI for GET routes. Without it, the service is headless only.
 
 ## CLI
 

apps/website/docs/index.md

@@ -0,0 +1,3 @@
+{
+  "label": "Redis"
+}