Documenting Construct Projects
As you probably already know that Construct has "Scenes, Layout, and Layers" and then each of those has an associated "Event Sheets". Well, if we think about it while reviewing the picture above, we should see that the "Event Sheets" really have all the game's "rules, logic, and data" -- the Game Mechanics. The "Scenes, Layout, and Layers" hold all those visual elements displayed in the browser -- the Game Framework Mechanisms. It becomes a simple matter of exchanging the "Imported Artwork" to build a visually different game that uses the same "Scene" arrangements, rules, logic, and data. Adopting the Game Design System™ allows you to crank out several games, of the same genre, within a week! Your only limitation is: "How fast you can create your Artwork and Theme assets?"
"Great, I knew all that!" you say? Well, of course, you do. But I'd wager that if you returned to a game you created months or even years ago (especially in my case with "forgetfulness" setting in), you'll hit a development barrier: trying to remember "what, where, and why" you wrote that game in such way. AND, if you didn't sprinkle your event sheets with "comments" nor created supporting documentation -- like most software engineers don't or they write "sketchy" notes with cryptic meanings -- "deconstructing your game's design" becomes even harder as you "root and snort" through those large-single "Event Sheets" looking for those "needles in the haystack". You didn't really write everything in only one Event Sheet? Right?!? Please say you didn't! My heart couldn't take it.