processwire-templates

Guide ProcessWire front-end template development with output strategies and URL routing.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/webmanufaktur/pwaiworkflow --skill processwire-templates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: processwire-templates
Source: https://github.com/webmanufaktur/pwaiworkflow/tree/main/.agents/skills/processwire/templates
Command: npx skills add https://github.com/webmanufaktur/pwaiworkflow --skill processwire-templates

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides clear guidance and examples for structuring and rendering ProcessWire front-end templates, helping developers choose and implement the most effective output strategies.

Core Features & Use Cases

  • Output Strategies: Explains Direct Output, Delayed Output, and Markup Regions.
  • URL Segments: Details how to use template files for routing.
  • Pagination: Covers implementing pagination with MarkupPagerNav.
  • Bootstrapping: Shows how to use ProcessWire's API from external scripts.
  • Use Case: A developer needs to build a complex, multi-region website and is unsure whether to use direct output, delayed output, or markup regions. This skill helps them understand the trade-offs and implement the chosen strategy.

Quick Start

Explain the differences between ProcessWire's direct, delayed, and markup region output strategies.

Frequently Asked Questions about processwire-templates

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the difference between direct output, delayed output, and markup regions in ProcessWire?

ProcessWire output strategies differ in rendering flow: direct output echoes content immediately, delayed output buffers variables for layout assembly, and markup regions use placeholders to inject front-end template content into specific page sections.

How do I use URL segments for front-end routing in ProcessWire templates?

To use ProcessWire URL segments for front-end routing, configure your template file to accept segment parameters, allowing a single template to serve multiple page variations and handle custom routing logic without creating separate physical pages.

How do I implement pagination with MarkupPagerNav in ProcessWire?

Implement ProcessWire pagination with MarkupPagerNav by configuring your page selection query with a limit, then rendering the pager navigation markup to display front-end links for browsing multiple pages of results.

Can I bootstrap ProcessWire from an external PHP script?

Yes, you can bootstrap ProcessWire from external PHP scripts by including the core index.php file, which loads the ProcessWire API and allows you to manipulate pages and data outside the standard front-end template environment.

What are common pitfalls when designing ProcessWire front-end templates?

Common ProcessWire front-end template pitfalls include choosing an output strategy that complicates multi-region layouts, mishandling URL segment routing logic, and incorrectly configuring pagination limits within the page selection query.