The WP Project Manager alternative for kanban backed by CPTs
WP Project Manager from weDevs is a full PM suite with kanban, gantt, milestones, and tasks in its own data model. SleekView renders kanban (and tables and feedback boards) over your existing CPTs and ACF or Meta Box fields, with edits writing back to the post.
♾️ Lifetime License available
PM suite vs data-views plugin: two different shapes
WP Project Manager from weDevs is a long-running, well-built project-management plugin for WordPress. It ships kanban boards, gantt charts, milestones, task lists, time tracking, comments, file attachments, and integrations across the weDevs ecosystem. The recent versions add AI-assisted task creation and summaries on top of that base. The data is its own (projects, task lists, tasks, milestones, comments) stored in custom tables managed by the plugin.
SleekView is not a project-management product. It is a data-views plugin: point it at a post type, configure columns or kanban groups or feedback cards, and render that data as a view. Kanban is one of several view types alongside tables and feedback boards, all reading the same CPT and ACF or Meta Box fields. There is no separate project entity; the cards are posts the rest of WordPress already knows about.
That makes the choice a question of what is being built. A team running real PM workflows with milestones, gantt timelines, time tracking, and comments is what WP Project Manager is for. A view over data that already lives in WordPress (roadmaps, releases, editorial pipelines, leads) rendered as a kanban among other view types is what SleekView is for. The overlap is thin: kanban over data that could plausibly live as a CPT or as plugin task rows.
Workflow
How a WP Project Manager board becomes a SleekView kanban
Identify projects that are really CPT lists
Create matching CPTs
Import existing tasks
Embed the SleekView kanban
Comparison
SleekView vs WP Project Manager at a glance
Differences
What changes when you move off WP Project Manager (weDevs)
The WP Project Manager (weDevs) way
- Tasks live in plugin-owned tables, not your post types
- Designed as a full PM suite, not a view layer
- ACF and Meta Box are not native on the task model
- Cards are not posts, so REST and theme queries miss them
- Strong on internal PM, weaker on public-facing data views
The SleekView way
- Kanban over any post type you already have
- ACF and Meta Box on cards, filters, and grouping
- Same CPT also as tables and feedback boards
- Drag-and-drop edits write back to the post
- Embeds via shortcode or Gutenberg block on the frontend
Features
Three things that actually change how you work
Cards are posts, not project tasks
WP Project Manager stores tasks in its own tables and treats projects as standalone entities. SleekView renders kanban cards from your CPTs, so each card is a regular WordPress post the theme, REST API, and other plugins already see and update.
Multiple view types over one CPT
WP Project Manager is shaped around projects, with kanban and gantt as views inside that model. SleekView's kanban is one of several view types over a CPT, alongside tables and feedback boards, so the same data renders multiple ways with no duplication.
ACF and Meta Box on cards
SleekView reads ACF and Meta Box fields directly onto cards, into filters, and into grouping. WP Project Manager exposes its own project and task fields; mapping ACF data onto cards needs custom integration work or a bridge.
Migration
When to move from WP Project Manager to SleekView (and when not to)
1. Decide if cards should be posts
If the cards are real records (roadmap items, releases, content, leads) that other parts of the site need, they want to be CPTs. For internal PM workflows with milestones, time tracking, and comments, WP Project Manager remains the better fit.
2. Create the matching CPT
For each WP Project Manager project that is really a list of records, create a CPT with ACF or Meta Box fields for the card details (status, owner, dates, description).
3. Import the relevant data
Export the relevant tasks from WP Project Manager and import them into the CPT with WP All Import or a similar tool. Map each task field to its CPT or ACF or Meta Box equivalent.
4. Render with SleekView
Configure a SleekView kanban over the CPT, grouped by the status field. Embed it on admin or frontend pages. Keep WP Project Manager installed for any genuine PM workflows that still need its full feature set.
Audience
Where SleekView fits and where WP Project Manager fits
Public-facing roadmaps and changelogs
Roadmap items and releases want their own URL, schema, and ACF fields. As CPTs in SleekView, they get a kanban view in admin and a public render on the frontend, all from the same data.
Editorial pipelines and content workflows
Content that already exists as posts (articles, case studies, releases) does not benefit from being copied into a separate task system. SleekView renders the existing CPTs as a kanban directly.
CPT-driven directories and listings
When the cards are records (leads, members, services, products) that the rest of the site also queries, they want to be CPTs. SleekView renders them as kanban, table, or feedback board over the same data.
The bigger picture
Why product shape matters more than feature count in the PM vs views debate
WP Project Manager and SleekView's kanban look similar in screenshots (columns, cards, drag-and-drop) but the products underneath are different shapes solving different problems. WP Project Manager is a project-management application that lives inside wp-admin. It ships its own data model (projects, task lists, tasks, milestones, comments, time entries), its own UI for editing those records, and a wider PM feature surface including gantt charts and reporting.
The kanban is one view inside that product, not the product itself. SleekView is a view layer over WordPress data: the data already exists as a post type, structured with ACF or Meta Box, and the kanban is one of several ways the team wants to look at it. Picking the wrong shape is more painful than picking the wrong feature.
A team buying SleekView to run internal PM workflows finds the PM features missing on purpose, because data rendering is not project management. A team buying WP Project Manager to render a public roadmap finds itself fighting to surface task data into the rest of WordPress, because plugin tables are not posts. The honest answer is that the two products only compete in a thin overlap (kanban over data that could plausibly live as a CPT or as plugin tasks).
Outside that overlap, the choice is not better-or-worse; it is which data model matches how the data actually wants to live. A useful gut check: if every other plugin and every theme template needs to read these records, they should be posts and SleekView is the right view layer. If the records are private team workflow that needs PM features around them, they should be plugin tasks and WP Project Manager is the right home.
Questions
Common questions about switching from WP Project Manager (weDevs)
No. WP Project Manager is a full PM suite with milestones, gantt charts, time tracking, comments, and file attachments. SleekView is a data-views plugin, not a PM app. The replacement story is specific: cases where the WP Project Manager board is really a list of records that should live as CPTs, where SleekView renders the kanban view over the actual posts.
No. Those features are intentionally outside SleekView's scope. SleekView focuses on tabular, kanban, and feedback views over CPTs. Sites that need gantt timelines or built-in time tracking are better served by WP Project Manager or a dedicated PM tool.
Yes. They do not share storage, hooks, or rendering. A team can run WP Project Manager for internal projects with PM features and SleekView for CPT-backed roadmaps, releases, or feedback boards. They cover different shapes of work and rarely collide on the same data.
In custom database tables created by the plugin (projects, task lists, tasks, comments, time entries). They are not WordPress posts, which is why ACF and Meta Box do not naturally apply and why the rest of WordPress's post-aware tooling does not see them.
As regular WordPress posts in whichever CPT the view points at. The kanban is a rendering of those posts grouped by a status field. Standard WordPress post hooks, capabilities, and queries all apply.
WP Project Manager has added AI-assisted task creation and summaries inside its PM context. SleekView does not duplicate that; AI inside WordPress is SleekAI's job (chat, content gen, alt text). Sites that want both can run SleekAI alongside either WP Project Manager or SleekView, since SleekAI is independent of the views layer.
Yes. Drag a card to a new column and SleekView writes the new value to the underlying status field on the post. Permissions follow standard WordPress roles, so any user with edit-post on the CPT can move cards.
Yes. That is the SleekView model. The kanban, the table, and the feedback board are three views over the same CPT and fields. Define the data once, render it three ways with different SleekView configs and embed each where it fits.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout