superpowers-sage:acorn-routes

To define Acorn routes in a WordPress Sage theme, you structure route definitions within routes/web.php and routes/api.php, utilizing route groups and prefixes to isolate logic from standard WordPress content and prevent permalink conflicts.

Middleware for Acorn routes in Sage is applied through the RouteServiceProvider, allowing you to assign middleware to route groups defined in routes/web.php and routes/api.php for structured request handling.

Yes, you can scaffold Laravel-style controllers for Acorn routes using the provided CLI script, which generates Resource, API, and Invokable controllers to quickly wire up web and API endpoints.

A RouteServiceProvider is required for Sage Acorn to register route files, load definitions from routes/web.php and routes/api.php, and apply middleware, ensuring your custom routing coexists safely with WordPress.

Prevent Acorn route conflicts with WordPress permalinks by using route prefixes, which isolate your custom endpoints from core WordPress content routing and ensure requests map correctly to your Sage controllers.

Acorn routing requires an Acorn-enabled WordPress Sage environment and supports local development through Lando, providing a sandbox to test route definitions, middleware, and scaffolded controllers.