SleekView Kanban for Basecamp for WordPress
Basecamp for WordPress mirrors projects, to-do lists, and to-dos into custom tables. SleekView Kanban reads those tables and groups to-dos by list or by completion state, with assignee and due date shown on every draggable card.
♾️ Lifetime License available
Basecamp to-dos as a board inside the WordPress admin
Basecamp for WordPress mirrors your account into a set of custom tables. To-dos live in basecamp_todos with id, title, content, todolist_id, assignee_id, due_on, completed, and app_url on every row. To-do lists sit in basecamp_todolists, projects in basecamp_projects, and people in basecamp_people. The plugin admin shows a flat list of to-dos sorted by sync timestamp.
SleekView Kanban reads those same tables and groups basecamp_todos by todolist_id so each Basecamp to-do list becomes a column. For a simpler split you can group by completed and get a two-column Active vs Done board across the entire project. Card fronts show the title, the assignee name joined from basecamp_people, the due date when present, and the project name from basecamp_projects.
Dragging a card writes back to the grouping column, so a drop from To do to Done flips completed and the next sync pushes the change to the Basecamp API. To-dos with no assignee land in the column they belong to and render a muted Unassigned chip on the card. Archived to-dos are filtered out by default through the trashed column so the board only shows active work.
Workflow
From basecamp_todos to a board in four steps
Point SleekView at the Basecamp tables
Pick the column that becomes columns
Choose what shows on each card
Enable drag and write-back
Sample board
Sample Basecamp for WordPress to-dos board
Comparison
Default Basecamp for WordPress vs SleekView Kanban
Default Basecamp for WordPress
- Synced to-dos appear in a flat admin list sorted by last sync time, not by list
- No drag-and-drop in WordPress, you have to log in to Basecamp to move items
- To-do list grouping that Basecamp uses is missing from the admin display
- Cards cannot combine assignee and due date and project on a single line
- Embedding the to-dos on a frontend page for clients is not supported
SleekView Kanban
-
Group cards by
todolist_idto mirror Basecamp lists in one click -
Two-column Active vs Done board by grouping on
completedinstead -
Card fronts show
title,assignee_id,due_on, and project -
Overdue rows turn rose so slipped
due_ondates are visible -
Drag-and-drop writes back to
todolist_idorcompleted
Features
What SleekView Kanban gives you for Basecamp for WordPress
People joined to every card
basecamp_todos.assignee_id joins to basecamp_people so the card front shows the real name and avatar instead of a numeric ID. Filter by person to scope the board to one teammate for a focused weekly planning session.
Overdue surfacing built in
Compare due_on to today and color overdue cards rose. The same rule drives an overdue counter in each column header so project leads see how many to-dos slipped without opening individual rows from Basecamp.
Drag writes back to Basecamp
Moving a card to Done flips completed on the row and queues the change for the next Basecamp API push. The card stays in its new column locally so the team is not blocked by API timing or by sync schedule.
Audience
Where a Basecamp board inside WordPress is the right tool
Per-project status pages
Embed a project board on a private WordPress page so clients see Active vs Done without a Basecamp seat or a separate login.
One-on-one planning
Filter to one assignee and group by to-do list to run weekly one-on-ones from a single kanban URL with no extra prep.
End-of-week sweeps
Open the board grouped by completed and drag any straggler from Active to Done in seconds so projects stay tidy.
The bigger picture
Basecamp data is fine, the view is the gap
Basecamp's strength is calm collaboration, but the WordPress mirror flattens that into a long admin list and stops there. Teams who chose WordPress as their hub end up bouncing back to Basecamp every time they want to see flow across a project, even though all the data is already sitting in custom tables. SleekView Kanban removes that bounce.
Group by to-do list and the same columns the project lead set up in Basecamp render inside the WordPress admin, drag a card and the change writes back through the next sync push, embed the same board on a client portal page and stakeholders watch progress without a paid seat. Because the cards are tied to the source rows, anything updated in Basecamp itself shows up the next time the page loads and nothing diverges. Agencies billing clients out of WordPress, internal ops teams running their intranet on WordPress, and product teams whose roadmaps live in the CMS all benefit.
The board view is the way humans read project state, and now it lives where the rest of the work already does.
Questions
Common questions about SleekView Kanban for Basecamp for WordPress
Primarily basecamp_todos for the row per card, plus basecamp_todolists for column names, basecamp_people for assignee labels, and basecamp_projects for project context. SleekView only reads from tables Basecamp for WordPress already maintains, so it never calls the Basecamp API directly.
 Yes. completed gives a two-column Active vs Done board across the whole project. assignee_id gives a per-person board. Any column on basecamp_todos is a valid grouping field, distinct values become column titles in the order SleekView finds them on the first render.
 SleekView writes the new grouping value into basecamp_todos and fires the plugin write hook. The next sync push sends the change to the Basecamp API. The card stays in its new column locally so the team is not blocked while waiting for the round trip to complete.
 The local table updates immediately so the board reflects the change without a reload. The push to Basecamp happens on the plugin sync schedule. If you need instant pushes, switch the plugin to manual sync and call it from a SleekView post-drop hook to fire on every drop.
 Apply a SleekView filter on project_id before the grouping. The filter narrows the rows the kanban considers and the column counts adjust automatically. Save the filter as a named view so each project lead opens their own kanban URL with the right scope already applied.
 Yes. Drop the SleekView shortcode on any WordPress page and the same kanban renders. Combine it with a role filter so the client view excludes internal-only to-do lists. Mark the embed read-only and the client cannot drag cards, only watch progress as your team updates them.
 It still appears as a card in the appropriate column. The due-date pill simply does not render. Overdue rules ignore the card so it never turns rose. Filter where due_on is null if you want a saved view that surfaces all to-dos without a date for the team to triage.
 No, not by default. SleekView filters where trashed is false so the board shows only active rows. Toggle the filter off when you need a board of trashed work for an audit, or build a separate saved view that scopes the board to a recovery window.
 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