TrelloPro is an independent guide to Trello for small teams that share boards and hand work to each other. I'm Nathan Cole, and I write it around one question: could someone who wasn't in the planning meeting open this board and tell who moves each card and what happens next? A missing owner or a vague handoff usually deserves attention before anyone adds another label or rule.
What the guides cover
- Boards & cards: naming and filtering labels, restoring archived cards, deleting a card or a whole board without losing work someone still needs, and exporting a board to JSON or CSV first.
- Trello basics: the keyboard shortcuts for moving around a board, pushing cards between lists, selecting several cards, filtering to your own cards and undoing a slip, plus how to switch single-key shortcuts off.
- Automation, Power-Ups & integrations: bringing Google Calendar into Trello with Planner or sending due dates out through a board's calendar link, and turning emails into cards from your Inbox address, a board address, Gmail or Outlook.
- Workspaces & sharing: creating a Workspace, moving boards into it, inviting members or adding a client as a guest on one board, and the board and collaborator limits on Free.
- Account & apps: deleting a Trello account through Atlassian account settings, what happens to your boards, Workspaces and paid plans, and the 14-day window in which you can still cancel.
How I write a Trello guide
I start with the people on the board. An example needs handoffs a reader would recognise: who archives the card, who joins as a guest, who still needs an export before a board is deleted. When automation comes up, the guide states the trigger and the action, because a rule nobody can read back becomes one more thing to maintain.
Plan limits go in wherever they change the answer. CSV export, a board's calendar link and Trello AI on incoming email all depend on the plan, and a board design shouldn't quietly assume tools you lack. When Trello changes a feature, I revise the steps and check whether the original workflow still benefits from it or needs a simpler arrangement.
About Nathan Cole
My role here is Trello workflow and team-operations editor. I write about board and list design, card templates and checklists, Butler rules and scheduled automation, and the permissions and recurring work a shared board has to carry. The setting I have in mind is a small team with little time for administration.
My starting questions are concrete: who moves the card, which action comes next, and whether a due date is a real commitment. I'm lightly skeptical of any system that needs its own weekly maintenance meeting, and I'd rather a checklist record a decision than stand in for one.
TrelloPro is an independent guide and is not affiliated with Atlassian. Trello is a trademark of Atlassian.