Case study WordPress / Service operations
Digitizing Depot
A WordPress service storefront supported by separate PHP/MySQL production operations and a custom guided-help plugin.
Problem statement
Make a broad production offer easier to enter, while keeping catalogue content, customer enquiries, and staff production work in their appropriate systems.
Proof / A quick look
See the product before the detail.
01 / Overview
The brief.
Digitizing Depot’s public website and production administration are separate systems serving the same business. The WordPress website presents apparel, patches, sports products, and services; the PHP/MySQL operations application handles the detail after a request reaches staff. My work covers catalogue structure, quote entry, guided help, and the workflows behind production handoffs. Together, those surfaces give visitors a way to explain a request and staff the context to take it forward.
02 / Situation
What was already true.
The public offer includes apparel, patches, sports apparel, digitizing, vector work, web services, pricing, and portfolio context. A quick-order or quote route helps visitors turn that breadth into a specific request. Separately, the operations application contains the customer, employee, designer, salesman, invoice, and production records staff need to do the work.
03 / Tension
The competing needs.
The service range needs enough detail to communicate capability and enough structure to help a new buyer choose a starting point. Staff need a different level of detail around queues, files, invoices, and customer records. WordPress content publishing and PHP production administration each have their own interface and account context, so both sides need clear entry points.
04 / Decision
The choice that set the shape.
Use service families, public pricing, portfolio context, and a quick-order action as the public organising structure. Keep production administration separate, and add a WordPress-native guided-help plugin that answers common questions through authored choices and directs the visitor toward an appropriate next step.
05 / Responsibilities
What I designed and built.
My work covers the public website’s service and catalogue structure, responsive page experience, enquiry entry points, and the Ask Depot guided-help plugin. On the operations side, the implementation includes the PHP administration paths for production queues, invoice and file handling, exports, and customer/staff records. My responsibility spans the presentation of the offer and the operational stages staff use to organise work, handle files, and follow commercial records across these two applications.
06 / Architecture
The implementation behind the interface.
WordPress manages the public website. The custom digitizing-depot-assistant plugin provides the guided-help experience through WordPress hooks, browser assets, and an authored answer structure. A separate PHP/MySQL operations application contains route families for production queues, invoices, files, exports, customers, employees, designers, and salesmen. Public content and production records remain separate application concerns: WordPress supplies the service catalogue and enquiry presentation, while PHP screens organise the records and actions used in the ongoing production workflow.
07 / Access control
Who can do what.
core/Auth.php provides the session-based administrator gate for the operations application. Inside that surface, route families organise customer, employee, designer, and salesman records alongside production queues, files, invoices, and exports. WordPress manages public content in its own publishing environment. The two applications keep content administration and production administration in their respective account contexts.
08 / System
How the pieces fit.
A visitor narrows the request through a service or product family, consults pricing or portfolio examples, and starts a quick order or enquiry. Guided help offers another route through common questions. Once work reaches staff, production queues, assignments, files, invoices, and exports provide the operational context. The public site introduces the offer; the operations application supports the ongoing job.
09 / Evidence
What the shipped interface can show.
The public catalogue presents product and service families beside pricing, portfolio links, and enquiry actions. Ask Depot’s WordPress plugin packages its authored answers, hooks, and browser assets into a guided-help experience. The PHP administration screens provide production queues, file and invoice handling, exports, and customer/staff record management, making the stages behind a service request concrete.
10 / Next iteration
The next question.
Compare the terminology customers use in an enquiry with the public category labels and the production queue names. Review where a request needs additional explanation before staff can act, and make that handoff clearer in the public form and guided-help content.
11 / Feature list
Features.
- WordPress service and apparel catalogue
- Pricing and portfolio context
- Quick-order and enquiry routes
- Ask Depot guided-help plugin
- Separate PHP production administration
- Production queues and file handling
- Invoice and export workflows
- Customer, employee, designer, and salesman records
Gallery
Project images.
Open an image to view it. The full-image link still works when scripts are unavailable.