Why webs?
Because they are manageable live scalable communcation systems.
Good Communication like Good Habits are a continuum not a scattering of events.
As engineers we have two primary jobs: do good math and communicate it.
We're good at the engineering - often using state of the art tools and habits. With communication, most engineers do not use the best practices.
Email is NOT a Management System
For example, how good a management tool is email? Granted, it's a pretty good notification system, but it's a BAD management system.
It's a good Push system, a bad management system.
Live is Great, but eventual. Lots of waits.
Meetings are good. Presentations are good. But they are synchronous. They require participants to be available at some time - generally, too far in the future.
Asynchronous Communication does not require simultaneous attendance.
A mindset for Continual Asynchronous Communication means: sharing information (appropriately) as soon as its available in a consumable way. Meetings and Presentations can be Live, but the material doesn't need to be blocaded until some future date. Material has a "life" and live meetings are a point in that continuum.
Web is the Way
If webs are the way, why don't Engineers and Project Managers use them?
The short answer is that learning the full technical stack to build full-feature websites is a big ask.
The good news is that once a web is set up, editing and creating articles (pages) and other tasks sufficient to manage an implementation project is pretty simple. Especially if you have a web author available.
Case Study: How the web helped a huge migration and "Surpise Step-Up"