I'm a CS student so I have decent fundamentals about programming. One thing I struggled with yesterday when doing the trampoline mod was where the folders were supposed to be. I've poured over a few mods, and it seems like there is very little consistency about the convention of setting up the directory other than "put it in assets". As an example for me, following the guide to a T (or so I thought), I ended up needing to copy and paste the modinfo file into the root. Visual studio built off of ZZCakeBuild instead of the mod file I made, there were cs files inside of the mod that needed removing before building the final zip file package. I finally got it to work, but for such a simple mod, it took me far longer to troubleshoot than I'd like to admit, and I honestly felt somewhat more confused in the end than I did in the beginning.
As others have said, a guided walkthrough in the form of a self paced replication of a real mod, would be wonderful. Something the community can opensource review for best practices, explaining the why and how of things, and giving a higher level understanding of how everything scaffolds would be massive. Structure and file relationships is where I find the wiki tutorials lacking, and maybe a bit of JSON information for "code" values.
I would vote for a wiki page that's more like a book, with a basic informational landing page that points to an index of chapters and sub chapters, something like the following:
Getting Started
Introduction
Basic Overview (why the following chapters are important)
Devolopment Environment
Dependencies
API resources
File Structure
Root
Assets
FooMod
modinfo
FooMod.dll
Best Practices (links to C#, JSON, and Anego Studios specific docu for best practices, etc.)
C# Links
JSON links
Anego links
General Best Practices
Types of Mods
Theme
What
Why/When
Examples
Content
What
Why/When
Examples
Code
What
Why/When
Examples
Theme Mod Tutorials
Content Mod Tutorials
Code Mod Tutorials
