Dev Blog

Dev Blog

Real product updates plus practical articles for product and operations teams.

Product updates

Real product changes, ordered so the most important updates come first.

Mar 23, 2026 - 1 min read

New: import Trello boards via JSON in Kanban Studio

You can now migrate lists, cards, labels, and checklist data from Trello with a guided import flow and safety validations.

Ethan Navarro - Dev

#trello#import#migration#boards
Read post: New: import Trello boards via JSON in Kanban Studio

Mar 20, 2026 - 1 min read

Now in Kanban Studio: public boards

You can now share boards with a public link to show progress, roadmap updates, and current work status without access friction.

Ethan Navarro - Dev

#updates#public-boards#collaboration#product
Read post: Now in Kanban Studio: public boards

Mar 13, 2026 - 2 min read

New user identity with a unique userTag

We improved user identity so every profile is clearer, easier to recognize, and more consistent across the platform.

Ethan Navarro - Dev

#updates#profiles#collaboration
Read post: New user identity with a unique userTag

Articles

Guides and SEO content to go deeper on workflows, comparisons, and best practices.

Editorial notes

Each post focuses on a concrete change and explains practical impact for teams running boards, automations, and collaborative workflows.

We publish decision context, scope, tradeoffs, and next steps so you can plan adoption without guesswork.

When updates affect security, performance, or AI-assisted operations, we include references and validation guidance for your environment.

If an update changes roadmap priorities, we explain which options were evaluated, which tradeoffs were rejected, and why the final decision was made.

We also add implementation notes so product, engineering, and ops teams can validate impact in staging before broad rollout.

Suggested checklist when reading updates

  • Identify whether the change affects active boards, automations, or team routines.
  • Review rollout risk, compatibility impact, and migration steps before enabling it globally.
  • Capture one concrete follow-up action so updates become execution, not passive reading.

Changelog editorial standards

We clearly separate released changes, controlled experiments, and planned work so teams can interpret status correctly.

When updates introduce external dependencies, we document security implications, operational cost, and expected maintenance scope.

If a feature changes existing behavior, we include migration notes to reduce regressions for active teams.