Introducing the PtPlugins blog
A file-based Markdown blog, wired into the PtPlugins site in an afternoon. Here's what we'll write about — and how the blog itself works under the hood.
By PtPlugins team
We build premium Filament plugins for a living — pivot tables, model merging, deduplication, payment reconciliation, and a growing list of others. Until now everything we learned while shipping them stayed in commit messages and internal docs. This blog is where that knowledge comes out into the open.
What we'll write about
Expect practical, code-first posts:
- Filament how-tos — the non-obvious bits of building table widgets, custom columns, slide-over filters, and multi-panel apps.
- Release write-ups — what changed in a plugin, why, and what we learned shipping it.
- War stories — the production incidents, the v3-to-v4 migration gotchas, the SaaS hardening work behind ptplugins.com.
No marketing fluff. If we measured it, we'll show the numbers.
How this blog works
There's no database table and no CMS. Each post is a single Markdown file in resources/blog/posts/ with a YAML frontmatter block:
---
title: "Your post title"
slug: "your-post-slug"
date: 2026-06-07
description: "Shown on the index and in social cards."
tags: ["filament", "laravel"]
draft: false
---
A small BlogPostRepository reads the directory, parses the frontmatter, sorts newest-first, and hands the controller plain value objects. Markdown bodies render through Laravel's built-in Str::markdown() — no extra dependencies. Drafts stay hidden in production and only show up when BLOG_SHOW_DRAFTS=true, which we flip on staging behind the IP gate to preview posts before they go live.
That's the whole thing. Writing a post is just dropping a .md file in a folder and committing it.
Want a plugin covered, or have a question about one you use? Email us at mihailo@ptplugins.com.
More soon.
Try PtPlugins
Premium Filament plugins, built for production.
Pivot tables, model merging, deduplication, and more — with live demos you can try right now.