<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>webdesign — TypeDrawers</title>
        <link>https://typedrawers.com/</link>
        <pubDate>Mon, 08 Jun 2026 19:48:19 +0000</pubDate>
        <language>en</language>
            <description>webdesign — TypeDrawers</description>
    <atom:link href="https://typedrawers.com/discussions/tagged/webdesign/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>The Forge, a CMS built for type foundries</title>
        <link>https://typedrawers.com/discussion/5604/the-forge-a-cms-built-for-type-foundries</link>
        <pubDate>Mon, 08 Jun 2026 13:58:04 +0000</pubDate>
        <category>Type Business</category>
        <dc:creator>octavio</dc:creator>
        <guid isPermaLink="false">5604@/discussions</guid>
        <description><![CDATA[<div>I’m Octavio Pardo and I run <a rel="nofollow">Ashler, </a>a design and development studio focused on brand and digital craft. For years we’ve worked alongside type designers and foundries, helping shape their brands, build their websites, and translate the complexity of type into clear, high-performing digital experiences. That close collaboration has given us a front-row seat to a recurring problem: selling fonts online is still far harder than it should be.<br /><br /></div><div><b>The problem: selling type through generic e‑commerce</b></div><div>When a foundry tries to sell through generic e‑commerce, it usually turns into a patchwork of half-solutions: licensing forced into product variants, pricing logic squeezed into the wrong constraints, plugins piled on, custom code everywhere, and a buying flow that doesn’t match how people browse type families in the real world. The result is that you’re constantly adapting your work to a system that doesn’t understand it, and your website becomes a parallel technical project, which is exactly what it shouldn’t be.<br /><br /></div><div><b>A foundry doesn’t sell “files”</b></div><div>Because a foundry doesn’t sell “files.” It sells releases, specimen pages, updates, bug fixes, support, invoicing, VAT, renewals, and all the licensing edge cases that appear as soon as you have real customers. And when you try to handle all of that on platforms built for t‑shirts or online courses, you end up simplifying your offer just to make it fit the checkout, instead of building an experience that respects your business model.<br /><br /></div><div><b>What changes with The Forge</b></div><div>The Forge is built to change that dynamic. It’s a platform designed specifically for foundries: so licensing can match the way you work (your rules, your prices, your terms), and so the buying experience stays smooth and reliable when someone is ready to purchase. Because at that moment, performance isn’t a detail: it is part of the product. If the cart feels slow, sessions reset, tabs go out of sync, or checkout feels fragile, what you lose isn’t “a conversion.” You lose trust.<br /><br /></div><div><b>The Forge Mini (in progress)</b></div><div>Right now we’re building The Forge Mini, an entry version that starts with a solid base and lets you add customizations and features over time through an affordable monthly fee. The goal is to create a clear growth path: so a foundry can scale progressively without a big upfront investment, and once the project reaches a defined break point, there should be no reason to keep paying a monthly fee. If you want updates, you can join the newsletter to stay in the loop.<br /><br /></div><div><b>Learn more</b></div><div><a rel="nofollow" href="https://typedrawers.com/home/leaving?allowTrusted=1&amp;target=https%3A%2F%2Ftheforge.ashler.design%2F">https://theforge.ashler.design/</a></div><div><br /></div>]]>
        </description>
    </item>
   </channel>
</rss>
