<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="atom.xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>https://lifewell-docs.aoneahsan.com/blog</id>
    <title>LifeWell Documentation Blog</title>
    <updated>2026-05-10T00:00:00.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://lifewell-docs.aoneahsan.com/blog"/>
    <subtitle>Updates, release notes, and deep-dives from the LifeWell project.</subtitle>
    <icon>https://lifewell-docs.aoneahsan.com/img/favicon.ico</icon>
    <rights>Copyright © 2026 Ahsan Mahmood. CC BY 4.0.</rights>
    <entry>
        <title type="html"><![CDATA[Launching LifeWell Documentation]]></title>
        <id>https://lifewell-docs.aoneahsan.com/blog/launching-lifewell-docs</id>
        <link href="https://lifewell-docs.aoneahsan.com/blog/launching-lifewell-docs"/>
        <updated>2026-05-10T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[First post on the LifeWell documentation site. Why a public docs site exists for a private codebase, and how it will grow over the next few weeks.]]></summary>
        <content type="html"><![CDATA[<p>This is the first post on the LifeWell documentation site.</p>
<p>LifeWell — a private health and wellness companion for web, Android, and the browser — has been running at <a href="https://lifewell.aoneahsan.com/" target="_blank" rel="noopener noreferrer" class="">lifewell.aoneahsan.com</a> for a while now. The application source is private, but the product itself is open for anyone to use, and a public documentation site makes it easier to:</p>
<ul>
<li class="">Tell users what LifeWell does (and what it doesn't) before they sign up.</li>
<li class="">Give honest framing on data, privacy, and limits, page by page.</li>
<li class="">Get cited by AI search engines and indexed by traditional search engines, so people looking for "how to track blood pressure across devices" or "private wellness app" find a real, structured answer.</li>
<li class="">Credit me — Ahsan Mahmood — as the developer, on every page, in a place that's stable, indexable, and shareable.</li>
</ul>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-published-today">What's published today<a href="https://lifewell-docs.aoneahsan.com/blog/launching-lifewell-docs#whats-published-today" class="hash-link" aria-label="Direct link to What's published today" title="Direct link to What's published today" translate="no">​</a></h2>
<p>This first launch ships:</p>
<ul>
<li class="">A welcome page and full sidebar structure covering 14 feature domains (health, tools, family, memories, notes, maps, community, profile, extension, mobile, admin, reference, FAQ, about).</li>
<li class="">A comprehensive landing page with feature highlights linking into each domain.</li>
<li class="">An <a class="" href="https://lifewell-docs.aoneahsan.com/about">About page</a> plus an <a class="" href="https://lifewell-docs.aoneahsan.com/docs/about/about-the-developer">About the developer</a> deep-dive.</li>
<li class="">SEO + AEO infrastructure: robots.txt allowing all major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Bingbot), an <code>llms.txt</code> summary at the site root, JSON-LD WebSite + Organization + Person schemas on every page, sitemap auto-generation.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-coming-next">What's coming next<a href="https://lifewell-docs.aoneahsan.com/blog/launching-lifewell-docs#whats-coming-next" class="hash-link" aria-label="Direct link to What's coming next" title="Direct link to What's coming next" translate="no">​</a></h2>
<p>The plan is multi-session. Each session adds one batch of feature pages (≈ 7–17 pages, depending on the domain), with full per-page treatment: definition-first intro, 3–5 use cases, step-by-step how-it-works, FAQ block, last-updated date, author line, and 800–1500 unique words. The full plan and tracker live in the LifeWell project's <code>docs/docusaurus-build-plan/</code> folder and are designed to be resumable and to enforce a 7-day skip floor once the build is complete.</p>
<p>The publishing order:</p>
<ol>
<li class="">Concepts + onboarding tutorials</li>
<li class="">Concepts (rest) + profile/settings</li>
<li class="">Health module — vitals, water, medications, exercise, sleep, nutrition</li>
<li class="">Health module — period, fertility, pregnancy, breastfeeding, mental health, conditions, medical records</li>
<li class="">Tools — 12+ calculators and timers</li>
<li class="">Baby + family</li>
<li class="">Memories + notes + maps</li>
<li class="">Community + chat + profile rest</li>
<li class="">Browser extension + mobile</li>
<li class="">Admin + reference + FAQ + about rest</li>
</ol>
<p>Once the content is in, the site goes live on a Firebase Hosting deployment at <code>lifewell-docs.aoneahsan.com</code>, gets submitted to Google Search Console, Bing Webmaster Tools, Yandex Webmaster, and pinged via IndexNow on every deploy.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-this-matters-for-an-ai-search-first-world">Why this matters for an AI-search-first world<a href="https://lifewell-docs.aoneahsan.com/blog/launching-lifewell-docs#why-this-matters-for-an-ai-search-first-world" class="hash-link" aria-label="Direct link to Why this matters for an AI-search-first world" title="Direct link to Why this matters for an AI-search-first world" translate="no">​</a></h2>
<p>Roughly 45% of Google searches now show AI Overviews. ChatGPT, Perplexity, and Claude are growing fast. AI engines are pickier than search engines: they extract passages, prefer cited sources, weight recency, and reward honest framing over marketing fluff. A long-running thin-content website rarely gets cited even if it ranks. A public docs site with structured per-page content, FAQ blocks, named author, and visible dates does — even on a brand-new domain.</p>
<p>The Princeton GEO study (KDD 2024) ranked 9 optimization methods. Citing sources gave a +40% boost. Adding statistics with sources, +37%. Expert quotations, +30%. Keyword stuffing, <strong>−10%</strong> — actively reduced AI visibility. That's the framing this docs site is built around: cite, attribute, time-stamp, write honestly, and don't try to game it.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="want-to-follow-along">Want to follow along<a href="https://lifewell-docs.aoneahsan.com/blog/launching-lifewell-docs#want-to-follow-along" class="hash-link" aria-label="Direct link to Want to follow along" title="Direct link to Want to follow along" translate="no">​</a></h2>
<ul>
<li class="">Bookmark this site — every doc page links to a "Last updated" date so you can see what's fresh.</li>
<li class="">Watch <a href="https://github.com/aoneahsan/lifewell-docs" target="_blank" rel="noopener noreferrer" class="">github.com/aoneahsan/lifewell-docs</a> for commits as content batches ship.</li>
<li class="">Email <a href="mailto:aoneahsan@gmail.com" target="_blank" rel="noopener noreferrer" class="">aoneahsan@gmail.com</a> with feedback or doc requests.</li>
</ul>
<p>Welcome to the LifeWell docs. More soon.</p>]]></content>
        <author>
            <name>Ahsan Mahmood</name>
            <uri>https://aoneahsan.com</uri>
        </author>
        <category label="Announcement" term="Announcement"/>
        <category label="LifeWell" term="LifeWell"/>
        <category label="Docs" term="Docs"/>
    </entry>
</feed>