- Best Practices for Grouping Wireframes in myBalsamiq
- Using a Naming Scheme within a Project
- Using Multiple Projects
- I Did Not Receive the myBalsamiq Confirmation Email. What Can I Do?
- Site Owner and Site Settings FAQs
- Can I Make My Project Read Only for Project Members?
- Can I Use myBalsamiq with Atlassian Jira or Confluence?
- Our myBalsamiq Site Owner Left the Company. How Can I Reclaim Our Company's Site?
- Clearing Your Flash Cookies
- myBalsamiq Editor Keeps Asking Me about Storage Settings. How Do I Stop the Alert from Appearing?
- myBalsamiq Doesn't Remember Me.
- How to Consolidate Email Accounts in myBalsamiq
- How Do I Leave a myBalsamiq Site?
- How Do I Move a Mockup from One myBalsamiq Project to Another?
- Does myBalsamiq have Autosave?
- My Wireframes Are Stuck On 'Generating Image'
- Oops! I Accidentally Deleted a Mockup From My myBalsamiq Site
- The Total Project Count Doesn't Match Visible Projects
Best Practices for Grouping Wireframes in myBalsamiq
A few people have asked us what the best way to group sets of wireframes together in myBalsamiq is.
This document offers a couple of suggestions.
Using a Naming Scheme within a Project
A simple way to group wireframes that are related to the same feature or section of a website is to prepend each mockup with the name of the feature.
For example, in the project below we named all the wireframes about our settings page starting with "Settings - "
This approach has the advantage of keeping everything in a single project, which is cheaper and easy to manage (once you invite your project members you're all set).
The downside of this approach is that the project might fill up with lots and lots of wireframes, making it harder to navigate.
Using Multiple Projects
Another, complementary idea is to use multiple projects, one per feature or section of a website.
For example, in our own myBalsamiq site, we have projects that have to do with our wireframing editor (in red) and other projects related to myBalsamiq (in green).
Using a consistent book design and naming scheme makes projects easy to find.
This approach has the advantage of keeping the number of wireframes inside each project smaller and thus more manageable, but has the downside of being potentially more expensive in the long run and a little harder to manage in terms of project members, as you will have to invite the appropriate project members to each feature-project.