Task Guides
Purpose
Task guides are reusable, user-facing workflow pages for repeated operational actions in Pyle.
They are different from concept pages:
- concept pages explain what a feature is
- task guides explain exactly how to complete one practical workflow
What A Task Guide Is For
Use a task guide when a reader wants to do one thing right now, for example:
- create a product
- classify a product
- configure product groups
- export catalog setup
Task guides should be short, practical, and written for operators rather than developers.
Quick checklists are a lighter companion format for high-frequency troubleshooting cases.
- use a full task guide when the reader needs the full workflow and explanation
- use a quick checklist when the reader needs a fast triage pass before opening the full guide
Writing Rules
Every task guide must:
- start with the business outcome, not the code concept
- name the real admin entry point the user clicks into
- state prerequisites and missing setup clearly
- distinguish direct user steps from automatic downstream behavior
- explain what changes after the task is saved or completed
- warn about the most common failure modes for that exact workflow
Avoid:
- generic feature explanations that belong in concept pages
- code terms such as models, controllers, observers, or migrations
- vague instructions like "configure this as needed"
- invented packaged UI flows that do not exist in the repo
Evidence Standard
Research task guides in this order:
- packaged admin screens and dialogs
- storefront pages affected by the task
- import/export screens
- ERP or sync touchpoints when they change how the task works
- framework code only to confirm hidden rules or side effects
Required Page Structure
Every task guide should use this structure:
# <How To ...>
## What This Task Does
## Before You Start
## Steps
## What Happens Next
## Common Mistakes
## Related GuidesSection Expectations
What This Task Does
Explain:
- the outcome the user is trying to reach
- when this task is the right one
- what successful completion looks like
Before You Start
Explain:
- permissions
- records or setup that must already exist
- whether the task is direct UI work, Excel work, or generated/system-assisted work
Steps
Use numbered operational steps:
- where to go
- what to click
- which fields matter
- what to save or confirm
Only include steps the user can actually perform in the packaged product.
What Happens Next
Explain:
- what updates immediately
- what affects storefront browsing, product pages, or shopper options
- what may require background rebuilds, syncs, or related setup to become visible
Common Mistakes
List the most important workflow-specific problems such as:
- missing prerequisite records
- trying to delete or disable something still in use
- expecting storefront changes from a configuration that is only indirect
- using the wrong screen when the packaged product manages the workflow elsewhere
Related Guides
Link to:
- the parent domain page
- relevant end-user concept pages
- adjacent task guides in the same workflow chain
Current Catalog Task Guides
- How to create and publish a product
- How to classify a product with type, category, brand, and collection
- How to create a category structure for storefront navigation
- How to create a collection and add product groups
- How to configure product groups for a collection
- How to export catalog setup to Excel
Current Pricing Task Guides
Current Customer Task Guides
Current Inventory Task Guides
- How to create and maintain a vendor
- How to configure, run, and troubleshoot vendor data feeds
- How to review vendor catalog items and resolve them
- How to create or update an inventory location
- How to review vendor mappings
- How to review mapping attempts
- How to bulk edit vendor mappings with Excel
Current Fulfillment & Shipping Task Guides
- How to export and import shipping configuration
- How to choose a shipping service on an order
- How to review a fulfillment request
- How to manage shipping date calendar rules
Current Order Lifecycle Task Guides
Current Payments & Billing Task Guides
Current Tax & Territory Task Guides
Current Supporting Platform Capabilities Task Guides
Current Operations And Troubleshooting Task Guides
- How to troubleshoot a failed ERP sync
- How to troubleshoot a failed import
- How to troubleshoot a payment that did not settle an order
- How to troubleshoot why a promotion is not applying
- How to troubleshoot why a shipping service is not available
- How to troubleshoot why a product is missing from the storefront
Current Operations And Troubleshooting Quick Checklists
- Quick Checklist: Product Storefront Visibility
- Quick Checklist: Promotion Application
- Quick Checklist: Shipping Service Eligibility
Roadmap Status
All current top-level domains in the first-pass documentation roadmap have now been drafted.
The active next pass is cross-domain troubleshooting and recovery guidance for operators. The first troubleshooting batch is now in place.
Sources
packages/admin/routes/web.phppackages/admin/src/Livewire/Admin/Productspackages/admin/src/Livewire/Admin/Productpackages/admin/src/Livewire/Admin/Settings/Categoriespackages/admin/src/Livewire/Admin/Settings/Collection/ProductGroupspackages/admin/src/Livewire/Admin/Tools/Excelpackages/storefront/routes/web.phppackages/storefront/src/Livewire/Storefront/Productpackages/storefront/src/Livewire/Storefront/Categorypackages/storefront/src/Livewire/Storefront/Brandpackages/admin/src/Livewire/Admin/Order/Shipmentspackages/admin/src/Livewire/Admin/Settings/CalendarRulespackages/framework/src/Http/Controllers/Api/Admin/FulfillmentRequestsController.phppackages/framework/src/Http/Controllers/Api/Storefront/ShippingController.phppackages/storefront/src/Livewire/Storefront/Cart/Shipments