docs: add SEO article draft for public profile design

marketing/articles/karte/how-to-design-a-public-profile-that-answers-why-someone-should-contact-you.md

@@ -0,0 +1,107 @@
+---
+title: "How to Design a Public Profile That Answers Why Someone Should Contact You"
+slug: "how-to-design-a-public-profile-that-answers-why-someone-should-contact-you"
+target_query: "how to design a public profile that answers why someone should contact you"
+search_intent: "Learn actionable strategies for building a public profile or link-in-bio page that clearly communicates value, context, and purpose, encouraging meaningful inbound contact."
+meta_title: "Design a Public Profile That Drives Meaningful Contact | Karte"
+meta_description: "Learn how to build a public profile that goes beyond a list of links. Discover how to provide context and answer 'why' to drive better inbound connections."
+---
+
+## Outline
+
+1.  **Introduction**
+    *   The problem with standard link-in-bio pages: they provide destinations but lack context.
+    *   The goal: transitioning from a link list to a "public inbound assistant."
+2.  **Moving Beyond the Link List**
+    *   Why visitors need to know *why* they should contact you before they know *how*.
+    *   The importance of creator ownership and explicit control over public identity.
+3.  **Structuring Context: Projects and Timelines**
+    *   Using project cards to demonstrate active work and focus.
+    *   Using timeline events to establish history and credibility.
+    *   Concrete example: Differentiating "CodeVetter focus" from "Karte personal maintenance" through clear project descriptions.
+4.  **Providing Answers Before the Inbox**
+    *   The role of optional AI-generated profile modes (chat, encyclopedia, newspaper, roast).
+    *   How managed Knowledgebase memory supports contextual chat.
+    *   Why reliable, bounded fallbacks are better than fragile AI-only behavior (e.g., falling back to a deterministic public-bio answer).
+5.  **Designing for the Handoff**
+    *   Creating a clear path from discovery to a contextual inbound email or message.
+    *   The importance of protecting contact submissions (e.g., using Turnstile) to ensure quality.
+6.  **Accessibility and Reliability as Baseline Features**
+    *   Why a fast, reliable profile matters (Cloudflare Workers/OpenNext edge delivery).
+    *   Semantic landmarks, keyboard access, and reduced-motion support.
+7.  **Practical Next Action**
+    *   Review your current profile and add one specific piece of context (a project description or timeline event) that answers "why."
+8.  **Internal-Link Suggestions**
+    *   Links to related topics (e.g., configuring AI modes, managing inbound contacts).
+9.  **Source Notes (Non-Publishable)**
+    *   Repository references supporting the claims made in this article.
+
+---
+
+## Introduction
+
+A typical link-in-bio page serves a straightforward purpose: it acts as a directory. You provide a list of destinations—your social media profiles, your latest blog post, your booking calendar—and leave the visitor to navigate them. However, a directory only tells a visitor *where* they can go. It rarely tells them *why* they should go there, or more importantly, *why* they should reach out to you directly.
+
+When a public profile lacks context, the burden of discovery falls entirely on the visitor. They have to piece together your current focus, your past experience, and your preferred modes of interaction from a scattered collection of links. To encourage meaningful inbound contact, a profile must transition from a passive list of links into an active "public inbound assistant." It needs to clearly communicate value and provide the necessary context for a clean, productive handoff.
+
+## Moving Beyond the Link List
+
+The core challenge of designing an effective public profile is answering the visitor's underlying question: "Why should I contact this person?" Before a visitor clicks a "Book a Meeting" or "Send an Email" button, they need to understand how your expertise or current work aligns with their needs.
+
+This requires creator ownership and explicit control over the public identity presented. A successful profile doesn't just aggregate external platforms; it acts as the canonical source of truth for your professional or creative state. When you own the context, you control the narrative. By providing structured information directly on the profile, you reduce friction and guide the visitor toward a better-contextualized interaction.
+
+## Structuring Context: Projects and Timelines
+
+Context is built through structure. Instead of simply linking to a portfolio website, a profile should surface key elements of that portfolio directly.
+
+**Using Project Cards**
+Project cards are an effective way to demonstrate active work and current focus. They allow you to define what you are building, who it is for, and what its current status is. For instance, distinguishing between a project in "active focus" versus one in "personal maintenance mode" sets clear expectations for the visitor. If a visitor knows a project is only in maintenance, they are less likely to send an inbound request for a major feature collaboration, saving time for both parties.
+
+**Using Timeline Events**
+Similarly, timeline events establish history and credibility. While a resume lists chronological employment, a profile timeline can highlight specific milestones, shipped features, or published works. This chronological context helps a visitor understand the trajectory of your work, providing conversation starters and validating your expertise before they ever initiate contact.
+
+## Providing Answers Before the Inbox
+
+One of the most effective ways to answer "why someone should contact you" is to let them ask questions directly on the profile. Integrating optional AI-generated profile modes—such as a contextual chat—allows visitors to explore your background interactively.
+
+When a visitor can ask, "What kind of projects does this person take on?" and receive an immediate, accurate answer based on your managed Knowledgebase memory, the quality of their subsequent inbound contact improves dramatically. They arrive at your inbox with baseline questions already answered.
+
+However, it is crucial to prefer reliable, bounded fallbacks over fragile AI-only behavior. If a generative answer path fails, the profile should elegantly fall back. For example, failing over to a compact public-memory prompt, and finally to a deterministic, pre-written public-bio answer, ensures the visitor always receives useful context, rather than an empty response or an error state. Reliability builds trust, and trust encourages contact.
+
+## Designing for the Handoff
+
+The ultimate goal of adding context and interactive elements is to improve the visitor's path from discovery to a contextual inbound. Every element on the profile should support this handoff.
+
+When a visitor decides to reach out via direct message or an email inbound, the process should be seamless but protected. Implementing robust server-side verification, such as Cloudflare Turnstile, for contact submissions ensures that the inbound path remains open for genuine visitors while protecting the creator from automated spam. A protected inbox is a usable inbox, allowing the creator to focus on meaningful connections.
+
+## Accessibility and Reliability as Baseline Features
+
+Context and interaction only matter if the profile is reliably available and accessible to everyone. A public profile must be fast. Serving the application via edge networks, such as Cloudflare Workers using OpenNext, ensures that the profile loads quickly regardless of the visitor's location.
+
+Furthermore, uncached public profiles should stream a stable loading shell while data resolves, preventing jarring layout shifts. Accessibility must be a baseline feature, not an afterthought. Preserving semantic landmarks, ensuring full keyboard access, maintaining readable contrast, and supporting reduced-motion preferences guarantees that your context is communicated effectively to the widest possible audience.
+
+## Practical Next Action
+
+Take a moment to review your current public profile or link-in-bio page. Look at it from the perspective of a first-time visitor. Does it explain *why* you are linking to these specific destinations?
+
+**Action:** Add one concrete piece of context to your profile today. This could be a short description under your primary project link explaining its current status, or a timeline event highlighting a recent milestone. Move one step away from a simple directory and one step closer to providing a clear reason for contact.
+
+## Internal-Link Suggestions
+
+*   Learn how to manage your profile's knowledgebase for better chat responses.
+*   Understanding the difference between direct messages and email inbounds.
+*   How to configure project cards to show your current focus.
+
+---
+
+## Source Notes (Non-Publishable)
+
+The claims and product capabilities described in this article are derived strictly from the current repository evidence:
+
+*   **Product Purpose and "Public Inbound Assistant":** Sourced from `PRODUCT.md` ("Karte is a public inbound assistant. It combines a creator-owned profile, links, projects, timeline, optional AI-generated profile modes, and direct messaging...").
+*   **Moving Beyond the Link List / Creator Ownership:** Sourced from `PRODUCT.md` ("The profile is not only a link list. Its owned content and optional managed Knowledgebase memory support contextual chat... Preserve local ownership and explicit creator control.").
+*   **Projects and Timelines:** Sourced from `PRODUCT.md` ("Public profiles support links, projects, timeline events...") and `PROJECT_STATUS.md` (reference to "distinguish CodeVetter focus, Karte personal maintenance...").
+*   **Providing Answers / AI Modes / Knowledgebase:** Sourced from `PRODUCT.md` (mentions "optional encyclopedia, roast, and newspaper modes") and `PROJECT_STATUS.md` (details on "managed Knowledgebase recall the default for indexed profile memory," "fallback to local memory," and the specific failover path: "fails over to Karte's product free-ai gateway... then a compact public-memory prompt and finally a deterministic public-bio answer").
+*   **Designing for the Handoff / Turnstile:** Sourced from `PROJECT_STATUS.md` ("Protected public contact submissions with Cloudflare Turnstile... fails closed unless canonical server-side verification succeeds").
+*   **Accessibility and Reliability (Cloudflare Workers/OpenNext):** Sourced from `PRODUCT.md` ("Cloudflare Workers/OpenNext serves the application", "preserve semantic landmarks, keyboard access, readable contrast... and reduced-motion support") and `AGENTS.md` ("Next.js 16... Cloudflare Workers via `@opennextjs/cloudflare`"). Also references "uncached public profiles stream a stable loading shell" from `PROJECT_STATUS.md`.
+*   **Limitations:** The article aligns with the constraint that Karte is in maintenance/personal-use mode (`PROJECT_STATUS.md`), avoiding sweeping claims of broad SaaS adoption or invented metrics, and focusing on the tangible features verified in the codebase.