<?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://legaleaglelaws-docs.aoneahsan.com/blog</id>
    <title>Legal Eagle Documentation Blog</title>
    <updated>2026-05-10T00:00:00.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://legaleaglelaws-docs.aoneahsan.com/blog"/>
    <subtitle>Release notes, deep dives, and guides for the Legal Eagle platform.</subtitle>
    <icon>https://legaleaglelaws-docs.aoneahsan.com/img/favicon.svg</icon>
    <rights>© 2026 Legal Eagle Law Firm. Documentation by Ahsan Mahmood (CC BY 4.0).</rights>
    <entry>
        <title type="html"><![CDATA[Introducing the Legal Eagle public documentation site]]></title>
        <id>https://legaleaglelaws-docs.aoneahsan.com/blog/introducing-public-docs</id>
        <link href="https://legaleaglelaws-docs.aoneahsan.com/blog/introducing-public-docs"/>
        <updated>2026-05-10T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[Why we're publishing the Legal Eagle Law Firm documentation as an openly licensed, separately hosted public site on legaleaglelaws-docs.aoneahsan.com.]]></summary>
        <content type="html"><![CDATA[<p>The application source code for <a href="https://legaleaglelaws.com/" target="_blank" rel="noopener noreferrer" class="">legaleaglelaws.com</a> is in a private repository — and is going to stay there. The platform handles confidential client matters and publishing the source would be both an indirect security risk and a distraction from the work.</p>
<p>But documentation is different.</p>
<p>Documentation is the part of a product where transparency makes the product <strong>more</strong> trustworthy, not less. A user who reads how a feature works, what it does <strong>not</strong> do, and where its limits are is a user who can use it well. Hidden documentation tends to be less rigorous — there's nobody outside the team checking it — and it tends to atrophy because nobody outside the team can correct it.</p>
<p>So as of today, the Legal Eagle Law Firm public documentation lives at <strong><a href="https://legaleaglelaws-docs.aoneahsan.com/" target="_blank" rel="noopener noreferrer" class="">legaleaglelaws-docs.aoneahsan.com</a></strong> — an openly licensed (CC BY 4.0), separately hosted Docusaurus site. The repository is public on GitHub at <a href="https://github.com/aoneahsan/legaleaglelawfirm-docs" target="_blank" rel="noopener noreferrer" class="">aoneahsan/legaleaglelawfirm-docs</a>; spotting an inaccuracy or want to suggest a clearer way to phrase something, open a pull request.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-covered">What's covered<a href="https://legaleaglelaws-docs.aoneahsan.com/blog/introducing-public-docs#whats-covered" class="hash-link" aria-label="Direct link to What's covered" title="Direct link to What's covered" translate="no">​</a></h2>
<p>Three audiences:</p>
<ul>
<li class=""><strong>Visitors and firm clients</strong> — how to find a lawyer, book a free consultation, use the AI legal assistant, navigate the firm-client dashboard.</li>
<li class=""><strong>Firm staff (admin)</strong> — the admin panel, content workflows, plan management. <em>(Pages incrementally being released.)</em></li>
<li class=""><strong>Technically curious readers</strong> — a high-level architecture overview, public-safe. No secrets, no internal endpoints. Just the orientation a developer or a journalist needs to evaluate the platform's posture.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="how-the-site-is-built">How the site is built<a href="https://legaleaglelaws-docs.aoneahsan.com/blog/introducing-public-docs#how-the-site-is-built" class="hash-link" aria-label="Direct link to How the site is built" title="Direct link to How the site is built" translate="no">​</a></h2>
<p><a href="https://docusaurus.io/" target="_blank" rel="noopener noreferrer" class="">Docusaurus 3.10</a> on Node 20, TypeScript, MDX. Mermaid for diagrams, <code>@docusaurus/faster</code> (Rspack) for build performance, <code>@docusaurus/plugin-ideal-image</code> for responsive images. Theme is hand-built around the firm's navy-and-gold brand with full dark-mode parity.</p>
<p>The site ships to three deploy targets in parallel:</p>
<table><thead><tr><th>Target</th><th>URL</th><th>Purpose</th></tr></thead><tbody><tr><td>Firebase Hosting (firm domain)</td><td>legaleaglelaws-docs.aoneahsan.com</td><td>Brand-aligned home</td></tr><tr><td>Firebase Hosting (developer domain)</td><td>legaleaglelaws-docs.aoneahsan.com</td><td>Same site, second custom domain</td></tr><tr><td>GitHub Pages</td><td>aoneahsan.github.io/legaleaglelawfirm-docs</td><td>Independent search visibility on github.io</td></tr></tbody></table>
<p>Triple deployment is deliberate: GitHub Pages on github.io carries strong domain authority for new technical content, while the brand domains carry the on-brand reading experience.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="seo--aeo-posture">SEO + AEO posture<a href="https://legaleaglelaws-docs.aoneahsan.com/blog/introducing-public-docs#seo--aeo-posture" class="hash-link" aria-label="Direct link to SEO + AEO posture" title="Direct link to SEO + AEO posture" translate="no">​</a></h2>
<p>The site follows a strict per-page-uniqueness floor — every documentation page is at least 1 000 words of unique content with a definition-first intro, structured FAQ, explicit limitations, and a last-updated date. AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot, CCBot) are explicitly allow-listed in <code>robots.txt</code>. A root <code>llms.txt</code> (per <a href="https://llmstxt.org/" target="_blank" rel="noopener noreferrer" class="">llmstxt.org</a>) gives AI agents a curated map. Per-page JSON-LD covers WebSite, Organization, BreadcrumbList, Article, and FAQPage where applicable.</p>
<p>Honest framing is a hard rule. Every page documents what the feature does <strong>not</strong> do as clearly as what it does. Browser-only privacy claims match reality. No fabricated statistics — anything cited is named and linked.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="author">Author<a href="https://legaleaglelaws-docs.aoneahsan.com/blog/introducing-public-docs#author" class="hash-link" aria-label="Direct link to Author" title="Direct link to Author" translate="no">​</a></h2>
<p>I'm <strong><a href="https://aoneahsan.com/" target="_blank" rel="noopener noreferrer" class="">Ahsan Mahmood</a></strong> — full-stack engineer specialising in React, Capacitor, and Firebase. I built and maintain the Legal Eagle platform, the SaaS workspace, and this documentation site. The legal practice itself belongs to <em>Advocate Maaz Ahmed Warriach</em> and operates from Office No. 3, 2nd Floor, Kareem Chamber 2, Mozang, Lahore.</p>
<p>If you're hiring, want to chat about a similar project, or like the work and want to support continued maintenance:</p>
<ul>
<li class="">Portfolio: <a href="https://aoneahsan.com/" target="_blank" rel="noopener noreferrer" class="">aoneahsan.com</a></li>
<li class="">LinkedIn: <a href="https://linkedin.com/in/aoneahsan" target="_blank" rel="noopener noreferrer" class="">linkedin.com/in/aoneahsan</a></li>
<li class="">GitHub: <a href="https://github.com/aoneahsan" target="_blank" rel="noopener noreferrer" class="">github.com/aoneahsan</a></li>
<li class="">npm: <a href="https://www.npmjs.com/~aoneahsan" target="_blank" rel="noopener noreferrer" class="">npmjs.com/~aoneahsan</a></li>
<li class="">Email: <a href="mailto:aoneahsan@gmail.com" target="_blank" rel="noopener noreferrer" class="">aoneahsan@gmail.com</a></li>
<li class="">WhatsApp: <a href="https://wa.me/923046619706" target="_blank" rel="noopener noreferrer" class="">+92 304 661 9706</a></li>
<li class="">Support this work: <a href="https://aoneahsan.com/payment?project-id=legaleaglelawfirm&amp;project-identifier=com.legaleaglelaws.app" target="_blank" rel="noopener noreferrer" class="">aoneahsan.com/payment</a></li>
</ul>]]></content>
        <author>
            <name>Ahsan Mahmood</name>
            <email>aoneahsan@gmail.com</email>
            <uri>https://aoneahsan.com</uri>
        </author>
        <category label="Announcements" term="Announcements"/>
        <category label="Documentation" term="Documentation"/>
    </entry>
</feed>