Who this comparison is for
ProjectBoard highlights
- Built-in visibility modes + customer-only gating and signed file delivery (FileVault)
- Update scheduling + event-driven notifications (OccupancyCore → delivery apps)
WordPress (Custom “Projects” CMS) highlights
- Flexible CMS theming and content editing ecosystem
- Massive plugin marketplace (quality varies)
Capability matrix
| Capability | ProjectBoard | WordPress (Custom “Projects” CMS) | Notes |
|---|---|---|---|
| Public project pages | Full | Full | Both can publish public content |
| Customers-only updates and gated viewing | Native | Add-on | Often via membership plugins/custom code |
| Brochures (PDF) with signed links + access rules | Native | Add-on | Usually via media library + access plugins |
| Update scheduling (publish_at) + cron publishing | Full | Partial | WordPress schedules posts; portal rules require extra work |
| Assignment-aware audience resolution | Native | OccupancyCore resolves assigned customers | |
| Event-driven delivery to in-app/email/WhatsApp | Full | Partial | Requires multiple plugins + glue integrations |
| Audit logs for publish actions and delivery | Full | Partial | Plugins exist; usually not unified |
| External webhooks (signed, retries, logs) | Native | Partial | Requires plugins/custom endpoints |
Total cost of ownership
For a marketing-only projects page, WordPress is fine. For a real portal (gating, assignments, signed downloads, notifications, audits), ProjectBoard reduces plugin sprawl and custom maintenance by providing portal primitives and event-driven integrations out of the box.
Assumptions
- Need customer-only updates and controlled brochure access
- Need reliable notifications to assigned customers
Migration plan
From WordPress projects pages · Import core project content → attach files in FileVault → publish updates via ProjectBoard → optionally push public events back to WordPress via webhooks
-
1
Create ProjectBoard projects and port over descriptions/location/cover media
-
2
Upload brochures and galleries to FileVault and attach with visibility rules
-
3
Enable webhooks to update your WordPress site for public pages (optional)
Security
- Centralized RBAC + visibility modes for projects/updates
- Signed file delivery and retention controls via FileVault
Evidence & sources
| Claim | Value | Source |
|---|---|---|
| Gated downloads and signed links | Brochures and attachments are delivered via FileVault signed links with permissions | product_docs |
About ProjectBoard
ProjectBoard turns every project into a shareable, structured page with a clear timeline. Add descriptions, locations, amenities, cover media, image galleries, and brochures stored securely in file-vault.
Post progress updates on a schedule or publish instantly. Updates support categories (configurable per workspace), attachments, and visibility rules (public, customers-only, internal). When an update is published, ProjectBoard emits events so other apps can resolve audience and deliver notifications—without ProjectBoard needing to know who the customers are.
Use it for construction projects, property developments, events, product launches, internal initiatives, and any workflow that needs a “project home” plus an update stream.