<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<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>Byte8 PingBell Blog</title>
        <link>https://magento-pingbell.byte8.dev/blog</link>
        <description>Byte8 PingBell Blog</description>
        <lastBuildDate>Sun, 26 Apr 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[v1.0.0 — initial release]]></title>
            <link>https://magento-pingbell.byte8.dev/blog/v1-0-0-release</link>
            <guid>https://magento-pingbell.byte8.dev/blog/v1-0-0-release</guid>
            <pubDate>Sun, 26 Apr 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[The first public release of Byte8 PingBell is out: a tiny, MIT-licensed]]></description>
            <content:encoded><![CDATA[<p>The first public release of Byte8 PingBell is out: a tiny, MIT-licensed
Magento 2 module that bridges five core store events into
<a href="https://pingbell.io/" target="_blank" rel="noopener noreferrer">PingBell</a> for instant push notifications on phone,
desktop and watch.</p>
<h2 class="anchor anchorWithStickyNavbar_gijT" id="whats-in-v100">What's in v1.0.0<a href="https://magento-pingbell.byte8.dev/blog/v1-0-0-release#whats-in-v100" class="hash-link" aria-label="Direct link to What's in v1.0.0" title="Direct link to What's in v1.0.0" translate="no">​</a></h2>
<ul>
<li><strong>Five built-in event types</strong> — orders, invoices, shipments, credit
memos, and customer registrations. Each routes to its own PingBell ID.</li>
<li><strong>Encrypted API key storage</strong> — uses Magento's standard
<code>Magento\Config\Model\Config\Backend\Encrypted</code> backend model. The raw
key never sits in plaintext in <code>core_config_data</code>.</li>
<li><strong>Fetch Bells admin UI</strong> — a button on every event row that calls
<code>https://app.pingbell.io/userPingbells</code> and lets the admin pick a bell
from a dropdown rather than hand-typing the ID.</li>
<li><strong>Dedicated log file</strong> — every notification attempt, success or
failure, has a single line in <code>var/log/pingbell.log</code>. Separate from
<code>system.log</code> for clean ops/debug separation.</li>
<li><strong>Non-blocking by design</strong> — 5-second cURL timeout, exception-swallowed
observers. If pingbell.io is down or unreachable, your Magento checkout
/ invoice / refund flows complete unaffected.</li>
<li><strong>Multi-event extensibility</strong> — the observer is event-agnostic; new
events are added via a virtualType + an <code>events.xml</code> entry. See the
<a href="https://magento-pingbell.byte8.dev/docs/advanced/extending">Extending docs</a> for the pattern.</li>
</ul>
<h2 class="anchor anchorWithStickyNavbar_gijT" id="why-deep-indigo">Why deep indigo<a href="https://magento-pingbell.byte8.dev/blog/v1-0-0-release#why-deep-indigo" class="hash-link" aria-label="Direct link to Why deep indigo" title="Direct link to Why deep indigo" translate="no">​</a></h2>
<p>Eagle-eyed visitors might notice the docs site is deep indigo, while
Stock Radar is amber, VAT Validator is green and SEO Suite is brighter
indigo. The reasoning: each Byte8 Magento module gets a marketing-aligned
colour from the same product-family palette. PingBell sits in the
"alerts / push / signal" family — and the colour <code>#1f1d51</code> is lifted
straight from the <a href="https://pingbell.io/" target="_blank" rel="noopener noreferrer">pingbell.io</a> brand, so the docs
site feels like an extension of the parent product.</p>
<h2 class="anchor anchorWithStickyNavbar_gijT" id="whats-next">What's next<a href="https://magento-pingbell.byte8.dev/blog/v1-0-0-release#whats-next" class="hash-link" aria-label="Direct link to What's next" title="Direct link to What's next" translate="no">​</a></h2>
<ul>
<li><strong>Richer notification payloads</strong> — once PingBell's API supports
per-call message text, we'll wire order number / total / customer
email into the buzz body.</li>
<li><strong>Per-store routing</strong> — currently default-scope only. Multi-store
routing is on the roadmap as soon as we see real demand for it.</li>
<li><strong>A custom-events recipe gallery</strong> — community-contributed snippets
for common "I want a buzz when X happens" requests (newsletter
signups, low-stock thresholds, abandoned cart hits a value
threshold, …).</li>
<li><strong>Marketplace listing</strong> on Adobe Commerce + Hyvä Showroom.</li>
</ul>]]></content:encoded>
            <category>release</category>
        </item>
    </channel>
</rss>