I would generally agree an IDE should be the best place, but I've had trouble in practice. Maybe I haven't leaned on those features enough? My trouble with a

I would generally agree an IDE should be the best place, but I've had trouble in practice. Maybe I haven't leaned on those features enough? My trouble with a brand new codebase (framework, language, or library) is sussing out separation of concerns (usually split between files/functions/modules) and flow of code. An IDE should definitely help navigate those things (sometimes you need to actually run the code and look in a debugger). One reason a website might be more handy is skimming codebases you don't actually intend to build and compile. I do this to new projects all the time to stuff I see here (generally on GitHub). I'll also often look into the cPython codebase because I use Python, but it's very rare I have the need to download and build it.