Sign inBlogSupportContact
AI

Summarize any WordPress post or WooCommerce product as a downloadable PDF

AI reads the post, writes the summary, TrueCommander packages it as a PDF. Works on posts, works on products, works on both at once. No external AI app, no copy-paste roundtrip.

3 min read May 2026 ai summarize

Long-form content that nobody has time to read

Your blog has 200 published posts averaging 2,000 words. A new team member needs to get up to speed on editorial voice and topics you've covered. They're not going to read 400,000 words of archive. A product manager wants a one-page brief on each of the twenty SKUs in a category. Nobody prints every product page. You need a summary, fast, preferably PDF so it travels.

What most people do instead

Copy-paste into an AI chat, then into a PDF converterTwo tools, two copy-pastes, risk of losing formatting. Does not scale to 200 posts.
Print the whole post to PDF2,000 words, no summary. Defeats the point — you wanted the short version.
Ask someone to write a briefHalf a day per post. For a 200-post archive, a full month of content-team time nobody budgeted.

A better way: one command, summary in PDF

Run ai summarize -post_id=247. TrueCommander reads the post, sends title + content to AI, gets a summary back, renders it as a DOMPDF-generated PDF saved to uploads/tp-ai-pdfs/. The navigator shows a download link. The PDF is portable, shareable, and sized right for a one-page brief.

TrueCommander
Summary PDF ready
DOMPDF rendered
Source post: #1247 — "A history of single-estate Mediterranean olive oil"
Summary: 6 paragraphs, 240 words
Download: summary-1247-1747310400.pdfready

Post + product together = linked-entity summary. Pass both -post_id AND -product_id and AI receives both contexts. The summary ties the blog post to the product it reviews — ideal for long-form product launches where you want a one-page brief covering both the story and the SKU.

How it works

The handler validates at least one of -post_id or -product_id is provided and numeric. For posts, it pulls post_title + post_content; for products (requires WooCommerce), it pulls name + formatted price. These build a prompt like "Summarize this WordPress blog post: Title: {X}, Content: {Y}". AI returns the summary. The response() method takes over: creates uploads/tp-ai-pdfs/ if needed, builds minimal HTML with the summary text, runs it through DOMPDF (bundled in the plugin — no server package needed), saves as summary-{id}-{timestamp}.pdf, returns the download URL.

1
Pass a post or product ID (or both)At least one is required. Providing both creates a joint summary covering both entities.
2
AI summarizes the contentTitle + body go to the AI proxy. Summary returns.
3
DOMPDF renders the PDFSaved to uploads/tp-ai-pdfs/summary-{id}-{timestamp}.pdf. Download link in the navigator output.
ParameterValue
-post_idWordPress post ID — required if -product_id is not provided
-product_idWooCommerce product ID — required if -post_id is not provided. Both can be used together.
Output filePDF saved to uploads/tp-ai-pdfs/ with timestamped filename — URL returned in navigator
PDF engineDOMPDF, bundled with the plugin — no external service, no server-side package required
RequiresWooCommerce is only needed if -product_id is used — post-only summaries work without it
Can be used in

Real example

You hired a new content editor. You want them to read your archive — but you have 200 posts totalling 400,000 words. You build a macro: filter post -status=publish -category=editorialfor_each: ai summarize -post_id={{item.id}} → collect every pdf_url. Run it Friday afternoon.

Monday morning, the new editor has 200 one-page PDFs in a folder. They skim 200 summaries in two hours instead of reading 400,000 words in two weeks. They show up to the first editorial meeting with actual opinions on your voice and prior coverage.

Goes further with TrueCommander

Ready?

Summarize your archive. Ship PDFs.

This is one of 91 commands. All included with every license.

Cookies. The short version.

Essential cookies keep the cart and theme working. Analytics only fire if you say yes. Read our policy.