These pages are (or simulate) project deliverables. They range from articles to college lectures. Some entries are about format and style, while others contain audience-appropriate content. You can decide whether you are viewing the portfolio for format or reviewing it for content.
For example, content for educators may not seem to be useful to business developers who need online educational experiences, but accessing them all in one place allows you to make your own decisions.
Portfolios will showcase product samples, and the skills of the person that owns it. The heart of the matter is that the skills are not usually visible in a completed product, unless it is equipped with a breakaway view.
However, if all of the portfolio pages were a single project, they would relate to each other like this.
The BIG Picture. Visualize it, then make it happen.
In a large project, communication is what sells the big picture.
Write code that will cause the big picture to become a reality. Provide them, or their design patterns, to your team as appropriate.
Projects sometimes re-prioritize tasks, or re-train people. This content is separate from the documents that might be "in the box".
This content is "in the box". What it is, what it does, how it's used, how to install it, how to support it.
The BOX. Think outside it, look inside it. Write advertising for it. Regardless, visuals are what sells it.
(Don't mention that the CI/CD deployment pipeline doesn't use a box anymore...)
Gaming and animation have had a major impact on non-gaming Web pages, branding, and the UX experience.