feat: redesign archgw -> plano + website in Next.js (#613)

* feat: redesign archgw -> plano + website

* feat(www): refactor landing page sections, add new diagrams and UI improvements

* feat(www): sections enhanced for clarify & diagrams added

* feat(www): improvements to mobile design, layout of diagrams

* feat(www): clean + typecheck

* feat(www): feedback loop changes

* feat(www): fix type error

* fix lib/utils error

* feat(www): ran biome formatting

* feat(www): graphic changes

* feat(www): web analytics

* fea(www): changes

* feat(www): introduce monorepo

This change brings Turborepo monorepo to independently handle the marketing website, the docs website and any other future use cases for mutli-platform support. They are using internal @katanemo package handlers for the design system and logic.

* fix(www): transpiler failure

* fix(www): tsconfig issue

* fix(www): next.config issue

* feat(docs): hold off on docs

* Delete next.config.ts

* feat(www): content fix

* feat(www): introduce blog

* feat(www): content changes

* Update package-lock.json

* feat: update text

* Update IntroSection.tsx

* feat: Turbopack issue

* fix

* Update IntroSection.tsx

* feat: updated Research page

* refactor(www): text clarity, padding adj.

* format(www)

* fix: add missing lib/ files to git - fixes Vercel GitHub deployment

- Updated .gitignore to properly exclude Python lib/ but include Next.js lib/ directories
- Added packages/ui/src/lib/utils.ts (cn utility function)
- Added apps/www/src/lib/sanity.ts (Sanity client configuration)
- Fixes module resolution errors in Vercel GitHub deployments (case-sensitive filesystem)

* Update .gitignore

* style(www): favicon + metadata

* fix(www): links

* fix(www): add analytics

* fix(www): add

* fix(www): fix links + image

* fix(www): fix links + image

* fix(www): fix links

* fix(www): remove from tools testing.md

apps/www/src/data/diagrams-programmatic.ts

@@ -0,0 +1,82 @@
+/**
+ * Programmatic ASCII Diagram Builder
+ *
+ * For non-coders: Define your diagram structure with simple objects,
+ * and the system will automatically generate the ASCII art.
+ */
+
+interface DiagramStep {
+  id: string;
+  label: string;
+  type: "input" | "inner" | "regular";
+  position: { x: number; y: number };
+}
+
+interface DiagramFlow {
+  from: string;
+  to: string;
+  arrow: "right" | "down" | "left" | "up";
+  label?: string;
+}
+
+interface DiagramConfig {
+  title: string;
+  steps: DiagramStep[];
+  flows: DiagramFlow[];
+}
+
+// Example: Define diagram using simple objects
+export const myFlow: DiagramConfig = {
+  title: "User Registration Flow",
+  steps: [
+    { id: "start", label: "User", type: "input", position: { x: 0, y: 0 } },
+    {
+      id: "step1",
+      label: "Validate Email",
+      type: "inner",
+      position: { x: 2, y: 0 },
+    },
+    {
+      id: "step2",
+      label: "Create Account",
+      type: "regular",
+      position: { x: 2, y: 1 },
+    },
+    {
+      id: "step3",
+      label: "Send Welcome",
+      type: "regular",
+      position: { x: 2, y: 2 },
+    },
+  ],
+  flows: [
+    { from: "start", to: "step1", arrow: "right" },
+    { from: "step1", to: "step2", arrow: "down" },
+    { from: "step2", to: "step3", arrow: "down" },
+  ],
+};
+
+/**
+ * Convert diagram config to ASCII string
+ *
+ * Usage:
+ * import { buildDiagram } from './ascii-builder';
+ * const ascii = buildDiagram(myFlow);
+ */
+export const buildDiagram = (config: DiagramConfig): string => {
+  // This function would programmatically build the ASCII
+  // For now, return a placeholder
+  let result = "";
+  result += `╔═ ${config.title} ══╗\n`;
+  result += `║ Placeholder for programmatic generation ║\n`;
+  result += `╚════════════════════════════════════╝\n`;
+
+  // TODO: Implement automatic ASCII generation from config
+  // This would:
+  // 1. Layout boxes based on positions
+  // 2. Add arrows based on flows
+  // 3. Add shadows automatically
+  // 4. Handle different box types
+
+  return result;
+};