I am a site owner, and up until now, I have always created sub-sites instead of using basic pages or Web Part pages. I would like to understand what advantages Web Part Pages have over just adding a new sub-site.
So far, the biggest difference I think I see is that Web Part Pages don't allow the admin to control the access the same way as with a sub-site, which, to me, is a disadvantage. The other difference is that Web Part Pages are stored in a library. Are there advantages to storing pages in a library?
What other differences are there? Why would I choose a Web Part Page over adding a new sub-site?
The description of "Pages" from the Microsoft site is very basic. I guess "Pages" means all three types of pages? It seems that a site can do all that a Web Part Page can do and then some. Why would I choose to use a Web Part Page? On the MS site Introduction to sites, workspaces, and pages says:
"What is a page?
A Web page in a site can display lists of information, enabling team members to organize the information any way they want, such as by subject, due date, or author. For example, you can do the following:
- Filter the content to see only the set of information that applies to you
- Hide information that doesn't interest you
- Change the order in which the information is listed
- Set up customized views to make it easy for your team members to focus quickly on pertinent information "
Does someone have examples of when to use a Web Part Page instead of a sub-site? For example, does a Web Part page use significantly less space on the server? Does it load faster? Is it easier to retire when it's no longer needed? What problem was Microsoft trying to solve when it created Web Part Pages?