Don't Lose Your Stuff! Organizing your Game Development Content | Miko Charbonneau | Skillshare

Playback Speed


1.0x


  • 0.5x
  • 0.75x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 1.75x
  • 2x

Don't Lose Your Stuff! Organizing your Game Development Content

teacher avatar Miko Charbonneau, Creative Director, Designer, Writer

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Lessons in This Class

    • 1.

      Introduction

      1:19

    • 2.

      Installing Notion

      2:05

    • 3.

      Overview Page

      6:29

    • 4.

      Important Links

      1:08

    • 5.

      Documentation

      4:47

    • 6.

      Style Guides

      1:37

    • 7.

      Task Tracking

      2:57

    • 8.

      Source Control, Builds, Testing

      1:59

    • 9.

      Folder Hierarchy

      3:30

    • 10.

      Naming Conventions

      3:17

    • 11.

      External Assets

      1:12

    • 12.

      Conclusion

      0:58

  • --
  • Beginner level
  • Intermediate level
  • Advanced level
  • All levels

Community Generated

The level is determined by a majority opinion of students who have reviewed this class. The teacher's recommendation is shown until at least 5 student responses are collected.

46

Students

--

Project

About This Class

We always want more time to work on our games, and one way to achieve this is to organize your stuff! If you know where to find everything, you'll save yourself stress so you can focus on what you want to do: make games!


In this course, we'll use Notion to build an overview page for your game that covers the major aspects of the game development process. We'll also cover using Notion for task tracking and build management. Then in Unity, we'll show examples of creating a reusable folder hierarchy and naming convention plan that works for you.

This course is aimed at game developers in the Beginner category, however students at all levels might learn a few new tricks. The general concepts we cover in Notion can also be applied to creative projects other than games.

To start this course, you'll need a Notion account. We'll cover how to do that in the first lesson. If you prefer, you can use another note taking app and any game engine you wish to apply these lessons.

Meet Your Teacher

Teacher Profile Image

Miko Charbonneau

Creative Director, Designer, Writer

Teacher


Hey everyone! I'm a game developer, writer and content creator with over 30 games and apps shipped through self-publishing and at studios big and small. I also earned my PhD studying dance games a while back!

These days I run the indie game studio "prettysmart games", write books out in my greenhouse, and stream coworking sessions on Twitch (link above!)

I'm passionate about empowering others to live their happiest creative lives! Through my courses, you'll find advice on how to get unstuck, learn new tools, and find the process that works for you to make your goals a reality!

See full profile

Level: Beginner

Class Ratings

Expectations Met?
    Exceeded!
  • 0%
  • Yes
  • 0%
  • Somewhat
  • 0%
  • Not really
  • 0%

Why Join Skillshare?

Take award-winning Skillshare Original Classes

Each class has short lessons, hands-on projects

Your membership supports Skillshare teachers

Learn From Anywhere

Take classes on the go with the Skillshare app. Stream or download to watch on the plane, the subway, or wherever you learn best.

Transcripts

1. Introduction: No matter what kind of game you're making or how big your team is, you need to organize your game development documents and assets. This may seem like kind of a boring thing, but anything that saves you time means you get to spend more of your effort working on your game. And if you don't have a plan from the start, it's easy to end up with a cluttered collection of files and folders. In this course, I'll show you how to keep everything organized from the beginning. We'll cover your documentation, your game assets in and out of engine, your tasks, folder hierarchy, and naming best practices. I'll be using unity and notion in my examples, but you can easily translate these lessons to any note taking app and game engine that you prefer. By the end, you'll have an easy to follow system. You can apply to all your game projects in the future and use to clean up the ones you already have. So, let's get started. 2. Installing Notion: I'll be using notion in this course. So if you need help installing it, that's what this lesson is for. I recommend the software because of its great formatting features and database tools. You go to the website, which is at notion dot SO, and they may change up the way it looks. They do that every once in a while, but the general process should be the same. There'll be some very noticeable button that says get Notion for free or sign up here. Then you'll be able to use an account that you already have or make your own account from scratch. This is really up to you whatever you prefer. Although it's good to pick an e mail address that you don't mind sharing with others if you're going to collaborate. After that, I think you should get both the mobile app and the desktop app. The mobile app is really great for quickly making notes on the go, so you don't forget anything. And the desktop app is really great for deeper work. I especially like to have two windows open at a time, which you can do on windows with Control Shift N. That lets me look at my to do list and also lets me look at whatever I'm currently working on or copy things in between two different windows. There are multiple plans in notion, and you'll be fine with the free one, especially if you're just starting out. You'll still be able to share with some people as guests and you'll have unlimited pages. If you do want to pay for the software, one of the primary benefits of that is being able to have larger files added and the page history in case anything accmly gets deleted. So that's something important to think about. But you can definitely stay on the free plan when you're starting out and just see if you like the software. Once you've got everything set up, go ahead and open up notion in browser or in your desktop app, and we'll be ready to get started. 3. Overview Page: Okay, so what we're going to do is create an overview page from scratch. Here's an example from one of my previous games. This is like a home page or start menu for your game project. And it's a great way for new people on the team to find what they need and quickly be onboard, or just to keep everything organized. So you're going to go ahead and make your start page at the highest hierarchy level that you can. Mine is inside of courses and videos for my example, but try to put it as high as you can. You should also select the star in the upper right hand corner to pin this page to your side bar, that'll make it easy to find this, especially if you're an active notion user that already has tons of other pages. The first thing that we're going to do is have a name for this page, and we're going to use a code name for our project. This idea that I'm going to be using for the course is a wholesome cruising game idea that I came up with. And so for now, I'm just going to give the name of the game, Cozy Cruise, and you're going to click on Empty Page with icon, and I'll pick an icon randomly. This is a pretty fun one. But you can change this icon to be anything that's related to the game. I'll choose a shark because it is ocean based and I love sharks. You can also add a cover, which again, will randomly choose something from the library, but you can upload any image that you want, or you can search in their list of images for something that's better. So I'm going to find something ocean themed here just to get kind of that imagery going. Hopefully the next time that you're on a cruise, you don't have to deal with a wave like this, like these people here. But, it's just something to get everything rolling. Give it a nautical vibe. And then for our first section that we're going to make up here, we're going to use a heading one by doing a slash and starting to type the word heading and then press Enter. We're going to call it the game overview section. The main goal of this page is to have everything in a place where people can quickly find it. So ideally, we want this whole page to be pretty short, but also very handy, and then use pages within it to get into more detail. The first thing I'm going to put here is the same thing that we have above, which is the code name and Cozy Cruz. The reason why I called a code name is because it's not the final name of the game. It might be, but we haven't done all the research I want to into what we're going to name it. And we can always add that final name here when we have it. For picking your code name, it can be something totally random, or it can be the name of your favorite restaurant, your dog's name, or just something that has to do with the game itself. And that's why we picked Cozy Cruz for our code name because it speaks to the vibe of it and what the game is about. Having a code name makes it easier to talk to your teammates. Speak of teammates. The second thing we're going to do is add a team section. Now, when I hit a slash here, you can see that you can poke around and look at all the different types of things you can add with notion. So don't feel shy about opening it up and trying some other things out as well. But we're just going to very quickly add a heading two, and then put a list of our current team. Let's do some aesthetics here as well once we have this written out. You can highlight, and then you'll see a little pop up that lets you bold and underline these titles. Making things more beautiful actually makes the more readable. We're going to be doing that a lot in this course because our goal is for you to find information as quickly as you can. After that, let's add a couple of high level sections to give a framework for your whole project, starting with the elevator pitch or one line summary. This is a phrase you use to summarize your whole idea, and it's often updated throughout your game death process until you land on something that's just right. In general, your elevator pitch is going to be something that says what it is in the first part of the phrase, and then what makes it different or has a unique element to it in the second half of the phrase. After brainstorming a bit, I knew I wanted this to be a relaxing cruise game, where felt like a vacation, but I think it would be fun to make it a little mystery game and also have that tilt shift, cute little art style. And that's what I tried to capture with this pitch here. I also like to have creative pillars. These are three to five statements with a descriptive paragraph, using words that define what the most important principles are in your game. So I'm going to use three pillars that I brainstormed here. One thing that makes these pillars extremely useful is the fact that you can use them as a razor blade on your features. If everyone agrees what your creative pillars are from the beginning, later on in development, as you start to come up with all cool ideas, you can use these pillars to say, Hey, is this actually something that emphasizes what we're trying to do here, or is this a really cool idea, but it just doesn't make sense for this game. I want to emphasize these a little more, so I'm going to use Notions color feature for that. You can highlight like we did before or use the little dots on the left side to click, and you'll see color in here. That will let you add a subtle highlight to the whole line. But actually, we're going to use the other part here and just color the font itself. And then I'll bold it as well, which will give it a little bit more pop on the page. Since these pillars are really important, we want them to stand out and be easy to read. If you don't have these yet, that's totally fine. Just block in these sections, write TBD or something similar, and you can return to them later when you can. 4. Important Links: Next section is your important links. There will inevitably be other websites and apps that you need to point to regarding your game. This list is totally up to you. But you should try to keep it fairly small. Here are some examples. You might want to Google Drive link or one drive link or something that points to your Git hub where you keep your code, your social media accounts, or maybe your own website and press kit. A good rule of thumb is to keep a mental note every time you scramble to find something important. It happens more than twice, it's something that you need a quicker link to. Now, in notion, you can highlight this and make the whole thing a link or you can add a colon and put the link right after it. It's really your preference. You can even make links to other parts of notion. This list will be short at first. And again, if you don't have anything yet, that's fine. But you can block it in whenever you find that you can't find something as easily as you hope to. 5. Documentation: Next section is for your game documentation. As you work, you'll naturally create notes and ideas that you'll want to write down so you can remember them later. You don't have to organize these pages formally yet, but still helps to know where to go to find all of your notes. I recommend starting with two sections, a game design document and a technical design document. For the design document, this can be anything about how the game works, the narrative, the main features. Again, we're going to make an empty page with an icon. I'm going to choose a brain icon for this to represent all the thinking we're about to do here. And at the beginning, like I said, this can just be a bunch of random notes. Anything that's in your brain that you just want to get out onto the page so that you don't forget about it. In this case, I'm thinking that I definitely want to have some kind of buffet feature that maybe is one of the first things I'm going to prototype for this cruise game. If you want to make a bulleted list like this, you just need to do an asterisk and then press space to get it started. Later, you might want to build a legend when you're getting a little more organized. This is just a little section at the top of your design document that's color coded so that when people are looking at pages below, they know the status of every page. It's really common for design document pages to be out of date because people have made new decisions. Make sure that if you're doing something like this, though, that you're keeping in mind anyone who may be color blind on your team and that you're using colors and symbols that work for everybody. Now I'm going to make a sub page for the gameplay loop. It's just a slash page to make a new subpage. I really want to show you how the toggle block works with a slash toggle. This is something that lets you collapse and expands sections of your document when it gets really long. Once you have this toggle, you can easily colorize it just like any other part of notion, and then you can drag things into it. You'll also give it a name. This may seem a little redundant to call it the overall section, but this is the name that you'll see when it's collapse like this. We could even take this previous segment that we made and just drag it right in like this, and now it's all contained in one place. That's another way that you can keep your design doc organized. Now let's move on to the technical document. The technical design document is useful for details about what tools and game engine that you're using, breaking down features into coding classes and functions, or any research that you have to do about the technical areas. Some people like to have their technical document as part of the game design document, and that's totally fine. When I do that, I like to have the dev details be a section within every design page. But having it separate is also a good idea if that's how you want to organize your material. You could even start out with something like a simple to do list here. You can do this with the slash to do command, and that just makes a few checkboxes that really fun to fill out. Now the next page I'd like to have is a research guide, and this is about comparable titles that are similar to your game. Let's get a magnifying glass in here since it's all about investigating. At the beginning, you can just start off with some notes about what kinds of games you think are similar to yours. For our cruise game, I'm thinking about games that feature cruises and ships, Maybe some wholesome games like Life Sims with small worlds, and then some cozy mystery games. I'll first start out with a list of something like so. Then I'll do some research and I'll start grabbing some links and putting them in here. You can embed a list of links from steam, which will show you the image and the name. You could also make a header for every game name and a bunch of information about it, or you can make a database and have a separate page for every game. Finally, I'd like to have a business and marketing section or even separate pages for those two topics for details like the selling price, the social media campaigns, events you'd like to submit to, things like that. You may even want to store assets page because many of the platforms require different visual assets, and you might want to know about that from the beginning. If anything feels overwhelming or if you have different names or different needs right now, don't stress out. We're just building a skeleton to fill out, and as you work on this game, you can use these pages to store links and quick ideas and then reformat them into something more organized as you get further along. A 6. Style Guides: If you're wondering why we haven't covered art and audio yet, this is the lesson for you. We're going to call these sections style guides. For the art style guide. This can include anything from inspiration mood boards to early art experiments to final game art guidelines. We can also use these pages for fonts and color schemes, any little details that help the art team keep everything consistent and on the right track. Notion does support multiple columns of images, but it can get tricky to move things around. You can also use divider lines to break sections apart. But if ultimately you don't like this style, you can make your own moodboards and other image programs and bring them in. For the audio style guide, you can bring in reference videos, playlists, audio files of in progress effects or music, anything like that. We've also found it helpful to make notes about the full list of expected songs and any other audio deliverables we might need outside of the game, such as the soundtrack. You can also use these cell guides for instructions on how to add each type of asset to your game, which will be helpful for the team to work consistently. Even if you're working by yourself or on a small team, it's easy to forget how to do something if you haven't touched that area in a while. Try to write down the steps the first time you do it to save yourself time in the future. 7. Task Tracking: Next, we're going to talk about task tracking. This area can get complicated, but we're going to do a very simple version in this course. Notion is a great way to get started in this. Now you might have noticed that I've been writing the code name in front of the page name on a lot of these sections. The reason for this is if you're going to be searching a notion, it's much easier to find the one that you want when you have the code name attached. You're not looking at a bunch of pages called task tracking and trying to figure out which one is the one you're looking for. So for this, you're going to do a slash, and we're looking for a database, a board view database. Though any database can be used with multiple views. And this board is often called a C bond board. It starts automatically with three columns, and you can drag these cards in between the columns. So that's an easy way for you to track your ongoing tasks. Each of these cards is also its own page. So if you want to make notes on them, you can do that very easily. We're going to do one more thing here. We're going to change the property, starting with the assigned property. So this assigned property, I'm going to change the limit to one person. This is just for convenience so the UI doesn't ask you for multiple people. And we're also going to add a select property, and we're going to name this sprint. And this is going to represent whether this is in our current group of work, or upcoming group of work or something in the far future. The past is for dragging finished tasks to. You'll see that after you do a few current sprints, you'll have so many tasks in your completed column that you'll want to sort of archive them somewhere. It's up to you how long these sprints can be. You don't have to assign a time limit to them at all, or you can say that you want a current sprint to last a week and put that many tasks on there that you think you can complete in a week. So that's completely up to the way that you like to work. Let's also change the board format to allow for thumbnails and a smaller size. So you can see we can add a gift to this card, and now it's easily seen on the main task board. Also, I like to filter by subgroup, which allows us to make some rows for our convenience, and we'll use the sprint categories for them. You may have to rearrange in that menu the order of the different sprint options. But you can see now we can easily drag them up and down. If you want a more detailed version of task tracking, check out my course, finish your indie game, where we do a little bit more complicated version of this. 8. Source Control, Builds, Testing: For the last few lessons, we'll be moving away from documentation and discussing the organization of your development assets. But let's discuss a few more pages you might want to have a notion before we're done here. Having a source control page is useful for giving your team instructions on how to get and check in updates on your game. If you have a new source control before, it's essentially a system for backing up your work and avoiding conflicts between members of your team. You can also use this page for links, best practices, or frequently ask questions. Next is the build page. Having builds of your game to share is useful for play testing, bug fixing across your team or sharing with outside collaborators. It can be as simple as just putting a date here, and you can drag the build file right in if you have the space for it on your notion. But if you prefer, you can also make this a table. And what's useful about making it a table, which is another form of database. There's actually also a simple table that we're not showing here. This one will allow every entry to still be a page, and you can give it a property which is an attached file to put the build right on here. Having the page like this is really useful because you can also include build notes, change lists, known issues, and bugs, things like that, and you can use the comment section as well. You also might want a test plan. You may not have much to write here in the beginning, but as you start working on your game, you can use this test plan to write notes about important features and just make it a sanity check every time you create a belt. For example, you might want to have a list for our Cozy Cruz game that says something like make sure you can leave the cabin in the morning and make sure that you can start the Bingo game. Try to create a list of things that you want to double check before you send a bill to anyone else. 9. Folder Hierarchy: Now, let's step away from notion and talk about our game assets. No matter what game engine environment you're using. You're probably dealing with folders of scripts, images, audio, scenes, engine specific features like unreal blueprints or Unity prefabs. It's tempting to start a project by stuffing things into random folders, but you'll pay the price eventually. By investing a little time up front into your preferred project structure, you can reuse it for all of your projects and save precious time and stress. The most important rule for organizing your content is that you know where to find things. Your first gut instinct of where to find something is usually the right call. The two main ways to structure your folders are by type and by meaning. By the way, I'm using Miro to diagram some of these examples out, which is another tool I recommend, especially for diagramming flow charts. Type is what it sounds like. You sort folders by what type of content they contain. For example, in this list here, characters, decals, enemies, props, and the UX assets. Now, if we're going to take the same content and organize by meaning first, we switch the order. So we might have a folder for enemies, and then a subfolder for every type of enemy within that. Within these subfolders, we then organize the animations, audio, images, and materials that belong to that enemy. In general, I'd recommend not naming folders with temporary information, such as the date it was added or the name of someone on the team. One exception to this could be giving each team member a folder for their experiments, and their chaos can be contained within as they're working. But later in the process, it's harder to remember what month an item was added rather than I need the pink car now. An external plug ins folder is also good to have, as it can keep other content that you have purchased to use in your game separate from the content that you've made. I usually do this so I can remember to remove it later or to give credit if it's staying in the game. We use an underscore in the front so that this folder is easy to find at the top of the folders list. Don't be afraid to mix it up if it's easier for you. I usually like to organize my content by type first, but I found it too confusing when making V effects, since they use so many types of files. In our game, Z effect ends up being its own folder. Another last minute trick to make your life easier is to set up saved searches for the terms and specific files you need most often. Once you catch yourself doing the same search or action multiple times, it's a good candidate for a shortcut. And once you've got everything the way you like it, it's always useful to create a notion page with all this info listed out. Otherwise, you might have other people on your team putting things in folders without knowing the way that you wanted it organized. I'm going to put this in the technical design document. But if that doesn't make sense to you, put it wherever you're going to look for it first. You can use a simple bullet list here. It doesn't have to be too complicated. And you can refer to this list later the next time that you're starting a new game project. S. 10. Naming Conventions: In addition to having a great hierarchy of folders, your assets will benefit from great naming practices. This can be challenging for any team, as we all have different ways we like to name our files, but it's super important to have a consistent method everyone agrees on in the game, especially as you get into iteration work, where files should seamlessly swap out as they are updated. This will also help you when searching, so you're not looking at 100 animations that are named the same thing. The first best practice is to get used to naming all of your layers and game objects in all your tools. Even adding a subfix based on their shape, their position, or their size is better than nothing. You can also go back to numbers if you absolutely have to. Another example of this is not naming all the doors in a room door. You can name them things like door outer East or whatever distinguishes each one. In your art files, this is important for later editing, and if files automatically get named when they enter the game engine. In your game engine scenes, this will make animating and scripting much easier, too. For example, in Unity, a dot PSB can be added, which automatically makes images from every layer. Taking the time to name each layer appropriately makes this pipeline work almost instantly. Another good idea is to use parenting within your game scenes. So you can see here that I've named a bunch of empty game objects, parent underscore and whatever that topic may be. And that way I can nest and collapse different types of game objects, so I don't need to be looking at them all at the same level of the hierarchy. To find a naming hierarchy that works for you. Start with the categories you've already used for the folders. If your folders go image and then minions, you can name your assets, Minion, underscore the Minion name, and then something like idle for the pose of the enemy. Also, you might note here that we have a slight mismatch between our folder name enemies and our file names Minion. We're not perfect either, and it's okay if you don't get everything exactly 100% cleaned up, just do what you can to make it more convenient for you to work and clean it up if it seems to be a problem. I often start with naming the most broad category and going to the most specific. We also tend to combine a narrative name with a gameplay term. If you have a weapon that everyone calls the Dark blade or on the office, because it has shadow abilities, you might want to name it weapon shadow Dark blade. It's fine if the asset is named something different from the final in game name. But keep in mind that some players may dig through your game code, so avoid using anything you'd find embarrassing if it came to light. Don't put numbers and dates and versions on the end. That's a common shorthand for many creatives, but it will drive you wild later. Once you have a good system in place, you can update your style guides and documentation pages for easy reference. 11. External Assets: Let's talk quickly about your game assets outside of your game engine. You may have everything totally organized now, but what about the original files for your art and audio? It's likely you have much larger versions and working copies that need to be preserved for future work. So how do we keep them safe? If you want to keep everything in the same place, you can make separate databases in notion that track the progress of every asset. Or you can add your art and audio files to your source control if you prefer that. If that's not an option for you, using a Cloud service like Google Drive or One Drive works just as well. If you want to name these files with more freedom than you used in the game, adding sues like V two or the date, that's fine. But I'd still recommend you organize the subfolders in the same way as they are in game. So everyone gets used to the hierarchy. Once your content has a home, don't forget to cross link it back to your overview page. The important link section is a good spot for this, or you can add them under the appropriate style guide. 12. Conclusion: That's it. We're done. I hope that this helps you get your game dev documents organized. For more examples, check the course description where I've included reference images and screenshots. And please, share your own screenshots of your setup in the discussion area below, or tell me about your game if you want, or what courses you'd like to see next. I'm here for you. If you enjoyed this course, please follow me on skill share for more lessons, and please leave a review or a comment in the discussion, as I'll help me know what would help you the best. You can also watch me stream gamed on Twitch, or join my discord or Patrion, if you want to hang out with me more someplace else. Thanks for watching and good luck with your game project.