Intranet Site Structure with Hub Sites

Charisma Riley  Just looking at this piece:

For a site like Products and Services (which currently has sub-sites), what types of Modern site is recommended? It's not just a single team, and will either need to link to (or house directly) document and asset libraries. Originally, I thought a Communication site, but then I read that those cannot have sub-sites, and that if I want those, I should consider Publishing sites instead. But THEN, I read that publishing sites are not available as modern sites, and that doesn't work for us. 

Here's how I would design it if it was for us. We're starting our rewrite from our old SP2013 intranet to the new SPO structure, so these are just my thought process...

I'd create a communication site 'Products and Services'. I would make it a public site if there are documents/lists/news articles that would be shared with the whole company. Make it a hub.

Then all those other subsites I'd make team sites, and associate them to the 'Products and Services' hub.  Benefits:

• Communication site hub has extra navigation where you can use mega menu to get to all the associated sites.
• Searching from the hub would easily surface information in all the other associated team sites.
• You can now have 2 levels of news - teams can create their own news that is accessible to their team, and for 'public' news you can publish those on the hub site...

Then on the main Intranet site, or wherever needed, I'd add a link or a menu option or a hero webpart or image that links to the 'Products and Services' site. 

For wikis, to stay modern, you'll want to use modern pages. You can create page templates so all pages can look the same, you can add metadata to the Site Pages library, and you can surface those pages anywhere with the Highlighted Content web part...

You could even create a separate team site, or another comm site even, and use it for all wiki pages if there aren't security concerns....