Liberty Digitizing.

Liberty Digitizing combines an apparel and service storefront with an existing production operation. Customers browse garments, patches, sports apparel, and digitizing or vector services, then continue through a quote or customer account. Behind that public surface are quote and order queues, designer assignments, delivery files, invoices, and reporting. My work connects the public experience to those operational paths while respecting the existing PHP application and its separate staff portals.

The same brand serves someone choosing apparel and someone supplying artwork for embroidery or vector work. Public pricing, portfolio context, customer login, and quote requests sit beside the catalogue. Existing staff operations already distinguish work awaiting a price, production work in progress, and work ready for the next handoff.

A catalogue shopper needs product families and a quick route through the offer. A production customer needs to explain a job and return to its files or account. Staff need queue-level detail, assignment context, and commercial records. The implementation also needs to work with the established PHP database paths and independently authenticated portals that support the business’s daily operations.

Organise the storefront around named apparel and service lanes, with Get Quote and Customer Login as visible next steps. Connect the public and customer work to the existing operational states, and introduce shared PHP helpers where they fit while retaining compatible legacy mysqli paths.

My scope includes the public navigation, responsive storefront pages, quote entry, customer-facing account flow, and the PHP/MySQL connections behind the experience. The operational work covers quotes becoming orders, embroidery and vector queues, assignments, file handoffs, invoices, and the reports staff use to follow production and commissions. I also built the Ask Liberty guided-help widget, whose authored question-and-answer tree routes visitors to relevant service information or a human contact path.

Server-rendered PHP supplies the pages, with HTML, CSS, and vanilla JavaScript handling the browser layer. A newer core uses PDO-backed database access and shared request/session helpers alongside preserved mysqli-based legacy modules. Customer account pages use a session guard; the storefront and account share a shell, while administration, designer, and partner areas have separate page structures and authentication. Quote and order records connect to assigned production work, file slots, invoice records, and reporting. Ask Liberty reads an authored answer tree from include/chat_data.php, with assets/js/chat.js presenting the guided choices and answers in the browser.

Customer account access is session-gated through account/guard.php. The administrator, designer, and partner portals use separate authentication paths with different operational purposes. Administrators manage production queues and commercial records; designer-facing work centres on assigned production, and partner-facing work includes its own reporting context. Each portal provides an entry point suited to the work its users need to carry out.

A new buyer enters through apparel, patches, sports, or services and supplies quote context when the job needs pricing. Staff review the request, move it into an order or vector queue, handle unpriced and ready states, assign production, and attach files. Customer access, invoicing, performance reporting, and commission views support the continuing relationship after the initial form.

The storefront separates apparel, patches, sports, and service lanes, with public pricing, quote entry, and customer login close to the browsing journey. Staff screens expose quote-to-order operations, unpriced and ready queues, assignments, file handling, invoices, and operational reports. Ask Liberty pairs a PHP-authored content tree with a JavaScript widget that lets visitors follow questions to service information or contact.

Follow one apparel enquiry and one artwork job from the public form through pricing, assignment, file delivery, and the customer account. Use those observations to clarify labels and reduce repeated data entry at handoffs while retaining the information production needs.