Patch’s clipboard
What is actually running under the hood?
This page is the public map of the Lab. It separates what WordPress handles, what WooCommerce adds, and what still depends on infrastructure and people.
The workload map
One website, several systems doing different jobs.
WordPress
- Pages and reusable block patterns
- Posts, categories, tags, and archives
- Media library and galleries
- Editor accounts and publishing workflow
WooCommerce
- Products and collections
- Cart and checkout
- Orders and customer accounts
- Store policies and fulfillment handoff
Infrastructure and people
- Hosting, TLS, backups, and updates
- Uptime Kuma endpoint checks
- Human investigation and recovery
- Packet containment procedures
Ping’s live signal
Monitoring tells us when to look, not what the whole story is.
Uptime Kuma checks whether configured endpoints answer, tracks response time, and watches HTTPS certificates. It does not submit forms, confirm email delivery, read every page, or judge the visitor experience.
The publishing loop
WordPress earns its keep when content keeps moving.
1. Draft
Build with headings, images, galleries, forms, product blocks, and saved patterns.
2. Review
Preview on desktop and mobile, check links, and keep uncertain case studies as drafts.
3. Publish
New posts flow into Query Loops, archives, search results, and the homepage automatically.
4. Watch
Ping watches availability. Patch maintains the system. Packet keeps everyone humble.
PACKET’S NOTE: A ROLLBACK PLAN IS JUST A TIME MACHINE WITH BETTER LABELS.
WordPress here. Business pricing there.
The Lab documents how this platform works. SloanOps.com remains the source for current services, pricing, and production website work.