<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Tupynambá Lucas Blog</title>
        <link>https://tupynambalucas.dev/blog</link>
        <description>Tupynambá Lucas Blog</description>
        <lastBuildDate>Sat, 03 Oct 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <item>
            <title><![CDATA[Release - v1.0.0]]></title>
            <link>https://tupynambalucas.dev/blog/releases/v1.0.0</link>
            <guid>https://tupynambalucas.dev/blog/releases/v1.0.0</guid>
            <pubDate>Sat, 03 Oct 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Welcome to the first official major release of tupynambalucas.dev (v1.0.0)! This update establishes our core architecture, localization infrastructure, and unifies our content strategy.]]></description>
            <content:encoded><![CDATA[<p>Welcome to the first official major release of tupynambalucas.dev (<code>v1.0.0</code>)! This update establishes our core architecture, localization infrastructure, and unifies our content strategy.</p>
<!-- -->
<h3 class="anchor anchorTargetStickyNavbar_hOK8" id="highlights">Highlights<a href="https://tupynambalucas.dev/blog/releases/v1.0.0#highlights" class="hash-link" aria-label="Direct link to Highlights" title="Direct link to Highlights" translate="no">​</a></h3>
<ul>
<li class=""><strong>Unified Content Architecture</strong>: We have officially merged the Changelog and the Blog into a single chronological timeline. All releases, updates, and regular posts are now accessed in one unified view.</li>
<li class=""><strong>Enterprise Localization Pipeline</strong>:<!-- -->
<ul>
<li class="">Restructured our translation strategy, extracting Docusaurus React UI strings into a dedicated, enterprise-standard <code>messages/</code> folder.</li>
<li class="">Deployed a unified plugin to automatically unpack Crowdin translations directly into the Docusaurus native locale structure.</li>
<li class="">Successfully mapped Crowdin properties for Docusaurus JSON (<code>type: chrome</code>), preventing translators from modifying system keys.</li>
<li class="">Completed the first full wave of Portuguese (pt-BR) localization covering Brand Principles, Design Tokens, Cloudflare Storage, and the entire Knowledge Base Overview.</li>
</ul>
</li>
<li class=""><strong>GitOps and Automation</strong>: Hardened our <code>.github/</code> workflows for synchronized translation deployment and architecture-as-code principles.</li>
</ul>
<p>We are ready to scale!</p>]]></content:encoded>
            <category>Release</category>
            <category>Architecture</category>
            <category>L10n</category>
            <category>I18n</category>
        </item>
        <item>
            <title><![CDATA[Welcome to the Tupynambalucas Knowledge Base & Architecture Portal]]></title>
            <link>https://tupynambalucas.dev/blog/welcome-to-knowledge-base</link>
            <guid>https://tupynambalucas.dev/blog/welcome-to-knowledge-base</guid>
            <pubDate>Tue, 29 Sep 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Welcome to the official developer portal and technical documentation platform for tupynambalucas.dev.]]></description>
            <content:encoded><![CDATA[<p>Welcome to the official developer portal and technical documentation platform for <strong>tupynambalucas.dev</strong>.</p>
<p>This platform serves as the central source of truth for architectural specifications, system designs, workspace guides, and community initiatives across our unified monorepo.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_hOK8" id="architectural-foundations">Architectural Foundations<a href="https://tupynambalucas.dev/blog/welcome-to-knowledge-base#architectural-foundations" class="hash-link" aria-label="Direct link to Architectural Foundations" title="Direct link to Architectural Foundations" translate="no">​</a></h2>
<p>The Tupynambalucas monorepo is engineered as a modular, high-performance system structured around clear bounded contexts:</p>
<ul>
<li class=""><strong>Documentation Portal (<code>knowledge-base/</code>)</strong>: A decoupled documentation architecture using Docusaurus v3, organized by content collections and custom preset integrations.</li>
<li class=""><strong>Unified AI Engine (<code>cortex/</code>)</strong>: AgentGateway MCP proxy, vector memory subsystems, and automated coding agents.</li>
<li class=""><strong>Infrastructure &amp; Platform (<code>platform/</code>)</strong>: Kubernetes cluster management, Traefik ingress, Cloudflare tunnels, and OpenTelemetry observability pipelines.</li>
<li class=""><strong>Brand &amp; Asset Studio (<code>studio/</code>)</strong>: Centralized design tokens, Penpot integrations, and R2 asset distribution.</li>
<li class=""><strong>Client &amp; API Hub (<code>hub/</code>)</strong>: React 19 web applications and Fastify 5 REST services.</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_hOK8" id="what-to-expect">What to Expect<a href="https://tupynambalucas.dev/blog/welcome-to-knowledge-base#what-to-expect" class="hash-link" aria-label="Direct link to What to Expect" title="Direct link to What to Expect" translate="no">​</a></h2>
<p>Moving forward, this blog will publish:</p>
<ol>
<li class=""><strong>Release Notes</strong>: Deep dives into major versions, breaking changes, and migrations.</li>
<li class=""><strong>Architecture Decision Records (ADRs)</strong>: In-depth rationale behind structural choices and infrastructure upgrades.</li>
<li class=""><strong>Engineering Updates</strong>: Benchmarks, developer experience improvements, and ecosystem milestones.</li>
</ol>
<p>Explore the <a class="" href="https://tupynambalucas.dev/docs/intro">Documentation</a> or check out the <a class="" href="https://tupynambalucas.dev/community/support">Community</a> section to get involved!</p>]]></content:encoded>
            <category>Announcement</category>
            <category>Architecture</category>
            <category>Portal</category>
        </item>
    </channel>
</rss>