What is a page?

Rachel Jackson  I love using the pages for a variety of use cases that don't directly correlate to content like forums, wikis, etc like you mentioned. I have a few different informational/landing pages that wouldn't fit into the rest of the site architecture. A few examples:

• for some of our programs
  
  • https://sugarclub.sugarcrm.com/learn/p/skill_builders
  • https://sugarclub.sugarcrm.com/learn/p/certification_overview
• an "All" page, rolling up all content from all applications across the site
  • https://sugarclub.sugarcrm.com/p/all
• a way to nicely show a list of sub-groups within a specific group: 
  • https://sugarclub.sugarcrm.com/engage/p/user_groups
• A way to host things like embedded forms that COULD go through our corporate website, but this is another way to drive traffic to our community:
  • https://sugarclub.sugarcrm.com/p/become-a-reference
• We use SSO for login, but there's a "hidden" admin login page with the login widget in case something ever happens to our SSO connection/configuration (especially useful when we were initially rolling out our site). It's basically the key under the doormat now

We also have some upcoming initiatives for our company that need landing pages for a catalog of reference materials, but since it's not relevant to ALL customers, we didn't want to put groups or blog posts out in the "regular" community, but they still need to be publicly accessibly. For some of these pages, they're part of the site theme from the home page, but I added the Custom Metadata widget and <meta name=“robots” content=“noindex”> so they're not readily available for people that haven't been emailed the direct link.

All of these come with the benefit that I was able to customize more of the theme of the page without worrying about the functional buttons (join, digests, create, report abuse, etc) and had more flexibility over the page-specific CSS and other widgets. 

Rachel Jackson  I love using the pages for a variety of use cases that don't directly correlate to content like forums, wikis, etc like you mentioned. I have a few different informational/landing pages that wouldn't fit into the rest of the site architecture. A few examples:

• for some of our programs
  
  • https://sugarclub.sugarcrm.com/learn/p/skill_builders
  • https://sugarclub.sugarcrm.com/learn/p/certification_overview
• an "All" page, rolling up all content from all applications across the site
  • https://sugarclub.sugarcrm.com/p/all
• a way to nicely show a list of sub-groups within a specific group: 
  • https://sugarclub.sugarcrm.com/engage/p/user_groups
• A way to host things like embedded forms that COULD go through our corporate website, but this is another way to drive traffic to our community:
  • https://sugarclub.sugarcrm.com/p/become-a-reference
• We use SSO for login, but there's a "hidden" admin login page with the login widget in case something ever happens to our SSO connection/configuration (especially useful when we were initially rolling out our site). It's basically the key under the doormat now

We also have some upcoming initiatives for our company that need landing pages for a catalog of reference materials, but since it's not relevant to ALL customers, we didn't want to put groups or blog posts out in the "regular" community, but they still need to be publicly accessibly. For some of these pages, they're part of the site theme from the home page, but I added the Custom Metadata widget and <meta name=“robots” content=“noindex”> so they're not readily available for people that haven't been emailed the direct link.

All of these come with the benefit that I was able to customize more of the theme of the page without worrying about the functional buttons (join, digests, create, report abuse, etc) and had more flexibility over the page-specific CSS and other widgets.