 To convert ideas into reality, we might need a team with varied skills working and collaborating around different types of assets. My name is William and I want to show you an example of collaboration using GitLab. Consider this scenario. We have these folks where one of them is a designer. His day-to-day activities involve working and creating different types of assets, like wireframes, mockups, and high quality images. And in the same team, a developer who works all day long, mostly with text files or code. And we need these two folks to collaborate and create a landing page. Let's start this journey as a designer. I am the designer now. I want to kick off the landing page creation, so in GitLab I create a new issue. I give it a name, explain the goal, and assign it to the developer who will code the site. And once I submit the issue, then I click on Designs tab, and here I can upload high quality images, being one of them the website mockup. These assets are now under version control. Remember, in this story, right now I am the designer, and these images are the input for the developer to start working creating the site. Now in the team, we can start discussions on the designs by clicking on the image on the exact location you would like the discussion to be focused on. Alright, so now let's switch roles. And I am the developer now. In GitLab, I can see I have an issue assigned. I can also see the designs and understand better what's expected from me to code. But wait, I can see that there is one mockup and two images. It's not clear to me which one of those should I use. So in the discussion, I can ask this question to the designer and get his answer right there in the mockup of interest. Good, the designer clarified my doubts. Now as a developer, I can move on and start doing what I know best. From the same issue page in GitLab, I can create a branch and a merge request in one single click from where I can fire up the web IDE and without leaving GitLab work in the page code. Here I have uploaded the image assets to the repo. There you go. That's Han Solo. I can go on and change the image path, observe the diff in the code, and commit to the branch. Good, I have GitLab CI configured. So once I commit and the changes are merged, this will start my pipeline where I can see from here it succeeded. It was successful, so that's great. It means I didn't break anything while doing these changes. Let's see the result. Looks nice. It has the image the designer wanted to use. Okay, so wrapping up, in this quick example, the team could manage and collaborate around assets and files of different types. This collaboration fits in the development practices and patterns such as branching, version control, merge request, and so on. It made it easier to move faster, having communication available at every level. All of these capabilities can lead to more efficient teams in turning ideas into reality. Stay tuned and let's continue learning at GitLab.