Step 1 Create a Project
Darren heard about Abstract and signed up. They created a Project and then invited Mika, their frontend engineer and Antonio, a fellow designer to the Project.
ProjectsProjects represent an area of work. If you are on a product team, you may want a Project for iOS, Android, or web. You may want separate Projects for your UI library and style guides, and a separate Projects for marketing work or sales materials. If you are a creative agency, each client contract could be a Project. How you set up your team’s Projects depends on how their work is organized.
You don’t always have to create a Project to begin. Someone on your team could start a Project and invite you to collaborate. Learn more…
Step 2 Import Files
Darren imports Sketch files by dragging and dropping them into the Project or by clicking the “add file” button.
MasterThese files are your Master files - your single source of truth. Each Project has a Master and can consist of one or several Sketch files. This way, everyone can look at the Master and use it as reference for their work.
Remember to always open your Sketch file from Abstract. This way, all changes made to your file will be tracked and recorded in Abstract. Learn more…
Step 3 Start a Branch
Darren wants to make some changes to the Sketch files they imported. So they start a new Branch.
BranchesBranches allow you to make a copy of the Master file while still being connected to the Master. It’s a safe space to explore, create, and iterate, without worrying about losing your original file. You can create as many Branches as you like!
You can Branch from two places: Master or another existing Branch. This is useful if you want to riff on someone else’s work that hasn’t yet been finalized. Learn more…
Step 4 Edit and Make Commits
Darren then opens the Sketch file from Abstract and edits it. After editing, they make a Commit and mention Antonio. Antonio reviews the design and has an idea. They create a Branch from Darren’s Branch to edit the file. This way, two designers can work on the same file without affecting the Master or worrying about overwriting each other’s work.
CommitsA Commit is like a “super save” with context. When you Commit, you write a short description of the edits you made. This way, your team can look at your Commit history and know what changes were made, when, and why.
Commit every time you make a change to your Branch like a new exploration, when you finish a chunk of work, or when you change direction. Learn more…
Step 5 Review Changes with Team
After editing the file, Darren notifies Mika and Antonio. Mika and Antonio jump in and add their comments.
Comments/AnnotationsAnnotating and leaving comments on a design simplifies the feedback process for your team. Use annotations to highlight specific areas of the file and share your feedback so the team knows exactly what you’re referring to. All feedback is collated with the design file, making it easy for the designer to incorporate it.
Make a Collection to share your work. All annotations and comments made on the designs will be reflected in the Collection. Learn more…
Step 6 Get Ready to Merge!
Darren makes more edits to their Branch. They also love Antonio’s new exploration and give Antonio the thumbs up to merge to their Branch.
MergeMerging is where the magic happens. It’s what brings all the separate edits together in one place. You can Merge two Branches and bring those Sketch files together in one place or, Merge to the Master. Completing a Merge will archive the Branch, where it can be reviewed or revived later.
Always get approval from a designer before Merging into their Branch. Most teams follow a process of getting approval from their design lead or team lead before Merging into Master. Learn more…
Master is updated!
Your Master file can be the single point of reference for the entire team. No duplicate files. No conflicted copy. No confusion.