If the site has a lot of guides, downloads, and supporting content, I’d avoid choosing one WordPress structure for everything. The structure should follow the type of content and how users are expected to move through the site.
For example, I’d usually keep the main evergreen guides as Pages if they are core resources that need to stay stable and easy to organize. If there are regularly published articles, updates, or tutorials, Posts + categories make more sense for those.
Custom Post Types can be useful when the site has a large number of similar resources that need their own fields or templates. For example, if every downloadable resource needs a version number, file type, operating system, requirements, screenshots, and a download button, a dedicated CPT can make the site much easier to manage than trying to force everything into normal Pages.
The important part is not just the content type, though. I’d plan the hierarchy before building it. A user should be able to go from a guide → installation instructions → relevant download → related troubleshooting content without having to search around the site.
For internal linking, I’d link based on user intent, not simply add links because two pages contain similar keywords. A setup guide could naturally point to the correct download, while a troubleshooting article could point back to the installation guide or a related solution.
With a large site, performance also becomes important. I’d keep plugins under control, avoid loading unnecessary scripts site-wide, optimize images and downloads, use caching, and make sure the database and hosting can handle the number of pages.
So in practice, a hybrid structure is usually the most flexible: Pages for core guides, Posts for ongoing content, and CPTs where there is a genuine need for structured resources. The key is designing the information architecture around how visitors actually use the site.