Switch to custom domain agents.siddhantkhare.com

- Update site URL and remove /agentic-engineering-guide base path
- Add CNAME file for GitHub Pages
- Fix font paths and image paths to use root-relative URLs

Co-authored-by: Ona <no-reply@ona.com>

Author: Siddhant-K-code

astro.config.mjs

@@ -4,8 +4,8 @@ import sitemap from "@astrojs/sitemap";
 import tailwindcss from "@tailwindcss/vite";
 
 export default defineConfig({
-  site: "https://siddhant-k-code.github.io",
-  base: "/agentic-engineering-guide",
+  site: "https://agents.siddhantkhare.com",
+  base: "/",
   integrations: [mdx(), sitemap()],
   vite: {
     plugins: [tailwindcss()],

public/CNAME

@@ -0,0 +1 @@
+agents.siddhantkhare.com

src/content/chapters/05-context-engineering-stack.mdx

@@ -17,7 +17,7 @@ implement retrieval (getting chunks from a vector database) and skip the
 post-retrieval processing that determines whether those chunks actually
 help the model.
 
-![](/agentic-engineering-guide/images/fig-context-stack.png) 
+![](/images/fig-context-stack.png) 
 
 ## Layer 1: Clustering
 When you retrieve 10 chunks from a vector database, they often contain

src/content/chapters/07-agent-security-crisis.mdx

@@ -65,7 +65,7 @@ the way you validate structured API inputs.
 The agent threat model has three primary attack vectors. Understanding
 them is essential because they require fundamentally different defenses.
 
-![](/agentic-engineering-guide/images/fig-threat-model-sketch.png) 
+![](/images/fig-threat-model-sketch.png) 
 
 ### Vector 1: Prompt injection
 Prompt injection occurs when malicious instructions are embedded in data

src/content/chapters/13-agents-md-onboarding.mdx

@@ -316,7 +316,7 @@ of your project. Skills provide the "how" - the domain expertise for
 doing things well. MCP provides the "what" - the tools and data sources
 the agent can access at runtime. A well-configured agent has all three.
 
-![](/agentic-engineering-guide/images/fig-knowledge-stack.png) 
+![](/images/fig-knowledge-stack.png) 
 
 ### Anatomy of a skill
 A skill is a directory containing a `SKILL.md` file, hosted in a Git
@@ -361,7 +361,7 @@ request per service - a single structured record containing all relevant
 context (user identity, business data, feature flags, timing, error
 details).
 
-![](/agentic-engineering-guide/images/fig-wide-events.png) 
+![](/images/fig-wide-events.png) 
 
 With such a skill installed, agents writing new endpoints or refactoring
 existing ones would automatically apply the wide event pattern - adding

src/content/chapters/14-agent-traces.mdx

@@ -98,7 +98,7 @@ iterations, each showing what the agent decided to do and why. Within
 each iteration are the individual tool calls and LLM requests, with
 their timing, cost, and results.
 
-![](/agentic-engineering-guide/images/fig-agent-trace.png) 
+![](/images/fig-agent-trace.png) 
 
 Good trace visualization tools
 ([Jaeger](https://www.jaegertracing.io),

src/content/chapters/17-agent-loop.mdx

@@ -18,7 +18,7 @@ executes that tool, appends the result to the conversation, and sends
 everything back to the model. This continues until the model produces a
 final answer or hits a limit.
 
-![](/agentic-engineering-guide/images/fig-agent-loop.png).],
+![](/images/fig-agent-loop.png).],
 ) 
 
 The simplicity of this loop is deceptive. The engineering challenge

src/content/chapters/18-multi-agent-systems.mdx

@@ -85,7 +85,7 @@ updates docs. Pipelines are simple and predictable, but they’re slow -
 each stage must complete before the next begins - and a failure at any
 stage blocks the entire pipeline.
 
-![](/agentic-engineering-guide/images/fig-multi-agent.png) 
+![](/images/fig-multi-agent.png) 
 
 ## Task decomposition and handoffs
 The hardest part of multi-agent systems isn’t the architecture - it’s

src/content/chapters/22-agent-maturity-model.mdx

@@ -36,7 +36,7 @@ infrastructure." The gap between Level 3 and Level 4 is where most risk
 is managed - it’s the difference between "we use agents" and "we use
 agents safely."
 
-![](/agentic-engineering-guide/images/fig-maturity-model.png) 
+![](/images/fig-maturity-model.png) 
 
 ## Maturity assessment
 | Dimension | Level 1 | Level 2 | Level 3 | Level 4 | Level 5 |

src/styles/global.css

@@ -6,15 +6,15 @@
   font-style: normal;
   font-weight: 100 900;
   font-display: swap;
-  src: url("/agentic-engineering-guide/fonts/GeistVF.woff2") format("woff2");
+  src: url("/fonts/GeistVF.woff2") format("woff2");
 }
 
 @font-face {
   font-family: "Geist Mono";
   font-style: normal;
   font-weight: 100 900;
   font-display: swap;
-  src: url("/agentic-engineering-guide/fonts/GeistMonoVF.woff2") format("woff2");
+  src: url("/fonts/GeistMonoVF.woff2") format("woff2");
 }
 
 /* ── Design tokens ── */