Ability to create custom pages / menu items on the customer portal

We could REALLY use this feature. Even it was limited to like 2 or 3 extra pages.
I would love to have a couple scratch pages we could modify similar to how we can modify the other pages in the system now.

I mean, I can go in and edit the heck out the existing pages to look any way I want, which is AWESOME, but if I had just a couple new pages I could add, FreshDesk could replace our SharePoint site.

Would also be great if we could modify some pages of the Agent side of the system. Hide the social tab, add a new tab that links to our e-commerce site, for example.

We could really use this as well.

I'm really surprised this isn't a standard feature. It's great being able to the few pages I have access too, but at the same time I feel limited if I can't add content that isn't in the knowledge forum format.

Please let this be a thing....

Guys, this might be what you're looking for: 

https://support.freshdesk.com/support/solutions/articles/83289-adding-a-new-tab-to-the-navigation-bar

The use case here isn't really fixed by just the addition of a new tab. I also have similar needs.

The desire here is to have one support portal with one theme that can be managed and updated via freshdesk exclusively. Essentially, it would be like adding a stripped down CMS to the Portal Customization feature of the Estate plan. I'm not saying that a wordpress engine needs to be added, but just another area where other pages can be added in that use the same setup and css as the rest of the portal.

Adding a new tab is only a partial solution as adding a new tab only creates a nav link and lacks the creation of another top level page that holds content. While a tab could link to a specific article or forum post, it still takes the end user to that section of the website for that desired content, and the page then reflects that location in the breadcrumbs and styling for that sub-section of the portal, instead of keeping the new content in its own logical sub-section of the portal. 

The idea desired is to have some extra content pages on the site that hold other content that goes along with details on the support portal but aren't specifically support articles or forum posts. Essentially, it would be like adding not just another tab, but having the tab add another whole page/sub-section of the support portal that still uses the same theme that is set in the customizable portal. The workaround of creating a tab that links to an external site for some details and then have that external site link back is that it creates two locations to update, maintain, and style similarly and just looks unprofessional. 

We have a need for having an additional page that contains a bulletin board of sorts that has details about uptime and coming release schedule, as well as links to strategic blog content for our service. This content is related to support, but not desired to be added as support articles for a number of reasons.

Example 1: Let's say that instead of having a blog subsection, we added the blog content as support articles. The blog articles would then be searched by the feedback widget, instead of serving only the applicable support article. Can you imagine how frustrating it would be to get an article in the feedback widget that talked about a topic's strategy instead of the nuts and bolts how to article on how to fix the thing you're contacting support on? 

Example 2: Let's say that instead of having a coming features section on the portal itself you instead have to new tab link to external page with brochure type marketing content. The end user is then taken off the support site and can't immediately use the new ticket button or jump directly to the forum to discuss the details in the community without having to browse back to the support portal. Instead of having one site, now we've got to update two sites. Instead of having one system to manage now we have two. Instead of having one site listing in Google search, now we have two that need to be linked together. It's clunky and not ideal.

I would love to have this feature taken up by Development.