Who this comparison is for
ProjectBoard highlights
- Canonical project records, categories, typed attributes and visibility
- Dedicated project update lifecycle and public update template system
- Built-in project/update analytics and Velaxe integration APIs
WordPress (Custom Projects CMS) highlights
- General-purpose page/post publishing and media library
- Themes, roles and plugin ecosystem
Capability matrix
| Capability | ProjectBoard | WordPress (Custom Projects CMS) | Notes |
|---|---|---|---|
| Structured project domain model | Native | Partial | ProjectBoard has first-class project, category, media, attribute and update entities. |
| Public content publishing | Full | Full | Both support public-facing content workflows. |
| Media library | Full | Full | Both manage media; ProjectBoard binds media directly to project records and visibility. |
| Scheduled publishing | Full | Full | ProjectBoard schedules project updates; WordPress supports scheduled publishing for CMS content. |
| Project-specific engagement analytics | Native | Partial | ProjectBoard captures project/update sessions and interaction events. |
| Workspace app capability API | Native | Partial | ProjectBoard exposes canonical Velaxe operations and context. |
| Bridge v2 external integration credentials | Native | Partial | ProjectBoard has per-connection HMAC credentials and operation controls. |
| General website/theme ecosystem | Partial | Full | WordPress is a broad general-purpose CMS platform. |
Total cost of ownership
ProjectBoard provides a focused project domain and workspace integration layer, while WordPress is flexible general web publishing infrastructure.
Assumptions
- Projects need reusable structured data as well as web presentation
- Connected workspace apps need canonical project operations rather than page scraping
Migration plan
From WordPress (Custom Projects CMS) · Create canonical projects in ProjectBoard → attach project media → publish updates and public update pages → use authorized capability operations for app/system integration.
-
1
Create ProjectBoard project records from current project content
-
2
Move project media into ProjectBoard-owned media collections
-
3
Publish future project progress through ProjectBoard updates
Security
- ProjectBoard visibility/RBAC and app-scoped storage
- Per-operation authorization for app and Bridge callers
Evidence & sources
| Claim | Value | Source |
|---|---|---|
| ProjectBoard product surface | Project-specific data model, publishing queue, public update templates, analytics and integration operations. | product_docs |
About ProjectBoard
ProjectBoard gives each workspace a structured source of truth for project content. Create project records with categories, locations, dates, visibility, type-specific attributes, cover media, galleries and supporting files.
Create rich project updates with summaries, categories, period tags, attachments and visibility controls. Publish immediately or schedule updates through the built-in publishing queue, then present published content through configurable public update pages with versioned templates.
ProjectBoard includes project and update analytics, activity history, media management, integration administration, Bridge credentials, ContextResolver capabilities and event publication. Authorized workspace apps can consume canonical project and update operations through Handler or RCP, while external systems can use Velaxe HMAC Bridge v2 with operation, IP, replay, timestamp and rate controls.