All that said, my client is looking to transition the site to be based in SharePoint (basically run on their big SharePoint company intranet website). I have a lot of experience with C# winforms programming over the years, but no specific Sharepoint programming and no ASP.NET programming of note.
I am looking for suggestions based on your experience with SharePoint/ASP.NET. What sub-tools/technologies in SP might be a good fit to write the site on? I have just started to skim what options I have. There looks to be many different sub-tools/technologies I can leverage in SP to transition/rewrite the website. I will assume they are running on the most recent version of SharePoint, but they could be one version behind. They have been using SP for many years now as their intranet site (multinational company), so I assume they have every add-on to SP available. I do know they have a big server farm setup for SP.
I am not looking for really hard specifics here, just suggestions on Sharepoint/ASP.NET development that might be best practices or whatever given my description of the existing website. There seem to be 10 ways to do any one task these days with Microsoft tools. Probably my biggest difficulty moving forward will be working with their IT to secure resources on their servers to make it happen, haha.