Think Data Hub

Tag: Wordpress

  • The 3-Tier Logic Stack: How I Run This Hub

    Complexity is the enemy of execution.

    I often see creators carrying a “debt” of 15+ subscriptions—Monday.com for tasks, Trello for roadmaps, Webflow for design, ConvertKit for emails. They spend more time managing their tools than building their products.

    I run Think Data Hub on a lean, 3-tier architecture. It costs almost nothing and requires zero maintenance.

    Here is the stack.

    Tier 1: The Operating System (Notion)

    Everything starts here. I don’t use Notion just for notes; I use it as a relational database.

    • CRM: Tracking connections.
    • Content Calendar: Planning these posts.
    • Product Development: Building tools like The Auto-Prioritizer.

    If it isn’t in Notion, it doesn’t exist. It is the RAM of my business.

    Tier 2: The Engine (WordPress)

    Many people moved to Substack or Medium. I stayed on WordPress. Why? Control.

    I treat WordPress as a “Headless CMS.” It allows me to build custom logic loops—like the Self-Updating Code Repository I built yesterday—without needing a dev team. It is robust, open-source, and I own the data.

    Tier 3: The Storefront (Gumroad)

    I don’t want to manage Stripe APIs or worry about VAT taxes in Europe. Gumroad handles the logistics. It is the checkout layer.

    • I build the logic in Notion.
    • I explain the logic in WordPress.
    • I deliver the file via Gumroad.

    See the live storefront in action here.

    The Philosophy

    This stack follows the “Unix Philosophy”: Do one thing and do it well.

    • Notion handles Data.
    • WordPress handles Display.
    • Gumroad handles Transaction.

    Stop looking for the “perfect” all-in-one tool. It doesn’t exist. Build a modular stack and get to work.

  • Stop Manually Updating Your Blog. Build a “Query Loop” Instead.

    I hate manual maintenance.

    In engineering, if you have to do something twice, you automate it. If you have to do it three times, you build a system.

    For a long time, my “Guides” pages were static. Every time I wrote a new article about Notion or Python, I had to:

    1. Open the “Notion Guide” page.
    2. Create a new text block.
    3. Paste the link.
    4. Upload the thumbnail.

    This is O(n) complexity. As the number of posts grows, the maintenance time grows linearly. That is bad architecture.

    Today, I refactored my site to be O(1).

    I replaced my static lists with a Query Loop. Now, my “Logic Hub” updates itself automatically.

    The Logic: What is a Query Loop?

    In SQL terms, a Query Loop is just a visual interface for this command:

    SQL

    SELECT * FROM posts
    WHERE tag = 'Notion'
    ORDER BY date DESC

    It dynamically fetches content from your database and renders it on the page. You define the “Template” (how one card looks), and the loop repeats it for every matching post.

    The Protocol: How to Build It (No Plugins)

    You don’t need heavy plugins like Elementor or custom PHP for this. WordPress has a native block that does it all.

    Step 1: The Setup Create a new page (e.g., “The Logic Hub”) and type /query. Select the Query Loop block.

    Step 2: The View Select “Grid View”. This turns your posts into a visual catalogue of cards rather than a boring list of links.

    Step 3: The Filter (Critical) This is where the magic happens.

    1. Click the Query Loop block.
    2. Open the Settings Sidebar.
    3. Under Filters, set your parameter.
      • Example: Category: Notion

    Now, the moment I hit “Publish” on a new article, it automatically appears in my Hub.

    I don’t touch the page. The system does the work.

    See the live result here