B2B · CMS · Business operations
Industrial CMS
From a presentation website to a managed B2B product
An independent platform combining the public website, catalog, inquiries, publishing and analytics. Staff use shared workflows instead of disconnected manual operations.
- Core workflowsCatalog · inquiries · publishing
- 3
- Enforced access roles
- 7
- Controlled publishingChanges go live after acceptance
- Draft → Live
Catalog, inquiries and publishing in action
INTERACTIVE PRODUCT DEMO
Try the CMS workflow
A portfolio-safe interactive reconstruction of the production administration workflow. Click through products, publishing, inquiries and analytics. All records and metrics shown below are synthetic demo data; no production backend or customer data is exposed.
Draft → Publish
Edits leave the published version intact until acceptance. Publishing creates a revision, updates live content and the audit log, then invalidates cache.
Inquiry lifecycle
New → Viewed → In Progress → Proposal Sent → Closed / Rejected. Search, filters, product association, notes and status history support the process through to a decision.
Product analytics
Product interest, inquiry funnels, form stages and PDF downloads are visible in a first-party dashboard, informing catalog and inquiry decisions.
Decisions and ownership
Product scope
Defined catalog, page, media, document, job and multilingual-content structure. Designed the public interface and administration as parts of one product.
UX and workflows
Designed contextual editing, independent drafts and controlled publishing. Separated access to content, catalog, inquiries and analytics workflows.
Releases and quality
Used AI during implementation; owned requirements, acceptance criteria, functional and regression checks, responsive behavior and deployment.
Validation and acceptance
How to verify the result
- Validation covered editing, publishing, permissions, inquiries, analytics, locales, responsive UI and cache invalidation.
- The portfolio includes an interactive administration reconstruction; a full live/staging walkthrough is available on request.
Technical details
Image optimization: in one example, 2.75 MB PNG → ~200 KB WebP, approximately 93% smaller.
Custom PHP 8.4 MVC/DI application with Controller → Service → Repository → Database separation and server-side rendering.
29 database tables and ≈188 PHP source files cover products, pages, media, documents, jobs, inquiries, analytics, revisions, permissions and help.
Transactional publishing follows Revision Snapshot → Live Update → Audit Entry → Draft Removal → Cache Invalidation.
Security and operations include CSRF, RBAC, Argon2id, rate limiting, sanitization, MIME validation, protected uploads, diagnostics, migrations, backups and APCu → Memcached → File Cache fallback.
Privacy design avoids Google Analytics, external tracking pixels, raw IP storage, PHP session persistence and browser fingerprint storage.
Technology
- PHP 8.4
- JavaScript
- MySQL
- SSR
- RBAC
- AVIF / WebP
- APCu / Memcached