<?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://aeonbrowser.dev/blog</id>
    <title>Aeon Browser Blog</title>
    <updated>2026-04-13T00:00:00.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://aeonbrowser.dev/blog"/>
    <subtitle>Aeon Browser Blog</subtitle>
    <icon>https://aeonbrowser.dev/img/aeon-favicon.svg</icon>
    <entry>
        <title type="html"><![CDATA[Introducing the Aeon Browser Dev Portal]]></title>
        <id>https://aeonbrowser.dev/blog/introducing-dev-portal</id>
        <link href="https://aeonbrowser.dev/blog/introducing-dev-portal"/>
        <updated>2026-04-13T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[The official developer documentation site for Aeon Browser is now live at aeonbrowser.dev. Here's what to expect.]]></summary>
        <content type="html"><![CDATA[<p>Today we're launching <strong>aeonbrowser.dev</strong> — the official developer documentation hub for Aeon Browser. This site will serve as the central resource for everything technical about Aeon: architecture documentation, API references, build guides, and engineering deep-dives.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-a-dedicated-dev-site">Why a Dedicated Dev Site?<a href="https://aeonbrowser.dev/blog/introducing-dev-portal#why-a-dedicated-dev-site" class="hash-link" aria-label="Direct link to Why a Dedicated Dev Site?" title="Direct link to Why a Dedicated Dev Site?" translate="no">​</a></h2>
<p>Aeon Browser isn't a simple Chromium reskin. We're building a privacy-first, AI-native browser with a custom engine architecture. That level of ambition requires comprehensive, well-organized documentation — not just for external contributors, but for our own development velocity.</p>
<p><strong>browseaeon.com</strong> remains our product-facing site (downloads, features, marketing). <strong>aeonbrowser.dev</strong> is for developers — the people who want to understand <em>how</em> Aeon works, contribute to the codebase, or build extensions for the platform.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-here">What's Here<a href="https://aeonbrowser.dev/blog/introducing-dev-portal#whats-here" class="hash-link" aria-label="Direct link to What's Here" title="Direct link to What's Here" translate="no">​</a></h2>
<ul>
<li class=""><strong>Architecture docs</strong> covering the Aeon Engine, browser shell, and Chromium integration layer</li>
<li class=""><strong>Build guides</strong> for getting Aeon compiling from source on Windows</li>
<li class=""><strong>API reference</strong> (coming soon) for the extensions API and engine interfaces</li>
<li class=""><strong>This dev blog</strong> for engineering updates, release notes, and technical deep-dives</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="the-tech-stack">The Tech Stack<a href="https://aeonbrowser.dev/blog/introducing-dev-portal#the-tech-stack" class="hash-link" aria-label="Direct link to The Tech Stack" title="Direct link to The Tech Stack" translate="no">​</a></h2>
<p>This site is built with <a href="https://docusaurus.io/" target="_blank" rel="noopener noreferrer" class="">Docusaurus 3</a> and deployed to Firebase Hosting. It's part of the Aeon monorepo, making it easy to keep docs in sync with code changes.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-next">What's Next<a href="https://aeonbrowser.dev/blog/introducing-dev-portal#whats-next" class="hash-link" aria-label="Direct link to What's Next" title="Direct link to What's Next" translate="no">​</a></h2>
<p>We'll be publishing regular engineering updates here as we reach key milestones:</p>
<ul>
<li class=""><strong>Engine Integration</strong> — Wiring the C++ browser shell to <code>aeon_engine.dll</code></li>
<li class=""><strong>Privacy Engine</strong> — Built-in ad blocking and tracker prevention</li>
<li class=""><strong>AI Bridge</strong> — Gemini integration for intelligent browsing features</li>
<li class=""><strong>Extensions API</strong> — Manifest V3 compatibility layer with Aeon-specific extensions</li>
</ul>
<p>Follow the progress here, or star us on <a href="https://github.com/AeonBrowserDev/aeon-browser" target="_blank" rel="noopener noreferrer" class="">GitHub</a>.</p>
<hr>
<p><em>Built different. Browse different.</em></p>]]></content>
        <author>
            <name>DelgadoLogic</name>
            <uri>https://browseaeon.com</uri>
        </author>
        <category label="Release" term="Release"/>
        <category label="Infrastructure" term="Infrastructure"/>
    </entry>
</feed>