<?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://your-docusaurus-site.example.com/blog</id>
    <title>Ouasl Documentation Blog</title>
    <updated>2026-04-14T00:00:00.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://your-docusaurus-site.example.com/blog"/>
    <subtitle>Ouasl Documentation Blog</subtitle>
    <icon>https://your-docusaurus-site.example.com/img/ouasl.svg</icon>
    <entry>
        <title type="html"><![CDATA[Introducing the Ouasl Builder Documentation]]></title>
        <id>https://your-docusaurus-site.example.com/blog/docs-launch</id>
        <link href="https://your-docusaurus-site.example.com/blog/docs-launch"/>
        <updated>2026-04-14T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[We're excited to launch the official Ouasl Builder Documentation — a single place for every team member to learn how to create, style, and ship reusable sections for the Ouasl app builder.]]></summary>
        <content type="html"><![CDATA[<p>We're excited to launch the official <strong>Ouasl Builder Documentation</strong> — a single place for every team member to learn how to create, style, and ship reusable sections for the Ouasl app builder.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why-we-built-this">Why we built this<a href="https://your-docusaurus-site.example.com/blog/docs-launch#why-we-built-this" class="hash-link" aria-label="Direct link to Why we built this" title="Direct link to Why we built this" translate="no">​</a></h2>
<p>Ouasl templates are made of independent <strong>sections</strong> that our backend merges into complete, production-ready pages. Each section has to follow a strict set of rules so it can be edited inside the builder, its styles don't leak into other sections, and its data is tracked correctly by the dashboard.</p>
<p>Until today, those rules lived scattered across internal notes, PDFs, and chat messages. That worked when two people were writing sections — it stopped working the moment the team grew. This documentation is our answer.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="whats-inside">What's inside<a href="https://your-docusaurus-site.example.com/blog/docs-launch#whats-inside" class="hash-link" aria-label="Direct link to What's inside" title="Direct link to What's inside" translate="no">​</a></h2>
<p>The docs are organized into seven topic categories, each covering a specific part of building a Ouasl section:</p>
<ul>
<li class=""><strong>🏗️ HTML Structure</strong> — root tags, <code>data-tag</code>, the mandatory <code>.container</code> wrapper, the <code>wrapper</code> and <code>content-box</code> utility classes</li>
<li class=""><strong>🎬 Media</strong> — embedding YouTube / Vimeo / Dailymotion video, Google Maps, and Swiper sliders (with carousel and pagination patterns)</li>
<li class=""><strong>🧩 Components</strong> — the three mandatory patterns: responsive headers with the hamburger script, native <code>&lt;details&gt;</code> accordions, and countdown timers</li>
<li class=""><strong>📝 Forms</strong> — every input type, side-by-side <code>half-span</code> fields, the special <code>first_name</code> / <code>last_name</code> tracker attributes, and the newsletter / contact / leads form types</li>
<li class=""><strong>⚡ JavaScript</strong> — variable rules (<code>var</code> / <code>let</code> only), <code>querySelectorAll</code>, named-function scoping, and the header hamburger logic</li>
<li class=""><strong>🎨 CSS &amp; Styling</strong> — the fixed color palette (main / secondary / shades-1..10 / tints-1..10), mandatory RTL direction, and the three responsive breakpoints</li>
<li class=""><strong>🛠️ Tools</strong> — an interactive <strong>Unique ID Generator</strong> you can use to generate <code>data-form-id</code> values without leaving the docs</li>
</ul>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="bilingual-from-day-one">Bilingual from day one<a href="https://your-docusaurus-site.example.com/blog/docs-launch#bilingual-from-day-one" class="hash-link" aria-label="Direct link to Bilingual from day one" title="Direct link to Bilingual from day one" translate="no">​</a></h2>
<p>The whole site ships in <strong>English</strong> and <strong>Arabic</strong> (العربية) — switch with the locale picker in the navbar. Every page, sidebar label, and category description is translated, and the Arabic build uses the <strong>Cairo</strong> font (the same family our templates use), with automatic RTL layout across the site.</p>
<p>Code blocks stay left-to-right in both locales, so the HTML / CSS / JavaScript examples read naturally no matter which language you're browsing in.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="search-that-works">Search that works<a href="https://your-docusaurus-site.example.com/blog/docs-launch#search-that-works" class="hash-link" aria-label="Direct link to Search that works" title="Direct link to Search that works" translate="no">​</a></h2>
<p>We've added a local search engine indexed over every docs page and every blog post. Press the search box in the navbar (or <code>Ctrl+K</code>) and start typing — results appear as you type, in both languages.</p>
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="what-to-do-next">What to do next<a href="https://your-docusaurus-site.example.com/blog/docs-launch#what-to-do-next" class="hash-link" aria-label="Direct link to What to do next" title="Direct link to What to do next" translate="no">​</a></h2>
<ul>
<li class="">New to Ouasl? Start with <a class="" href="https://your-docusaurus-site.example.com/docs/getting-started"><strong>Getting Started</strong></a> and then copy-paste the <a class="" href="https://your-docusaurus-site.example.com/docs/quick-start"><strong>Quick Start</strong></a> example to see a working section on screen in under two minutes.</li>
<li class="">Already building sections? Skim the updated rules in <a class="" href="https://your-docusaurus-site.example.com/docs/section-structure"><strong>HTML Structure</strong></a> and <a class="" href="https://your-docusaurus-site.example.com/docs/css/rules"><strong>CSS Rules</strong></a> — the class names are now <code>ouasl_*</code> and <code>oa-*</code>, and the color palette has new shades/tints variables.</li>
<li class="">Need to generate form IDs? The <a class="" href="https://your-docusaurus-site.example.com/docs/tools/id-generator"><strong>ID Generator</strong></a> is now an interactive React component right inside the docs.</li>
</ul>
<p>We'll keep this site updated as the builder evolves. If you find something missing or unclear, open an issue on the <a href="https://github.com/wibitech-agency" target="_blank" rel="noopener noreferrer" class=""><strong>GitHub repo</strong></a> — we read every one.</p>
<p>Happy building. 🚀</p>]]></content>
        <author>
            <name>Ouasl Team</name>
            <uri>https://github.com/wibitech-agency</uri>
        </author>
        <category label="Launch" term="Launch"/>
        <category label="Documentation" term="Documentation"/>
        <category label="Announcement" term="Announcement"/>
    </entry>
</feed>