Add Project Organization Text to Title Screen Section#168
Open
Les-Wet wants to merge 4 commits intogbdev:masterfrom
Open
Add Project Organization Text to Title Screen Section#168Les-Wet wants to merge 4 commits intogbdev:masterfrom
Les-Wet wants to merge 4 commits intogbdev:masterfrom
Conversation
quinnyo
approved these changes
Jan 25, 2026
Contributor
quinnyo
left a comment
quinnyo
left a comment
There was a problem hiding this comment.
This looks good.
I think the input code is a good, understandable, chunk to separate.
The title lesson is pretty brief, so it seems like a good opportunity to do some 'housekeeping'/refactoring.
src/part2/title-screen.md
Outdated
| And just like that we have ourselves a title screen! | ||
|
|
||
| ## Organizing Our Code | ||
| Our project is getting quite large with all the functionality we're building in! Let's briefly go over how to better organize things. Until now, we have always added new code into the same assembly file (`main.asm`). This file can get pretty large if we're not careful. Instead, RGBDS has a handy feature for making [functions](./functions.md) or other labels visible to external files. As an example, let's take everything we added in our [input](./input.md) lesson, and put it in a separate file named [`input.asm`](https://github.com/gbdev/gb-asm-tutorial/raw/master/unbricked/title-screen/input.asm). |
Contributor
There was a problem hiding this comment.
"This file can get pretty large if we're not careful." doesn't explain why the file growing is undesirable.
Contributor
Author
There was a problem hiding this comment.
Good eye. I added a commit that adds text to justify why chunking files into functional blocks is desirable for a software project.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As discussed in #149, it could be beneficial to introduce linking multiple assembly files in the Title Screen section of the tutorial. This section of the tutorial is rather sparse, and could help prepare for the complexity of the Serial Link section, which is currently the section which introduces multi-file projects.
This PR adds a section to the Title Screen page which teaches how to make and build multi-file projects. It also slightly rewords the Serial Link section now that the Title Screen has already introduced that topic. Lastly, it removes and corrects the style of the
input.asmfile in the way that #149 intended to.